BaaS lock-in and market split

This reveals that BaaS lock in is driven less by headline pricing than by the cost and risk of rebuilding a bank in pieces. A fintech can pay a platform per account and per transaction, but replacing that platform means hiring compliance staff, support staff, operations staff, and engineers, then stitching together KYC, ledger, processor, and sponsor bank relationships. The economic case to leave usually appears only when a company wants more control over partners, product design, and migration timing.

• The concrete trade off is simple. A full BaaS provider wraps bank access, compliance processes, and operational work into one integration. Going direct can preserve more revenue share, but it pushes the fintech to manage the bank relationship, processor coordination, and day to day program operations itself.
  1 sacra 4 sacra 5 sacra
• That is why switching costs are so high. Moving providers can force new account and routing numbers, new cards, and a fresh compliance and operations setup. In practice, the pain is not just code migration, it is customer disruption plus rebuilding the internal teams needed to run the stack safely.
  1 sacra 4 sacra
• The market has since shown what companies do move for. Large fintechs have migrated away from middleware providers toward bank owned API platforms like Column, not because BaaS was too expensive in isolation, but because tighter control over the bank, ledger, compliance, and payment rails reduces counterparty risk and dependency on a middle layer.
  3 sacra 6 apnews 7 americanbanker 8 pymnts

The next phase of BaaS is a split market. Smaller fintechs will keep buying the all in one layer because it is still the cheapest way to launch. Larger fintechs will increasingly choose models that give them direct control of bank partners and core infrastructure, pushing providers to compete on flexibility, product breadth, and resilience rather than just low per account pricing.