BaaS Assembly Layer Economics

The key move in BaaS is not building every banking component, it is controlling the assembly layer that turns a pile of vendors into one product. Treasury Prime, Bond, Unit, and peers sit between sponsor banks, KYC vendors, card networks, and issuer processors, then expose one API so a fintech can open accounts, verify users, issue cards, and move money without signing and managing every vendor contract itself.

• Bond using i2c is a clear example of the stack. i2c handles core card processing, while Bond handles the middleware, bank coordination, and program management. A fintech can go direct to i2c, but then it has to manage more contracting, vendor setup, and operational work itself.
  2 sacra 3 sacra
• Treasury Prime partnering with Alloy for KYC shows the same pattern on onboarding. The BaaS platform decides what customer data to collect, runs that through a KYC vendor approved by the sponsor bank, and wraps the result into the account opening flow so the fintech sees one system instead of several.
  1 sacra 4 sacra
• This design makes launch faster, but it also creates extra mouths to feed. Interchange and fees get split across the bank, network, processor, and BaaS layer. As programs scale, customers often want more direct control because every extra intermediary can reduce margins and slow down troubleshooting.
  1 sacra 2 sacra 5 sacra 6 sacra

The market is moving toward fewer middle layers for large, scaled programs, and better assembly software for everyone else. Early stage fintechs and brands will keep buying the packaged version because it removes months of bank, compliance, and processor work. As volume grows, the winners will be the platforms that either own more of the stack or make the handoff to direct relationships much less painful.