Neobank

A neobank is a company that provides banking services accessed entirely online. The most useful definition is the U.S. Treasury's, published in its November 2022 report Assessing the Impact of New Entrant Nonbank Firms on Competition in Consumer Finance Markets, because it says out loud that the category contains two different things: "Neobank means a technology company that provides banking services that are accessed exclusively online. Such companies may be digital only-IDIs without traditional physical branch networks or fintech firms that provide a digital consumer interface, such as a mobile app, through which they offer financial services in arrangements with IDIs."

"IDI" is an insured depository institution: a chartered, examined, insured bank. So the first species is a bank without branches. The second is not a bank at all; it is a company whose app you use, with an arrangement behind it under which an actual bank holds the money. Treasury names the second kind separately in its own analysis, calling them "non-bank neobanks."

Nothing in the brand name, the app, or the phrase "banking services" tells a customer which species they are dealing with. That is the whole practical content of this page, because the two behave identically until something goes wrong.

Why the split matters, in one sentence. Deposit insurance covers the failure of an insured bank. Where the app is itself the insured bank, that is the end of the analysis. Where the app is a technology company placing customer money at a partner bank, the coverage still attaches to the bank, and the question becomes whether the records establish whose money is whose. The fintech page teaches that mechanism in full and it is not repeated here; the FDIC insurance page carries the limit and the ownership categories.

The rule that binds a non-bank making claims about FDIC coverage. 12 CFR part 328 subpart B is not addressed to banks. Its scope provision, 12 CFR 328.100, applies to "any person" who falsely represents that a deposit is FDIC-insured, knowingly misrepresents that it is insured or the extent or manner of insurance, or aids and abets someone doing so. "Person" is defined to include any corporation or other entity.

The operative prohibition, 12 CFR 328.102, then does three things a consumer can check on an app's own screens.

It bars a firm from using FDIC-associated terms in its business name to imply that an uninsured product is insured.

It treats a statement as materially incomplete where a person other than an insured bank represents that a product is FDIC-insured and "fails to clearly and conspicuously identify the insured depository institution(s) with which the representing party has a direct or indirect business relationship for the placement of deposits and into which the consumer's deposits may be placed." That is the origin of the "Banking services provided by [Bank], Member FDIC" line at the bottom of these apps: it is not branding, it is the identification the rule requires.

And it treats as materially incomplete a statement that "fails to clearly and conspicuously disclose that the person is not an FDIC-insured depository institution and that FDIC insurance only covers the failure of the FDIC-insured depository institution," and separately a statement about pass-through coverage that "fails to clearly and conspicuously disclose that certain conditions must be satisfied for pass-through deposit insurance coverage to apply."

So an app that says "FDIC insured" and nothing else is not complying with the rule, and the missing sentences are exactly the ones a customer needs.

The case that shows what the middle layer can do, told from the FDIC's own account. In its October 2024 proposed recordkeeping rule the FDIC set out the Synapse failure at length. Synapse Financial Technologies was a "middleware provider" whose software "bridged the information technology systems of fintech companies and IDIs," including "opening and managing deposit accounts, issuing debit and credit cards, and facilitating payments for customers." In those arrangements, the FDIC records, "fintech companies developed user interfaces and application logic, and importantly, maintained the ledgers of their customers, including the deposit amounts attributed to each individual customer."

Synapse filed for bankruptcy in late April 2024. In early May one partner bank "froze deposits that had been placed at the IDI through relationships with Synapse and the fintech companies that Synapse serviced," stating that it did so "because Synapse denied the IDI access to an essential system through which the IDI accessed information on end users, deposits, and transactions." Consumers could not reach their money for months. The FDIC's consumer assistance center received "more than a thousand inquiries, complaints, and concerns" from consumers about it. A bankruptcy trustee appointed in May 2024 "had difficulty obtaining access to Synapse's data, due in part to Synapse's termination of its employees, including employees who held credentials necessary to access systems." And the trustee "indicated that the deposits at the IDIs appear to be insufficient to cover the amounts owed by the fintech companies to their customers."

No insured bank failed. Deposit insurance was never triggered, because the event that triggers it did not happen. The loss of access came entirely from the records in the middle layer. That is the precise risk the two-species definition points at, and it is a different risk from the one deposit insurance is designed to cover.

It was not the first instance. The same FDIC document notes that in 2022 Voyager Digital "falsely represented that customer funds held with Voyager were insured by the FDIC up to $250,000 in the event of Voyager's failure, not just the failure of the IDI where Voyager deposited customer funds," and that when Voyager entered bankruptcy many customers could not access their accounts.

What the FDIC proposed, and what it has not done. The October 2024 rule would have required insured banks holding certain custodial deposit accounts to maintain records identifying the beneficial owners. Measured against the Code of Federal Regulations on 2026-08-28, no such part appears in title 12: it remains a proposal. What is in force is part 328 subpart B, above, and the ordinary deposit insurance rules.

In the first species the company holds a bank charter, is examined, and is insured. A deposit is a deposit at that bank.

In the second the customer's money moves from their employer or their old bank into an account the technology company arranges at a partner bank, often pooled with other customers' money, with the ledger of who owns what maintained by the technology company or a middleware provider. The customer's app balance is that ledger's answer.

A hypothetical example of the consequence people miss, using the deposit insurance limit of $250,000 per depositor, per insured bank, per ownership category. Ravi holds $180,000 at one app and $140,000 at a second, reasoning that two institutions means two coverage limits. Both apps place deposits at the same partner bank.

The limit attaches to the bank, not to the brand. His total at that insured bank in that ownership category is $180,000 + $140,000 = $320,000.

Coverage is $250,000, so $320,000 − $250,000 = $70,000 sits outside it if the bank fails, even though neither individual balance exceeds the limit.

This is why the disclosure rule reads the way it does. 12 CFR 328.102(b)(5)(i) requires a non-bank representing that a product is FDIC-insured to identify the insured institutions "into which the consumer's deposits may be placed." Without that identification Ravi cannot perform the addition above, which is the point of requiring it. Some apps place deposits across a network of banks precisely to spread the limit; that arrangement also depends on records, and the same disclosure rule applies.

And a separate failure mode sits alongside it. Nothing in the arithmetic above addresses the Synapse case, where no bank failed at all and the problem was that nobody could establish whose money was whose.

Pros

• No branch network to fund, which is part of why these institutions compete on price and on features.
• The first species is an ordinary insured bank in every legal respect, so nothing about the absence of branches changes the deposit insurance analysis.
• Federal rules require a non-bank making FDIC claims to name the insured banks involved and to say it is not one, so the information needed to evaluate the arrangement has to be on the page.
• Many of these firms specialize in customer segments that larger institutions serve poorly, which Treasury records as a competitive effect.

Cons

• The word covers two legally different things, and the brand name does not tell you which one you are using.
• Where the app is not the bank, deposit insurance still turns on the bank, and reaching your money depends on records maintained by parties you did not choose.
• Deposit insurance does not cover the failure of a technology company. The Synapse case froze consumer funds for months without any bank failing.
• Balances placed at the same partner bank through different apps share one coverage limit, and a customer cannot detect that without the disclosure.
• Treasury records that the CFPB has received numerous complaints about certain non-bank neobanks involving sudden account closures and loss of access to funds.
• The recordkeeping rule proposed after Synapse has not been adopted, so the protection that failure pointed at does not yet exist as a rule.