Insurance attaches to a legal relationship
Pass-through deposit insurance allows qualifying deposits placed through an intermediary to be insured according to the beneficial owners’ interests and ownership categories. It is not a separate insurance category or an extra limit created by an app. The FDIC’s disclosure guidance explains that deposits belonging to the same person in the same ownership capacity at the same bank must be aggregated when applying the $250,000 limit. The current regulation separately states the aggregation principle. [1][5]
That distinction matters whenever a fintech, broker, trustee or other intermediary stands between a customer and an insured bank. A customer may see several brands while funds ultimately sit at one institution. Conversely, one interface may distribute funds among multiple banks. Neither the number of interfaces nor the number of account labels independently answers the coverage question.
This article addresses current ownership and recordkeeping rules reviewed September 27, 2026. It does not assume that a proposed custodial-account rule has become binding, or that every platform using the phrase FDIC insured satisfies all applicable conditions.
What §330.5 requires records to establish
The regulation starts with the bank’s deposit account records as evidence of ownership. For a fiduciary relationship that supports additional insurance, the bank records must disclose that relationship, subject to the rule’s provisions. The relationship’s details and the other parties’ interests must be ascertainable from the bank’s records or qualifying records maintained in good faith and in the regular course of business by the depositor or its recordkeeper. [2]
Multiple layers of intermediaries make that traceability more demanding. Section 330.5 describes methods for documenting multilevel fiduciary relationships; a chain cannot simply end at an omnibus label if the underlying interests needed for coverage remain unidentifiable. [2] The operational task is to connect a dollar at the bank to a legally supported owner and category without relying on an improvised reconstruction after failure.
An ownership ledger should therefore be more than a list of customer names and app balances. It needs legal identity, applicable ownership capacity, bank allocation, effective time, pending movements and a reproducible reconciliation. The exact requirements vary with the arrangement. These recommended data controls support legal analysis; they do not create coverage where the contractual and ownership conditions are absent.
A hypothetical aggregation problem
Assume one individual has $180,000 in a direct single-owner savings account at Bank A and another $100,000 beneficial interest in a qualifying custodial account at the same bank, also in the single-owner category. With no other relevant balances or adjustments, the total is $280,000. The standard $250,000 limit leaves $30,000 above that limit. Opening the second balance through a different brand does not by itself change this calculation.
Suppose a platform instead places the second $100,000 at Bank B. Coverage must then be evaluated at Bank B, including any other deposits the person holds there in the same category. A sweep interface that advertises access to multiple banks still needs accurate allocations and clear treatment of excluded banks. The example assumes all pass-through conditions are met; it is not a guarantee for a particular product.
The lesson for product design is to avoid an isolated-account coverage display when the platform cannot see outside deposits. Show the bank identity, explain aggregation and make the customer’s bank exclusions usable. A displayed coverage estimate should state what information it includes and what the customer must supply.
Insurance and liquidity solve different problems
The FDIC’s deposit-insurance materials describe protection for insured deposits when an insured bank fails. [3] They do not turn a nonbank intermediary into an insured bank or guarantee continuous app access. A platform outage, reconciliation dispute or nonbank failure can impede access even if the underlying bank remains open.
This distinction changes contingency planning. A bank-failure scenario asks how ownership information supports an insurance determination. A nonbank-failure scenario asks who can instruct transfers, obtain records, identify legitimate customers and operate servicing when the interface disappears. A cyber outage asks whether restored data reconcile to the bank’s ledger. One business-continuity document should not treat these as interchangeable events.
Recommended drills begin with an independent copy of the ledger and a known bank balance. Reconcile total beneficial interests plus identified reconciling items to the custodial account, then demonstrate how an authorized successor could service individual owners. Do not count a successful aggregate reconciliation as proof that every customer’s allocation is correct: offsetting errors can hide underneath a balanced total.
Part 370 is a related but distinct regime
Part 370 imposes deposit-insurance determination recordkeeping obligations on covered institutions and includes alternative recordkeeping arrangements for certain accounts. The FDIC explains that some required ownership information may reside outside the bank and need to be supplied through the relevant process; §370.4 contains the recordkeeping provisions. [4][6] This framework should not be represented as a universal requirement that every bank maintain every intermediary data field in precisely the same format.
For a partnership, the practical question is whether contracts, technical access and operational rehearsals make the applicable obligations executable. Define who produces records, how quickly, under whose authority, and with what validation. Obtain access rights that survive a commercial disagreement or service-provider insolvency rather than depending entirely on cooperative personnel.
Cost, concentration and evidence
More frequent reconciliation, replicated records and tested exit arrangements add cost and can complicate data minimization. Those costs should be weighed against concentration in one recordkeeper and the consequences of unavailable funds. Moving deposits among more banks can diversify exposure but introduces allocation, disclosure and settlement complexity.
Evidence that would improve confidence includes successful customer-level reconciliations, documented ownership opinions, tested successor access and accurate bank-identity disclosures. Unexplained breaks, unavailable subledgers or a mismatch between advertised and actual bank placement would weaken it. A public insurance logo is useful identification; it is not a substitute for verifying the legal and operational chain supporting a customer’s balance.
Sources
- FDIC, deposit-broker disclosure requirements; reviewed September 27, 2026Back to text: ↑
- eCFR, 12 CFR §330.5, ownership and fiduciary records; reviewed September 27, 2026Back to text: ↑1↑2
- FDIC, Your Insured Deposits; reviewed September 27, 2026Back to text: ↑
- FDIC, Part 370 alternative recordkeeping entity processing; reviewed September 27, 2026Back to text: ↑
- eCFR, 12 CFR §330.3, deposit-insurance aggregation principles; reviewed September 27, 2026Back to text: ↑
- eCFR, 12 CFR §370.4, recordkeeping requirements; reviewed September 27, 2026Back to text: ↑