Financial, Geopolitical & Citizenship Intelligence Membership

Banking · Digital Banking

Banking-as-a-Service and Embedded Finance: Strategy and Risk

How BaaS and embedded finance work, the main models, where revenue comes from, and what the 2024 Synapse failure means for due diligence.

What embedded banking and BaaS actually mean

Embedded finance is the practice of offering financial products inside a non-financial product, such as a payment account in a ride-hailing app or a loan at the checkout of an online shop. Banking-as-a-Service (BaaS) is the infrastructure behind much of it: a licensed bank, or a platform working with one, exposes accounts, cards and payments through APIs so another company can offer them under its own brand.

The appeal is clear. A software company or retailer can add revenue and loyalty without becoming a bank. A bank gains distribution through partners' customers. The risk is just as clear: the brand customers see is not the one that holds the licence, and when something goes wrong it is not always obvious who is responsible.

The main ways it is built

ModelHow it worksMain strengthMain risk
Sponsor bank plus middleware platformA software platform connects many brands to one or more partner banksFast to launch and widely availableSeveral parties share the work, so records and responsibility can blur
Direct bank APIThe brand works directly with the bank that holds the licenceClear accountability and fewer layersSlower to integrate; the bank must have mature APIs
Own licence (for example e-money or bank charter)The company becomes regulated itselfControl of product and economicsHigh cost, capital and compliance burden
Bank-owned platformA bank offers its own BaaS platform to partnersRegulated end to endProduct and technology depth varies by bank

Where the money comes from

  • Interchange. Card fees paid by merchants are a core revenue source. In the United States, the Durbin amendment caps debit interchange for banks with more than 10 billion dollars in assets but exempts smaller banks, which is a large reason why smaller banks are popular sponsor banks.
  • Deposit spreads. Customer balances held at the bank earn interest income, part of which may be shared with the partner.
  • Software and platform fees. Usage-based or subscription charges from the infrastructure provider.
  • Lending margins. Embedded credit, when the partner brings underwriting data and the bank or lender provides the capital.

These revenue streams can change quickly with regulation and interest rates. A model that depends on one of them, for example an interchange cap exemption, should be stress-tested against that dependency being removed.

What went wrong in 2024, and why it matters

The weaknesses of the layered model became visible in 2024. Synapse, a US BaaS middleware company, filed for bankruptcy in April of that year. Customers of fintech apps built on Synapse found that balances held at partner banks, including Evolve Bank & Trust, did not reconcile with the records the apps displayed, and many were unable to access funds for an extended period. The episode showed a basic weakness: when several firms keep records of the same money, a failure at one can leave nobody able to say exactly who is owed what.

Regulators had already been warning sponsor banks. Enforcement actions against several of them, including Blue Ridge Bank and Evolve, centred on weak oversight of fintech partners, compliance programmes that did not keep pace with growth, and poor controls over customer money. In September 2024 the Federal Deposit Insurance Corporation proposed rules that would require banks to keep detailed records of the individual owners of custodial accounts, aimed at exactly this problem.

A due-diligence checklist for companies using BaaS

  1. Who holds the money? Know the name of the licensed institution holding customer funds, and be able to show customers how to find it.
  2. Who keeps the ledger? Insist on daily reconciliation between the bank's records and the platform's records, with a written process and reports.
  3. Who is accountable for compliance? The bank usually remains responsible for its anti-money-laundering programme even when the partner collects customer data. Make sure roles are written down and audited.
  4. What happens if a partner fails? Have a plan to move customers to another bank or platform, and check that contracts give you access to your own data.
  5. How does insurance work? Deposit insurance protects against the failure of the bank, not against losses at the fintech or platform. Pass-through coverage depends on accurate records of who owns the money.
  6. Is revenue durable? Test the business case without the most favourable regulatory or interest-rate assumptions.

What banks should consider

Banks entering BaaS as sponsors should ask whether their risk and compliance teams can grow as fast as the programmes they take on. Concentration is another concern: a few large partners can account for most of a bank's deposits, which complicates liquidity planning, and consumer complaint handling and fraud monitoring must work across the partner's customer base, not only the bank's own branches.

Regulation outside the United States

In the European Union, the payment services framework (PSD2, with a successor proposed) and the Digital Operational Resilience Act (DORA), which has applied since January 2025, place requirements on firms that rely on outside technology providers, including expectations on oversight, testing and exit plans. In the United Kingdom, the Financial Conduct Authority has focused on how firms safeguard customer funds. The details differ, but the direction is consistent: regulators expect whoever is responsible for customers to understand and control the whole chain.

Frequently asked questions

Can any company offer banking products without a bank charter?

It can offer them by partnering with a licensed institution, which holds the money and carries regulatory responsibility. The company needs to be clear to customers about which firm is the bank and which is the app, and its marketing should not suggest otherwise.

Are funds in a fintech app protected by deposit insurance?

Deposit insurance covers the failure of an insured bank. Coverage for money held through an app depends on how the account is structured and how well records are kept. It does not protect against the failure of the fintech itself.

What is the difference between BaaS and embedded finance?

BaaS is the infrastructure supplied by a bank or platform. Embedded finance is the product experience the customer sees inside a non-financial app. One is the plumbing; the other is the tap.

Is the BaaS model finished after the 2024 failures?

No, but it is more cautious. Expect more direct bank relationships, stricter oversight of partners, better ledger controls and fewer layers between the customer and the licensed institution.

Sources and further reading

  • Federal Deposit Insurance Corporation, proposed rule on recordkeeping for custodial accounts with transactional features (2024), on fdic.gov.
  • Board of Governors of the Federal Reserve System, Regulation II (Debit Card Interchange Fees and Routing), on federalreserve.gov.
  • Office of the Comptroller of the Currency, bulletins on third-party relationships and risk management, on occ.gov.
  • European Union, Regulation (EU) 2022/2554 (DORA), on eur-lex.europa.eu.

Rules, enforcement actions and company details are drawn from public information and can change; verify against the sources above. This article is general information, not financial or legal advice.

The information provided is for educational and informational purposes only and does not constitute financial, investment, tax, or legal advice.