Banks Internalizing Embedded Finance

The real risk to Bond was that its product advantage sat above the bank, not inside it. Bond made money by turning messy bank, processor, and compliance work into one clean developer workflow, but that same workflow could be pulled in house by banks that already owned the charter, compliance obligation, and economics. If a bank could offer modern APIs, dashboards, and onboarding directly, it could keep more revenue and own the customer relationship end to end.

• Bond’s value was concrete, it hid bank selection, compliance setup, KYC workflows, ledger data, and processor integrations behind one portal. Customers could see failed KYC checks, card issuance, spend by merchant category, and transaction level detail without stitching together multiple vendors themselves.
  2 sacra 3 sacra
• That convenience came with a structural tradeoff. Going through a BaaS layer usually meant giving up more revenue share than going direct to a processor and bank. For larger brands with money, compliance staff, and long time horizons, the incentive was to bypass the middle layer once they had enough scale.
  3 sacra 4 sacra 5 sacra
• The market was already pointing this way. Bond itself described banks moving from passive license providers to active embedded finance channels, and after the FIS acquisition the strategy shifted upmarket toward larger enterprises and banks, where standardized workflows, compliance tooling, and data visibility matter more than startup friendly self serve onboarding.
  1 sacra 5 sacra

The next phase favors platforms that either become the operating layer banks adopt, or go deeper in a narrow workflow that banks still do poorly. Broad BaaS wrappers become harder to defend as banks, processors, and large infrastructure firms package more of the stack themselves, which is why the center of gravity is moving toward enterprise embedded finance and bank facing software.