What the Synapse Collapse Taught Us About Fintech Risk

Last updated September 17, 2026.

In spring 2024, customers of several savings and banking apps opened their accounts to find their money frozen. No bank had failed. Instead, a little-known middleware company called Synapse had collapsed, and nobody could quickly prove who owned what. More than two years later, some of those customers are still waiting to be made whole. Here's what happened, where things stand, and what it means for anyone who uses or builds fintech.

Key takeaways

• Synapse was a Banking-as-a-Service (BaaS) middleware company connecting fintech apps to partner banks. It filed for bankruptcy on April 22, 2024 [1].
• The CFPB alleged a $60 million to $90 million gap between Synapse's records and its partner banks' records [1].
• FDIC insurance didn't help, because no bank failed; insurance covers bank failure, not a middleware firm's broken ledger [2].
• The CFPB has allocated $55.2 million from its Civil Penalty Fund for victims, but as of late August 2026, payment timing and amounts were still undetermined [3][4].

First, what was Synapse?

Synapse Financial Technologies sat in the middle of the BaaS stack. Consumer apps, including the savings app Yotta, the crypto-investing app Juno, and the teen banking app Copper, used Synapse's APIs to offer accounts and cards without becoming banks themselves [5]. Synapse, in turn, worked with FDIC-insured partner banks, including Evolve Bank & Trust, Lineage Bank, AMG National Trust Bank, and American Bank [5].

Customer funds were typically held in pooled "for benefit of" (FBO) accounts at those banks. The banks saw large omnibus balances. Synapse's ledger was supposed to show how much of each pool belonged to each end user. Related field note

Timeline: from bankruptcy to 2026

What went wrong

1. The ledger didn't match the bank

The core failure was reconciliation, the routine process of matching one set of records against another. The CFPB's complaint alleged Synapse failed to "maintain adequate records of the location of consumers' funds and failing to ensure those records matched the records maintained by its partnering banks" [1]. When Synapse's systems went down, the banks couldn't simply read off each customer's balance.

2. Money moved among banks

Funds had been moved among multiple partner banks over time, which made the reconstruction slow. Partner banks paid out what they believed they owed, but customers reported receiving far less than their app balances [5].

3. Deposit insurance wasn't designed for this

FDIC insurance protects depositors when an insured bank fails [2]. Pass-through coverage depends on accurate records showing each owner's interest [11]. When the problem is a non-bank intermediary's records, there is no FDIC payout to trigger. Customers had "insured" funds in name, but no fast way to reach them.

4. Nobody owned the whole problem

Each party (app, middleware, banks, bankruptcy trustee) controlled only part of the data and part of the responsibility. The bankruptcy estate itself was described as administratively insolvent, and the case was dismissed after, as one bankruptcy attorney put it, "the CFPB coming in and taking ownership of the payments back to the affected consumers" [10].

Where refunds stand as of September 2026

• Partner banks ran their own reconciliation and disbursement processes in 2024 [9].
• CFPB allocations: The CFPB's Civil Penalty Fund, which is funded by penalties from other enforcement cases, allocated a total of $55,214,058 across two rounds [3].
• Payments still pending: Yotta's August 31, 2026 update said the CFPB had not yet determined "the exact timing and amounts of payments" [4]. We found no confirmation that individual payments have been sent as of this update.
• Uncertainty: Reporting in late 2025 noted doubts about the CFPB's capacity to follow through amid efforts by the administration to shrink the agency [12].

If you were affected, watch official CFPB communications and be wary of anyone asking for fees to "recover" your money. Related field note

Lessons for consumers

1. "FDIC insured" has fine print. It usually means the partner bank is insured and your deposit may qualify for pass-through coverage, not that the app itself is protected.
2. Know your bank's name. If you can't find which bank holds your money, that's a signal to dig deeper.
3. Don't treat an app as your only account. Keeping emergency funds directly at an insured bank or credit union limits disruption if an intermediary fails.
4. Save statements. Your own records can matter in a reconciliation.
5. High yields don't equal high safety. Rewards or attractive rates say nothing about the plumbing underneath.

Related field note

Lessons for founders and product teams

• Own your ledger, or verify it daily. If a middleware provider keeps the books, you need independent access to data and daily reconciliation against the bank's records.
• Plan for provider failure. Have a documented wind-down plan: how would customers get their money if your BaaS provider disappeared tomorrow?
• Choose partners by controls, not only price. Regulators have made clear, through the 2024 joint statement, that banks remain responsible for third-party arrangements [7].
• Be precise in insurance marketing. Misleading deposit-insurance claims draw regulatory scrutiny. Related field note
• Expect more direct bank relationships, or charters. Some fintechs have responded by seeking their own bank charters, a trend that accelerated in 2026 [13]. Related field note

What changed in regulation, and what didn't

Regulators responded mainly with supervision rather than new final rules:

