Is your Venmo, Cash App, or PayPal balance actually FDIC insured?

Venmo, Cash App, and PayPal all use the letters "FDIC insured" somewhere in their marketing or fine print — and it's easy to read that as "my balance is protected exactly like money in a bank account." It usually isn't, at least not automatically. The protection those apps advertise is called pass-through deposit insurance, and it only applies when the app and its bank meet specific conditions the FDIC has spelled out. Miss one of those conditions, and the "FDIC insured" label on the app's homepage may not cover the balance sitting in your account the way you'd expect.

What "pass-through" insurance actually means

Payment apps aren't banks. When you load money into Venmo or Cash App, that money typically moves into an account the app itself holds at a partner bank — not an account titled in your name. For your share of that pooled account to carry FDIC coverage, the arrangement has to work the way the FDIC's pass-through deposit insurance rules require. All three of these have to be true:

1. The money is actually yours. You — the consumer — have to be the true legal owner of the funds, not the app itself.
2. The bank's own records show it's holding the money for someone else. The account has to be titled to reflect its "agency" nature — something like "XYZ App as Custodian for Customers," not a plain company account.
3. Someone's records show exactly who owns what. The bank's records, the app's records, or both together have to identify each individual customer and their specific dollar share of the pooled balance.

If all three hold, your share of the pooled account is generally insured up to $250,000, separately from your other deposits at that same bank, per the standard FDIC ownership-category rules covered in how FDIC insurance actually works.

What happens if those conditions aren't met

This is the part that catches people off guard. Per the FDIC's own consumer guidance on banking with third-party apps, "funds you send to a nonbank company are not eligible for FDIC insurance until the company deposits them in an FDIC-insured bank and after other conditions are met." If the recordkeeping test above isn't satisfied — say, the bank's records don't clearly break out who owns what — the money in that pooled account is insured only as a deposit of the app itself, combined with everything else the app holds there, capped at $250,000 total for the whole company. Not $250,000 per user. $250,000 divided among however many customers' money happens to be sitting in that account when the bank fails.

The risk isn't just "your bank fails" — it's "your app fails"

FDIC insurance protects against bank failures. It does not protect against the app or the fintech company running the app going out of business. The FDIC says this directly: "FDIC deposit insurance does not protect against the insolvency or bankruptcy of a nonbank company." If a payment app or the "middleware" technology layer connecting it to its partner bank collapses — even if the actual bank stays open and solvent — your money can still become inaccessible while a bankruptcy court and the bank try to reconstruct whose money is whose.

That's not a hypothetical. It's exactly the scenario that led the FDIC to propose new rules in the first place. On September 17, 2024, the FDIC proposed recordkeeping requirements for banks holding these pooled "for benefit of" customer accounts, citing the 2024 collapse of fintech-middleware firm Synapse as the case that prompted the rulemaking. Then-Chairman Martin Gruenberg framed the underlying problem directly: banks need to know "whether the deposit has actually been placed in the banks, and that the banks are able to provide the depositor their funds even if the third party fails." The proposal would require banks to maintain records identifying each beneficial owner and reconcile balances daily. As of this writing, check the FDIC's rulemaking docket (RIN 3064-AG07) for the rule's current status before assuming it's in effect.

The CFPB has reached the same conclusion from the consumer-protection side. In its Issue Spotlight on payment-app deposit insurance, the bureau notes that funds stored through payment apps "often are not placed in an account at a bank or credit union and lack individual deposit insurance coverage," and that those balances "can be at risk of loss in the event of financial distress or failure of the entity operating the mobile payment platform" — language that describes the app's own failure, not the bank's.

How to actually check your own balance

You don't have to guess. The FDIC's advice is straightforward: read the app's own disclosures and terms of service, since that's where a company states whether — and how — it structures its accounts to meet the pass-through test.

• Look for specific insurance language, not just the FDIC logo. A statement like "funds are held at [named bank], FDIC Member" with a description of how individual balances are tracked is a good sign. A vague "FDIC insured" badge with no named partner bank is not.
• Don't treat a large balance sitting in an app the same as a bank account. If you're carrying a meaningful cash balance for more than a few days, moving it to an account actually titled in your name at an FDIC-insured bank removes the pass-through question entirely.
• Remember Regulation E doesn't cover this. If you're worried about a scammer taking your money out of one of these apps, that's a different protection — see how Regulation E's fraud-liability rules apply to Zelle, Venmo, and Cash App transfers. This article is about what happens to the balance sitting in the app, not about an unauthorized transfer out of it.

ClearValue Banking is an independent education and comparison publisher, not a bank, payment app, or insurer — we don't hold customer funds or make insurance determinations. If you're deciding where to actually park cash, compare FDIC- and NCUA-insured deposit accounts against a payment app's disclosures before treating the two as equivalent.