"FDIC-insured" felt like a guarantee — until it wasn't, for over 100,000 real customers, because the insurance was never actually the weak point.
It depends almost entirely on the quality of the fintech's own recordkeeping, which is a genuinely uncomfortable answer because it's not something you can easily check yourself before signing up. In the US, "FDIC-insured" usually refers to the partner bank holding pooled customer funds behind the scenes, not the fintech app itself — if that fintech's internal ledger tracking who owns what breaks down, insurance doesn't automatically make you whole quickly, as over 100,000 customers of the collapsed middleware firm Synapse discovered in 2024. In the UK, e-money and payment institutions are legally required to "safeguard" your funds separately from their own — kept apart from the company's operating money — with meaningfully stricter enforcement of that rule arriving from May 2026.
| United States | United Kingdom | |
|---|---|---|
| Core protection mechanism | FDIC insurance on the underlying partner bank's deposits — up to $250,000 per depositor, per bank, per ownership category, if your individual ownership is properly recorded | "Safeguarding" requirement under the Electronic Money Regulations 2011 / Payment Services Regulations 2017, requiring customer funds be kept segregated from the firm's own money |
| What actually failed in a real case | Synapse (a banking-as-a-service middleware provider) filed for Chapter 11 in April 2024; the underlying banks were genuinely FDIC-insured, but Synapse's own ledger reconciling which customer owned what money broke down, leaving 100,000+ customers unable to access a combined $265+ million for months, some recovering only a fraction | No equivalent scale of failure has occurred under the current regime, but regulators have flagged historical safeguarding shortfalls as the reason for tightening the rules |
| Regulatory response | FDIC proposed the "Synapse rule" in 2024 requiring banks to maintain accurate records of individual customers behind pooled/custodial accounts — as of mid-2026, this remains proposed, not finalized | New Supplementary Regime rules take effect 7 May 2026: daily reconciliations, a maintained "resolution pack" retrievable within 48 hours, and stricter record-keeping standards for payment and e-money firms |
| Does deposit insurance itself cover the fintech? | No — the fintech is not a bank and is not itself FDIC-insured; insurance only ever covered the partner bank underneath it | The Financial Services Compensation Scheme (FSCS) does not currently cover e-money/payment institution failures directly, though if the safeguarding bank itself fails, the FSCS may be able to "look through" to compensate customers |
The Synapse case is worth understanding in some detail, because it's the clearest illustration available of exactly how this can go wrong. Synapse itself wasn't a bank — it was "banking-as-a-service" middleware sitting between consumer-facing apps (like Yotta and Juno) and real FDIC-insured banks (like Evolve Bank & Trust). Marketing from the consumer apps consistently emphasized FDIC insurance, and technically the underlying banks were insured — but the insurance protects against the bank failing, not against the middleware's bookkeeping falling apart. When Synapse's ledger collapsed, nobody could reliably determine which customer's money was where, and resolution dragged on for well over a year, with the CFPB eventually allocating $46.2 million from its Civil Penalty Fund toward victims in November 2025 — partial compensation, arriving over 18 months after the initial collapse.
Direct FDIC-insured bank accounts, and UK e-money institutions properly complying with safeguarding requirements (especially post-May 2026 with daily reconciliation), represent the more protected end of this spectrum.
This is precisely the Synapse pattern. The marketing wasn't technically false — the partner banks were genuinely insured — but it created a false sense of security about the actual point of failure, which was the middleware company's own recordkeeping, not the bank's solvency.
A fintech that's transparent about exactly which FDIC-insured bank holds your funds, and how its own ledger reconciles with that bank's records, is a meaningfully different risk profile than one that's vague about the underlying banking relationship.
Crypto holdings generally fall outside both FDIC insurance and UK safeguarding rules entirely, since cryptocurrency isn't a bank deposit or e-money in the regulatory sense. If a crypto exchange or platform becomes insolvent, customer crypto holdings are typically treated as part of the bankruptcy estate, subject to lengthy court proceedings, with no deposit-insurance-style backstop in either country.
"Your funds are held at [named partner bank], which is FDIC-insured. We reconcile our records against the bank's daily to ensure accurate individual balances."
A blanket "FDIC-insured" badge with no disclosure of which bank actually holds the funds, or how (or whether) the fintech's own ledger is reconciled against that bank's records — technically not false, but leaving out the exact detail that mattered most when Synapse failed.
Use our Fintech Safety Checklist to verify a provider's partner bank disclosure and safeguarding status before depositing significant funds.
Explore Crypto & Fintech tools →