NEW YORK — A consumer opens one app, sees one balance and expects one place to call when the money freezes. Underneath, a nonbank platform markets the product, middleware may route deposits and keep a sub-ledger, and a chartered bank holds the funds for benefit of customers. Each firm answers to its own regulator and signs its own contract. Each also has a view on whose ticket a frozen balance is.

Embedded finance sells that split as progress, and for distribution it is: checkout, payroll or a consumer app can offer banking surfaces without anyone building a bank. The split is also how these products fail. When records diverge, support scripts point sideways, because the brand on the screen is usually not the entity that can move the money.

An app can look like one product and still have no single firm accountable when the ledgers disagree.

What Synapse made concrete

Synapse Financial Technologies sat in the middle of that stack. According to the Consumer Financial Protection Bureau’s enforcement action page, Synapse provided technology and software that bridged nonbank fintech platforms offering banking services to consumers and traditional partner banks. On 22 April 2024, Synapse filed for chapter 11 bankruptcy protection.

The Bureau alleged that Synapse violated the Consumer Financial Protection Act by failing to keep adequate records of where consumers’ funds were, and by failing to keep those records matched to partner banks’ books. Partner banks found that the total they held for consumers was less than the total in Synapse’s records, a shortfall the Bureau put between $60 million and $90 million. Consumers could not reach their funds for weeks or months while the banks reconciled, and many did not receive the full amount of their recorded balance. On 21 August 2025 the Bureau filed a complaint and a proposed stipulated final judgment. The court entered the order on 12 September 2025, including injunctive relief and a $1 civil money penalty that opened a path to redress from the civil penalty fund.

What followed was a fight over records. Depositors paid for it. They had used one app, but the legal path ran through a bankrupt middleware firm, several partner banks, bankruptcy trustees and federal enforcement, and none of those parties owned the complaint from start to finish.

What supervisors had already said about complaint duties

US bank supervisors were writing about third-party risk well before Synapse. On 6 June 2023 the Office of the Comptroller of the Currency (OCC), the Federal Reserve Board and the Federal Deposit Insurance Corporation (FDIC) issued interagency guidance on risk management for third-party relationships. Effective contracts, it says, typically specify whether the banking organization or the third party responds to customer complaints or inquiries. If the fintech firm handles complaints, the contract should require timely responses and give the bank enough usable data to analyze their volume, nature and trends. If the bank handles them, the fintech firm must notify the bank promptly. In both cases each side is expected to monitor trends and remediation.

On 25 July 2024 the same three agencies issued a joint statement on bank arrangements with third parties to deliver deposit products. The agencies said it created no new legal duties; it restated that a bank’s use of third parties to perform activities does not diminish the bank’s responsibility to comply with applicable laws and regulations. The same package included a request for information on bank-fintech arrangements covering deposits, payments and lending.

Together, the two documents answer the product pitch. A bank can white-label the screen, but liability for consumer protection, deposit recordkeeping and complaint handling stays inside the regulated perimeter, and a middleware failure does not turn a deposit arrangement into a software problem.

Why the brand on the screen takes the first hit

Customers escalate wherever they already are: they open the app, post the brand name, and file a complaint with the Consumer Financial Protection Bureau naming the company on the card. A bank or program manager may be right that the contract gave day-to-day support to someone else. That does not keep the first public damage off the brand on the card, and examiners can still read complaint quality as evidence about the bank’s third-party program.

The gaps show up in ordinary tickets long before any bankruptcy. A dispute needs transaction data the platform has and the bank does not, or core banking data the platform cannot query in real time; a fraud claim can stall on who has authority to freeze a card that the issuer controls; and a wind-down needs an agreed sequence for moving balances when a partner exits. Each of these is settled, or left unsettled, when the partnership is designed, long before a support agent sees it. Firms that launch embedded products without a written path for first response, decision rights, regulator contact and public communications will, I expect, find the gap when complaint volume spikes. Only then do they learn that nobody agreed a RACI chart (who is responsible, accountable, consulted and informed).

Failure mode What the customer sees Who can actually clear it
Ledger mismatch Balance frozen or wrong Bank + middleware reconciling books
Card authorization error Declines at checkout Issuer processor + program manager
Marketing claim vs contract “FDIC insured” confusion Bank disclosures + platform copy owners
Partner exit / insolvency App still branded, money stuck Bank wind-down, bankruptcy court, agencies

Embedded finance will keep growing because distribution is worth paying for, and the products that last treat complaint ownership as a launch criterion. The brand on the glass can stay unified. Behind it, the contracts and escalation trees have to say who answers the customer and who talks to supervisors, and above all who can move the money once the middleware is gone.

Source notes