Fintechs Insourcing Card Issuing

The real risk in all in one BaaS is that the best fintech customers eventually learn enough volume, economics, and operational detail to cut out part of the middle. Fintechs that live on interchange have strong reason to internalize issuing once they reach scale, because issuing is not just a feature for them, it is a core profit engine. Embedded finance customers using cards to improve workflow, like courier payouts or expense controls, have much less reason to rebuild that stack themselves.

• All in one platforms sit closer to the customer and often bundle ledgering, compliance coordination, bank relationships, and card issuing. That makes them valuable early, but it also exposes which pieces a large fintech can later peel off and own directly, especially issuing and bank economics.
  1 sacra 2 sacra 3 sacra 5 sacra
• The money incentive is concrete. In the unit economics laid out here, a fintech keeps more interchange than its BaaS partner, and larger customers negotiate harder as volume scales. That is why high growth fintech customers create both outsized revenue and outsized churn risk for BaaS providers.
  1 sacra 2 sacra 3 sacra
• Brex shows what insourcing looks like at the far end. By building direct network and issuing infrastructure, it removed dependence on middleware like Stripe Issuing, Lithic, or Marqeta for its global card product. That is the end state BaaS platforms worry about when a fintech becomes large enough.
  4 sacra

Going forward, the winners in BaaS will be the providers that either own enough of the stack to stay valuable after customers scale, or stay narrow enough that customers keep buying instead of rebuilding. That favors point solutions for specialized tasks and favors platforms that turn speed to market into long term workflow dependence, not just temporary convenience.