Digital banking and payments: Who is liable? Banking-as-a-service and embedded finance

Embedded Finance in 2026: Who Does What and Who Is Responsible

Rate this post

Guide

  • Topic: How embedded finance and banking-as-a-service (BaaS) are structured, and where responsibility sits
  • US model: A licensed sponsor bank provides accounts and is accountable to its regulators, while the fintech brand sits on top
  • Evidence: Between 2022 and 2025 US regulators issued consent orders against seven sponsor banks running BaaS programmes, according to one law-firm summary
  • Open question: The FDIC’s proposed custodial-account recordkeeping rule has not been finalised in the sources we reviewed
  • Takeaway: You can outsource the technology, but not the accountability

Embedded finance puts financial products, such as payments, accounts, cards and lending, inside apps and platforms that are not banks. It makes finance easier to use, but it also raises a plain question: when something goes wrong, who is responsible? This guide sets out the main models and what the failure of a major middleware provider taught the industry.

The main models

Model How it works Who holds the licence
Referral or distribution The app introduces customers to a regulated provider The provider
Banking-as-a-service with a sponsor bank A bank offers accounts, cards and payments through an API, and a non-bank brand embeds them The sponsor bank. For the customer it is an app, but legally it is an account at the partner bank
Own licence The company is itself an e-money, payment or similar institution The company
Agent of a licensed institution The company acts for a regulated firm under that firm’s licence The regulated firm

Who is responsible

In the US sponsor-bank model, one legal summary puts it simply: the partner bank is responsible to the regulator for end-customer funds and compliance, and the fintech is responsible to the bank. There is no separate BaaS regime, and the relationship sits within the general framework for banks’ third-party risk.

Regulators have acted on that. Between 2022 and 2025 the FDIC, OCC and Federal Reserve issued consent orders against seven sponsor banks running BaaS programmes, and treated the absence of a wind-down contingency plan as a violation in itself, according to Shumaker, Loop & Kendrick. One example is the Federal Reserve’s June 2024 order against Evolve Bank & Trust, which cited unsafe and unsound practices in managing fintech partnerships.

The Synapse lesson

  • What happened. Synapse, a middleware provider, connected fintech apps with partner banks. It kept the sub-ledger that tracked each customer’s balance while the money sat in pooled accounts at the banks. When Synapse collapsed in 2024, the ledgers and the banks’ records did not match, and customers could not be reliably matched to their share of the funds, according to the Yale Journal of International Affairs and Shumaker.
  • What was not at stake. One analysis stresses that no bank failed, and that deposit insurance did not apply to the middleware failure.
  • The regulatory response. The FDIC proposed a recordkeeping rule for custodial accounts with transactional features, requiring banks to keep records of beneficial owners and to reconcile daily. Sources differ on its status: Financy Hub and Instnt describe it as still a proposal, while one law-firm summary reports it was withdrawn. Check the FDIC’s site for the latest.
  • A moving target. On September 11, 2026 the OCC, Federal Reserve, FDIC and NCUA proposed new third-party risk guidance that would rescind the 2024 interagency statement, according to Instnt. Sponsor banks may read that as relief, but the principle that a bank remains responsible for its partners’ compliance has not gone away.

A checklist for fintechs and brands

  1. Know where the money sits, and in whose name each account is held.
  2. Keep your own ledger and reconcile it daily against the bank’s records.
  3. Spell out loss allocation in your contract, including what happens if either party fails.
  4. Have a wind-down plan so customers can reach their funds if a partner exits.
  5. Market accurately. Do not imply deposit insurance covers things it does not, a confusion that surrounded Synapse.
  6. Remember that compliance duties follow the bank, and shifting anti-money-laundering work to a fintech does not remove the bank’s duty.
  7. Consider more than one bank partner for critical products.

In the EU, firms in this space are also subject to DORA, which governs how they manage technology providers.

How money flows in a sponsor-bank programme

The sequence below shows why the ledger matters. It describes a common US structure; details differ by programme.

  1. A customer adds $100 in a brand’s app.
  2. The money moves to a pooled custodial account held at the sponsor bank.
  3. The brand, or a middleware provider, records the customer’s $100 in its own ledger.
  4. The bank holds the funds. The ledger says who owns what share of the pool.
  5. Each day, the ledger and the bank’s records should match. When they do not, nobody can say with certainty who is owed what.

Contract clauses to negotiate

Clause Why it matters
Loss allocation Decides who pays when fraud, error or failure causes a loss. Ambiguity here is a frequent source of disputes after a problem
Ledger ownership and access Gives the bank or brand a copy of the records it can read independently
Reconciliation Requires daily matching of end-user balances to funds held
Wind-down and transition Sets out how customers keep access to funds if a partner exits
Compliance duties Allocates anti-money-laundering, sanctions and complaints work, while recognising the bank stays responsible to its regulator
Marketing and insurance claims Controls how deposit insurance and bank status are described to customers

Due diligence for brands choosing a bank partner

  • The bank’s regulatory history, including any public orders or open actions.
  • How many programmes it runs and how well its compliance team is staffed.
  • Its capital strength and ability to support growth.
  • Its approach to reconciliation and who controls the master ledger.
  • Its exit and transition plan if it stops supporting your programme.

Due diligence for banks choosing a brand

  • The brand’s customer base, risk controls and fraud history.
  • Its ability to reconcile balances and its record-keeping.
  • Complaints handling and customer support capacity.
  • Marketing review, especially claims about insurance and returns.
  • Financial strength and a plan to wind down in an orderly way.

Embedded finance beyond banking

The same question, who holds the licence and who answers to the regulator, applies to other products. Embedded payments, lending and insurance each rely on a regulated provider behind the brand. The more the brand shapes the customer’s decisions, the more regulators look at its conduct as well as the licence holder’s.

Frequently asked questions

Is my money insured if the app fails?

Deposit insurance covers the failure of an insured bank, not the failure of a middleware provider, according to the analysis cited above. One legal summary says pass-through coverage to each end depositor depends on correct, itemised records at the bank.

Who handles complaints?

It depends on the programme. The bank remains answerable to its regulator, but the brand is usually the customer’s first contact. The contract should say who resolves what, and customers should be told.

Can a brand hold customer money itself?

Only if it holds the right licence. Otherwise it relies on a regulated bank or institution.

Do these issues apply outside the US?

The details differ, but the principle is similar: someone licensed must answer for customer funds. In the EU, firms in this space are also subject to DORA’s technology-risk rules.

The Funding Journal view

Embedded finance works best when each party can answer three questions without hesitation: who holds the funds, who holds the ledger and who answers to the regulator. The Synapse failure showed what happens when the answers differ between the app, the middleware and the bank. Brands that treat reconciliation, contracts and wind-down plans as product features, not legal footnotes, will be the ones customers can trust.

Sources and further reading

This article is general information, not financial, legal or tax advice. See our disclaimer. Facts last checked October 26, 2026; rules and company details change, so confirm current terms before you act.

Published by The Funding Journal Editorial. Practical, sourced writing on fintech, crowdfunding, investment platforms, SaaS and AI, and the stories of founders who raised capital.

Similar Posts