Are challenger banks real banks?

The question recurs in every consumer-banking newsletter, every personal-finance subreddit, every conversation between a sceptical parent and a younger relative who has just opened a checking account with an app. Is Chime a bank? Is SoFi a bank? Is the brand on the front of the debit card the institution legally holding the deposit, or is something more complicated going on behind it?

The legal answer to "is this a bank" is precise and almost always no for the consumer-app brands that have grown in the past decade. The practical answer to "does it matter that it isn't a bank" is messier and depends on what the consumer actually needs from the relationship. This essay walks through both — first the legal posture in detail, then the practical implications, then the counter-argument that the legal distinction matters less than the legal precision suggests.

The legal answer

In the United States, a "bank" is a chartered institution authorized to take deposits and make loans, supervised by a state or federal banking regulator, and (in the consumer-facing case) insured by the FDIC. The federal definition lives at 12 U.S.C. §1813; the practical definition is whether an entity holds a state or federal bank charter on the FDIC's list of insured depository institutions.

By that test, the major consumer-facing neobanks are not banks. Chime is a financial-technology company with deposits held at partner banks (historically Bancorp Bank and Stride Bank). Cash App is a service of Block, Inc., a registered money transmitter, with cash-related deposit features held at partner banks (Sutton Bank and Lincoln Savings Bank). Varo Bank is one of the few exceptions — it obtained its own national-bank charter from the OCC in 2020, making it a bank in the full legal sense. SoFi obtained a national-bank charter in 2022 through its acquisition of Golden Pacific Bancorp, making SoFi Bank also a bank in the full legal sense. The rest of the major consumer-facing neobank brands are not chartered banks; they are fintech companies operating through partner-bank arrangements as described in challenger banks and neobanks and banking-as-a-service.

The use of the word "bank" in marketing materials by entities that are not banks is legally constrained. Federal and most state laws restrict the use of "bank," "banking," "trust," and related terms in trade names to chartered institutions. The neobank brands that do not hold charters typically navigate this by using "banking services" rather than "banking" in their core marketing copy, by clearly disclosing the partner-bank arrangement in fine print, and by avoiding direct claims to be a bank. The legal nuance is real but mostly invisible to consumers; the marketing copy reads as if these companies are banks because consumers understand them to be banks regardless of the formal disclosure.

The federal-charter exceptions — Varo, SoFi, and the small number of other fintechs that have obtained their own charters — are themselves instructive. Each took several years, navigated substantial regulatory scrutiny, accepted the capital and liquidity requirements that come with a charter, and made the deliberate choice that holding a charter directly was worth the regulatory cost. The fact that the rest of the fintech sector has not followed indicates that the partner-bank model offers economics most fintech operators prefer over the discipline of operating their own bank.

What the partner-bank structure produces

For a consumer using a partner-bank fintech product, the legal relationships are:

