to a distant observer, you look similar, but i'm sure there are real differences between you, so I'd love something like a "top 3 things to note" about Increase vs Column, in a least-getting-you-in-trouble way as possible - its hard to compare because i dont know what I don't know.
I think there are many engineers who are frustrated knowing the data and capabilities that exist in banking that aren't exposed programmatically.
There are at least four (and I'm undoubtedly missing many!) interesting companies aiming to combine technology and a bank charter:
- Luna[0].
- M1 Finance[1].
- Column[2].
- Increase[3].
Building a bank involves reading, understanding, and respecting regulation. It invovles integrating with large financial networks. It involves rallying a team for a years-long adventure. Each of these is early days and it'll be a few years before any of us understands how this super large and important problem will be solved.
0. https://www.americanbanker.com/news/former-square-exec-leads...
Column is an actual bank, and offers exhaustive developer-first APIs. I suspect you can do a lot of things with them you cannot do with Plaid, and at highly reduced cost comparatively. Increase doesn't seem to be a bank but is a much lower-level API than Plaid and allows things like opening accounts, FWICT.
BTW, bunq (https://www.bunq.com/) is a cool nl-based bank which offers an incredibly in-depth API. But I would not call it dev-centric, the DX is awful.
As a developer, I'd love to have some more information about the typical problems that inspired Increase's value proposition. If I was meeting with a financial tech CEO tomorrow, should I assume that they probably have these problems or need this service? Are there resources that I could peruse to learn more about these common problems?
When we built Stripe, one of the largest points of friction was getting a banking partner. It took months and only after signing were we even able to start assessing the technology. There are so many potential companies that simply don't make it past the partnership step. We want to fix that.
The US needs a bank (holding a bank charter) that's also a technology company. Increase certainly isn't there yet (patches welcome: [email protected]) but we already have integrations with the Federal Reserve, Visa, and The Clearing House. Our API already serves businesses you know and love.
Do you have plans on becoming a bank and getting a bank charter then? I've worked with several payment processors and BaaS providers that are most definitely not on that path. (CTO at neo bank).
Or something like credit karma has?
Do you need a large amount of money upfront?
We took the approach of starting with an intentionally bad name (in our case, bnk.dev) and using it until a good domain became available to purchase for a reasonable price.
Related: http://www.paulgraham.com/name.html
We're early days and not quite ready for open sign-ups yet (sorry, known bug). We'll be more public over the coming weeks and months.
We're banking for developers; you can programatically create accounts, cards, and move money.
Our users are primarily financial technology companies.
We're a small team from Stripe, Robinhood, and Visa building the bank we always wanted. If this sounds interesting to you we're hiring: [email protected]
If I can be helpful, I'm at [email protected].