Column's Bank-Owned API Core
Column
Column is not selling a software layer on top of someone else's bank, it is collapsing the bank and the software into one operating system. That matters because the fintech customer signs one integration and then gets accounts, payments, cards, ledgering, and compliance from the same institution that actually holds the charter. In practice, that removes the usual handoff between middleware, sponsor bank, and processor, which cuts launch friction and gives Column more control over reliability, pricing, and risk management.
-
Most BaaS platforms sit in the middle. They help a fintech capture KYC data, open accounts, and issue cards, but the underlying bank still owns the regulated balance sheet and approval process. That structure can speed launch versus going direct to a bank, but it still leaves multiple vendors and handoffs in the stack.
-
Column took the harder path and bought an existing national bank, Northern California National Bank, in June 2021, then rebuilt the customer facing banking layer with APIs. The result is that deposits sit directly at Column N.A., payments run on rails it connects to itself, and compliance stays inside the same entity instead of being split across partners.
-
This model is now a real wedge in fintech banking. Column and Lead Bank are the main U.S. examples of chartered banks with modern BaaS style APIs, while platforms like Unit, Synctera, and Treasury Prime remain middleware. Column's recent growth has come from winning large fintechs like Brex and Mercury that want fewer counterparties and tighter operational control.
The next phase is a shift from brokered BaaS networks toward bank owned API cores. As regulators push harder on oversight and larger fintechs demand durability, the winners are likely to be institutions that can offer one direct banking counterparty, one ledger of record, and one compliance perimeter, while still feeling as easy to build on as modern infrastructure software.