• The 2024 joint statement reminded banks of existing risk-management expectations without creating new requirements [7].
• The FDIC's October 2024 custodial-account recordkeeping proposal would require banks to keep better records of beneficial owners in custodial accounts [8]. We could not confirm it has been finalized as of September 17, 2026; its status should be checked on the FDIC's and Federal Register's sites.
• The CFPB used a creative legal path, a $1 penalty, to tap its victims' fund [1][3].

The larger question, who guarantees that ledgers in multi-party fintech chains are correct, remains largely a matter of contracts, bank supervision, and industry practice.

FAQ

What happened to Synapse? Synapse, a BaaS middleware company, filed for bankruptcy on April 22, 2024. Its records didn't match partner banks' records, leaving end users of several apps unable to access funds [1].

Why didn't FDIC insurance cover Synapse customers? FDIC insurance pays when an insured bank fails. The partner banks didn't fail; the problem was a non-bank's recordkeeping [2].

How much money was missing? The CFPB estimated a shortfall of $60 million to $90 million between Synapse's records and bank records [1]. Other reports cited up to $95 million locked [10].

Is the CFPB paying Synapse victims? The CFPB allocated $55.2 million from its Civil Penalty Fund (November 2025 and May 2026), but as of August 31, 2026, payment timing and amounts were not yet determined [3][4].

Which apps were affected? Reported affected apps include Yotta, Juno, and Copper, among others [5].

Could this happen again? Similar risks exist wherever a non-bank keeps the only detailed ledger of pooled customer funds. Daily reconciliation, clear disclosures, and stronger bank oversight reduce, but don't eliminate, that risk.

Sources

1. Consumer Financial Protection Bureau, "Synapse Financial Technologies, Inc." (enforcement action), https://www.consumerfinance.gov/enforcement/actions/synapse-financial-technologies-inc/, accessed 2026-09-17.
2. FDIC, "Understanding Deposit Insurance," https://www.fdic.gov/resources/deposit-insurance/understanding-deposit-insurance, accessed 2026-09-17.
3. Consumer Financial Protection Bureau, "Civil Penalty Fund," https://www.consumerfinance.gov/enforcement/payments-harmed-consumers/civil-penalty-fund/, accessed 2026-09-17.
4. Yotta Technologies, "Payment Processing Updates," https://www.withyotta.com/payment-processing-updates, update dated Aug. 31, 2026, accessed 2026-09-17. (Affected company; not a regulator.)
5. American Banker, "CFPB to refund $46 million to Synapse victims," https://www.americanbanker.com/news/cfpb-to-refund-46-million-to-synapse-victims, Dec. 22, 2025, accessed 2026-09-17.
6. Federal Reserve Board, "Federal Reserve Board issues an enforcement action against Evolve Bancorp, Inc. and Evolve Bank & Trust," https://www.federalreserve.gov/newsevents/pressreleases/enforcement20240614a.htm, June 14, 2024, accessed 2026-09-17.
7. Office of the Comptroller of the Currency, "Agencies Remind Banks of Potential Risks Associated with Third-Party Deposit Arrangements," https://occ.gov/news-issuances/news-releases/2024/nr-ia-2024-85.html, July 25, 2024, accessed 2026-09-17.
8. Federal Register, "Recordkeeping for Custodial Accounts" (proposed rule), https://www.federalregister.gov/documents/2024/10/02/2024-22565/recordkeeping-for-custodial-accounts, Oct. 2, 2024, accessed 2026-09-17.
9. Evolve Bank & Trust, "Evolve Bank Announces Process to Return Synapse Brokerage's End User Funds," https://www.getevolved.com/media-release/evolve-bank-announces-process-to-return-synapse-brokerages-end-user-funds-expects-to-begin-disbursing-funds-in-november/, Oct. 23, 2024, accessed 2026-09-17. (Company source.)
10. Banking Dive, "Synapse bankruptcy case tossed," https://www.bankingdive.com/news/synapse-bankruptcy-case-tossed/805575/, Nov. 14, 2025, accessed 2026-09-17.
11. Electronic Code of Federal Regulations, 12 CFR 330.5, https://www.ecfr.gov/current/title-12/chapter-III/subchapter-B/part-330/section-330.5, accessed 2026-09-17.
12. Bloomberg Law, "CFPB Payments to Synapse Victims Clouded by Questions Over Fund," https://news.bloomberglaw.com/banking-law/cfpb-payments-to-synapse-victims-clouded-by-questions-over-fund, Nov. 21, 2025, accessed 2026-09-17.
13. American Banker, "Fintechs asking for, and receiving, bank charters in 2026," https://www.americanbanker.com/news/fintechs-asking-for-and-receiving-bank-charters-in-2026, Apr. 28, 2026 (updated Sept. 4, 2026), accessed 2026-09-17.

Disclaimer: This article is for educational purposes only and is not financial, legal, or tax advice. Details of refunds and legal proceedings may change; affected consumers should rely on official CFPB and court communications and verify any claims process directly.