A California bankruptcy court dismissed Synapse Financial Technologies’ Chapter 11 case on 12 November 2025, closing the book on a corporate failure that spent 19 months exposing how little control US banks had over the fintech middleware sitting between them and their own customers’ money. Synapse filed for bankruptcy protection on 22 April 2024. The Synapse collapse has since reshaped how regulators expect banks to supervise banking-as-a-service, or BaaS, partnerships, in which a bank rents out its charter to non-bank fintechs that build consumer products on top of it.
The Consumer Financial Protection Bureau’s enforcement record states that Synapse’s partnering banks found they held less money for consumers than Synapse’s own records showed, a shortfall of between $60 million and $90 million. Consumers went without access to their funds for weeks or months while the banks reconciled their books against Synapse’s, and many never recovered the full balance their account had shown.
Regulators went after the banks, not just the middleman
Synapse itself had little left to seize once the reconciliation began. The regulatory response fell instead on the banks that had outsourced core account-keeping to it. The Federal Reserve issued a cease and desist order against Evolve Bancorp and Evolve Bank & Trust, of West Memphis, Arkansas, on 14 June 2024, citing deficiencies in the bank’s anti-money laundering, risk management and consumer compliance programmes tied to its fintech partnerships. The Fed’s own release notes that the action is independent of the Synapse bankruptcy proceedings, a distinction regulators drew carefully at the time: Evolve was cited for its own supervisory gaps, not simply for having done business with Synapse.
Separately, an FDIC consent order against Lineage Bank of Franklin, Tennessee, dated 30 January 2024, three months before Synapse’s bankruptcy filing, had already ordered the bank to rebuild its third-party risk management programme for fintech partnerships. The order requires Lineage to build a formal onboarding process for new fintech partners, commission an independent annual risk assessment covering each partner’s financial condition and compliance record, and give its board monthly reporting on account activity running through its banking-as-a-service business line. Read in full, the order describes almost exactly the failures that later surfaced across Synapse’s other bank partners: thin due diligence, weak reconciliation controls, and boards with limited visibility into what their fintech partners were doing with customer money.
A settlement, not a recovery
The CFPB’s own case against Synapse closed quietly compared with the scale of the harm it addressed. The Bureau filed an adversary proceeding on 21 August 2025 alleging Synapse violated the Consumer Financial Protection Act by failing to keep accurate records of where consumers’ money sat and failing to match those records against its partner banks’ own books. The court entered a stipulated judgment on 12 September 2025 that fined Synapse $1, a figure set deliberately low so the Bureau could draw on its Civil Penalty Fund, which pools penalties paid by unconnected companies, to compensate Synapse’s victims instead.
That fund has since paid out toward Synapse in two instalments, according to the CFPB’s own allocation schedule: $46,248,291 set aside on 28 November 2025 and a further $8,965,767 on 29 May 2026, for a combined $55,214,058 earmarked for the end users of fintechs including Yotta and Juno who lost access to their money through Synapse. The Bureau’s published guidance on the fund says distribution timing varies case by case and gives no fixed date for when that money reaches the people it is meant to compensate, more than two years after they were first locked out of their accounts.
The rule Synapse prompted, still not final
Synapse’s collapse produced a specific regulatory proposal built around its own failure. On 17 September 2024 the FDIC’s board voted to propose a new rule, Recordkeeping for Custodial Accounts, that would require banks holding custodial deposit accounts with transactional features to identify each beneficial owner in their own records and reconcile those records against the account balance at the close of every business day. Then-Vice Chairman Travis Hill said in his statement on the proposal that Synapse’s problems “could have been identified much sooner if the partner banks maintained better records and conducted frequent, routine reconciliations.”
More than two years on, the rule remains exactly that: a proposal. The FDIC’s own rulemaking agenda lists it under docket RIN 3064-AG07 with a final rule date still marked undetermined. In March 2025 the agency withdrew three other outstanding proposals, covering brokered deposits, corporate governance and the Change in Bank Control Act. The custodial-accounts proposal was not among them, though it has not moved toward a final rule either, under Hill, who was confirmed as FDIC Chairman on 2 January 2026. For a bank deciding whether to build the daily reconciliation and beneficial-ownership recordkeeping the proposal describes, nothing currently requires it, even though the FDIC’s own account of Synapse’s collapse describes precisely the gap that recordkeeping was designed to close.
The BaaS lesson banks are meant to have learned
For a bank still running, or considering, a banking-as-a-service programme, the enforcement record points to a specific standard rather than a general warning. The Lineage order’s requirements, a documented due diligence process before onboarding any fintech partner, an annual third-party risk assessment covering each partner’s finances and compliance history, and monthly board-level reporting on account activity, describe what supervisors now expect a bank to have in place before it lets a non-bank company touch its ledger. Synapse’s core failure was a recordkeeping gap between what it told its partner banks and what those banks held. Closing that gap on the bank’s own systems, rather than trusting a middleware provider’s numbers, is the specific fix regulators have been enforcing bank by bank, even without a finished rule requiring it. Fintechly has covered the underlying architecture choices behind ledger system design for banks weighing whether to keep that reconciliation work in-house.
A fuller list of infrastructure providers building the reconciliation, ledger and core-banking tools banks are now turning to for that work is on Fintechly’s infrastructure sector directory.