• The consumer's account is opened at the partner bank, typically in the consumer's name (for "for benefit of" structures, the account is opened at the partner bank in the consumer's name with the fintech as agent).
• The partner bank is the FDIC-insured depository institution and the legal counterparty for the deposit. Pass-through coverage applies up to the standard $250,000 per ownership category.
• The fintech provides the user interface, the customer-service function (primarily), the brand, and the value-added features.
• The middleware platform (if one is involved) provides the technology layer that connects the fintech's interface to the partner bank's systems and maintains the per-consumer ledger.

For most consumer purposes most of the time, the partner-bank structure operates indistinguishably from a directly-chartered bank. The consumer's deposit is FDIC-insured. Their debit-card transactions are governed by Regulation E. Their direct-deposit payroll arrives the same way. The bank's underlying balance-sheet management is invisible.

The structure becomes consequential in specific situations. If the fintech itself fails — operationally, financially, or because of regulatory action — the consumer's funds may be locked in dispute for months while the partner bank's records are reconciled, the bankruptcy trustee determines entitlements, and the funds are released. If the middleware platform fails — as Synapse did in 2024 — the same dynamic plays out, with the additional complication that the consumer-level records may be incomplete or contested. The legal protection of the deposit (FDIC insurance) does not protect against operational failure of the fintech or middleware layer; that is a separate risk the partner-bank structure introduces.

The 2024 Synapse case as worked example

The Synapse Financial Technologies bankruptcy in April 2024 produced the clearest example of where the legal-versus-practical distinction matters. Synapse was a banking-as-a-service middleware platform serving more than 100 fintech client brands; its consumer clients included Yotta (a prize-linked-savings fintech), Juno (a checking-and-savings fintech), and others. The brands' marketing emphasized FDIC insurance at the partner banks (principally Evolve Bank & Trust); consumers reasonably understood their funds to be safe.

When Synapse entered bankruptcy, it became apparent that the records of which consumer was owed what — held in Synapse's ledger system rather than in the partner banks' records — were not fully reconciled to the deposit balances actually held at the partner banks. The discrepancy was material; estimates of the unreconciled gap ranged from $65 million to $96 million across the affected programs. The bankruptcy trustee, the partner banks, and the FDIC worked through reconciliation procedures over many months; many affected consumers eventually recovered some portion of their funds, but the recovery was incomplete for some and substantially delayed for many.

The structural point is that the FDIC insurance worked exactly as designed at the partner-bank level — none of the partner banks failed, and none of the deposits the partner banks held were at risk of FDIC loss. What failed was the layer between the consumer and the partner bank, and the FDIC's coverage does not protect against that failure. The consumers' practical experience of locked accounts and partial recovery happened despite, not because of, the legal structure they had been told to rely on.

The practical answer

So: are challenger banks real banks? For ordinary day-to-day use — direct deposit, bill pay, debit-card spending, savings — the partner-bank-structured neobank operates much like a directly-chartered bank, and the consumer's experience is essentially equivalent. For the specific scenarios where the structural difference matters — operational failure of the fintech or middleware, complex pass-through-coverage reliance at larger balances, dispute resolution that requires the chartered bank's direct involvement — the partner-bank structure introduces friction and risk that a directly-chartered bank does not.

For most consumers using neobanks with modest balances, the practical answer is that the partner-bank structure works fine and the legal distinction does not matter. For consumers with larger balances who are relying on pass-through coverage for amounts approaching the $250,000 per-bank limit, the legal structure matters because pass-through coverage's recordkeeping conditions are operationally fragile. For consumers using more complex sweep arrangements that distribute funds across multiple partner banks, the structure matters because the FDIC's bank-by-bank coverage limit is meaningful in operation only if the sweep recordkeeping is reliable.

The counter-argument

The strongest counter-argument to the legal-distinction emphasis is that for the consumer use cases most neobanks actually serve — basic checking, savings, debit-card spending, P2P transfers — the legal distinction is functionally irrelevant. The partner-bank structure operationalizes regulated banking services through a different distribution model, but the substantive protections (FDIC insurance, Regulation E, Regulation DD, the BSA framework, Regulation V) apply with the same force as at a directly-chartered bank. The legal pedantry of "but it's not really a bank" misses that consumers experience the services as banking services and that the regulatory framework treats them as banking services.

There is force to this. A Chime customer experiencing an unauthorized debit-card transaction has the same Regulation E protections as a Chase customer. The partner bank's responsibility for the dispute is the same as Chase's. The customer's recovery, in the standard case, is the same. The fact that Chime is technically not the bank but rather the agent of the partner bank does not change the consumer's substantive rights.

The argument starts to break down in the edge cases. A Chase customer disputing a transaction does so through Chase; the resolution depends on Chase's processes, but the chain of responsibility is short. A Chime customer disputing a transaction may interact with Chime's customer service, which interacts with the partner bank's compliance team, which interacts with the network's dispute system. The interaction layers introduce friction that can become consequential in non-routine cases. And the 2024 Synapse case demonstrated that the layers can produce loss even where each individual layer is operating within its design.

The counter-argument also understates the asymmetry in operational maturity. Chartered banks have decades of experience with the operational requirements of consumer deposit-taking; the fintech sector is younger, with operational practices that are still maturing. The 2024 Synapse failure was an extreme case, but it was an extreme case in a sector where less-extreme operational failures (account-opening difficulties, customer-service unresponsiveness, dispute-resolution delay) have been a recurring source of CFPB attention.

What this implies

The legal answer is that most neobanks are not banks in the strict sense. The practical answer is that for the typical use case at modest balances, this does not produce a meaningfully different consumer experience. The practical answer at larger balances or in non-routine cases is that the structural difference can matter.

The substantive consumer-protection question — whether the U.S. should require non-bank entities that hold deposits or offer deposit-like services to operate under bank-equivalent regulation — is contested and likely to be the subject of continued attention. The post-Synapse regulatory tightening has substantially raised the bar for partner-bank arrangements; the trajectory suggests that the practical gap between chartered-bank operation and partner-bank-structured operation may narrow over time. The legal distinction will remain.

For a consumer evaluating a specific neobank product, the practical questions are the ones identified in challenger banks and neobanks: who is the partner bank, is the account in the consumer's name at that bank, is the pass-through coverage properly structured, and how would the consumer's funds be accessible if the fintech failed. The marketing emphasis on FDIC insurance is correct as far as it goes; the practical extent of the consumer's protection depends on the operational architecture behind the brand. For most consumers most of the time, the answer is "good enough"; the case is for being informed about when it might not be.