
Guides
Digital account guide: banks, nonbanks, balances, insurance, and access
Digital account guide to identifying banks and nonbanks, tracing customer balances, evaluating deposit insurance, understanding app access, and preserving records.
What to take away
- A finance app's brand may differ from the bank, broker, custodian, or program manager behind a feature.
- The customer-facing balance may be maintained outside the bank's own customer ledger.
- Deposit insurance covers eligible deposits when an insured bank fails, not every app failure, freeze, fraud loss, or record mismatch.
- Access depends on technology, identity controls, contracts, and records even when the underlying funds are at a bank.
- Map each feature separately and keep evidence outside the app.
An app can look and behave like a bank without being a chartered bank. It may offer access to a deposit account at a partner bank, a prepaid account, a nonbank stored balance, a brokerage sweep, a card, a loan, or several of these under one login.
The safest way to understand it is to replace the brand story with a relationship map. Identify the legal entity, account, ledger, custodian, payment rail, and protection attached to each feature.
This guide provides general U.S. educational information. Coverage and rights depend on the arrangement, records, product, and facts.
Start with the legal entities
Capture the names in the account agreement, privacy notice, cardholder agreement, and deposit disclosure. Do not assume the company named in the app store listing performs every role.
| Role | Question |
|---|---|
| App brand | Who markets the service and controls the interface? |
| Contracting entity | Which company signs the user agreement? |
| Bank | Which insured institution receives or holds deposits? |
| Program manager | Who administers the customer program? |
| Middleware or processor | Who maintains records or sends payment instructions? |
| Card issuer | Which entity issues the debit or prepaid card? |
| Broker | Is any cash or asset held in a brokerage account? |
| Support operator | Who receives error notices and complaints? |
One entity can hold multiple roles. Several entities can also sit between the customer and the bank.
Distinguish direct and intermediated accounts
Direct bank account
The customer opens an account with the bank, appears in the bank's customer records, receives the bank's agreement, and uses the bank's site or app. A vendor may provide software without becoming the account provider.
Bank account delivered through a nonbank
The customer interacts with a fintech or other third party that markets and services a deposit product at a bank. The bank may rely on outside parties for the system of record, transaction processing, compliance, support, or disputes.
Custodial or pooled arrangement
A third party may place funds from many users into one bank account and maintain the detailed user ledger. Eligibility for pass-through insurance can depend on ownership, disclosure, and recordkeeping requirements.
Nonbank stored balance
The provider may owe the user a contractual balance without establishing a deposit in the user's name. Funding, safeguarding, withdrawal, and insolvency treatment come from the applicable structure and terms.
Brokerage or sweep arrangement
Cash can remain at a broker, move into a money market mutual fund, or be swept to one or more banks. The location can change the relevant failure protection.
Understand who keeps the ledger
A customer may see an app balance while the bank sees one pooled account. The detailed records that connect each user's claim to the pooled money may reside with a program manager, processor, or middleware provider.
The Federal Reserve, FDIC, and OCC describe bank-third-party arrangements in which outside firms may maintain the deposit and transaction system of record, process payments, provide the app, service accounts, and handle complaints. Their joint statement on third-party deposit products also says a bank's use of third parties does not diminish the bank's responsibility to comply with applicable law.
For the customer, that structure creates practical questions:
- Can the bank identify the user and balance directly?
- Which record controls when app and bank totals differ?
- Does the bank have timely access to the detailed ledger?
- Who reconciles the pooled account to customer balances?
- Who can release funds if the nonbank stops operating?
Do not assume a named bank can search the app's private transaction ID.
Read the balance label
Common labels include cash balance, spending balance, available funds, savings, wallet, reserve, brokerage cash, and card balance. The label may describe a function without identifying the legal form.
For each balance, record:
- Legal owner or claimant.
- Entity owing the balance.
- Account title at any bank or broker.
- Whether funds are pooled.
- Institution maintaining the customer-level ledger.
- Withdrawal right and timing.
- Protection claim and covered failure.
A promise that funds are "held with partner banks" is incomplete without the partner names, timing of placement, ownership records, and conditions.
Evaluate deposit insurance correctly
FDIC insurance protects eligible deposits at an insured bank if that bank fails, subject to limits, ownership categories, and record requirements. NCUA share insurance provides a separate framework for federally insured credit unions.
Deposit insurance does not automatically cover:
- insolvency of a nonbank app operator;
- fraud or theft from an account;
- loss of access during an outage;
- securities or cryptoasset price losses;
- a balance not placed as an eligible deposit;
- amounts above applicable limits;
- missing or inaccurate beneficial-owner records.
Ask which institution would have to fail for the stated protection to apply. That question exposes many vague claims.
Treat access as a separate risk
Money can be safely held at an institution and still be inaccessible to the user because of:
- app or API outage;
- broken identity verification;
- frozen profile;
- lost phone or recovery channel;
- processor failure;
- bank-partner termination;
- ledger reconciliation dispute;
- withdrawal limit;
- legal or compliance hold.
Maintain an alternate route for essential bills. If the product is used for business receipts or payroll, export records and sweep funds according to a documented liquidity policy.
Examine movement between balances
An app may offer instant internal transfers while external withdrawals use ACH or another bank rail. Build a flow:
Funding account -> app or program ledger -> recipient app balance -> withdrawal instruction -> recipient bank
At every arrow, record:
- initiating party;
- payment rail;
- fee;
- stated timing;
- hold or review right;
- reversal or return process;
- transaction reference.
An internal credit may be immediately spendable inside the app yet not withdrawable. A bank debit may post before the app balance is available.
Read rights by transaction type
Do not assume every feature shares one error process. Card purchase disputes, consumer electronic-fund-transfer errors, remittances, brokerage claims, loan servicing disputes, and crypto transfers can have different rules.
Save:
- account and card agreements;
- fee schedule;
- privacy notice;
- deposit-insurance disclosure;
- bank and broker names;
- error-notice addresses;
- support records;
- monthly statements and tax records.
The agreement in effect on the transaction date may matter more than the current help page.
Plan for partner changes and closure
Finance apps change banks, processors, and program structures. A notice may require consent, new routing details, a card replacement, or an account migration.
Before accepting a change:
- identify the new legal entities;
- compare account ownership and insurance language;
- record when old and new terms apply;
- update direct deposits and automatic payments only through verified channels;
- download the closing statement from the old program;
- reconcile balances before and after migration;
- retain both sets of terms.
When closing, move funds first where practical, cancel recurring payments, download records, revoke linked access, and obtain written confirmation.
A one-page account map
| Field | Verified answer |
|---|---|
| App legal entity | |
| Account provider | |
| Bank or credit union | |
| Account title | |
| Customer-level ledger keeper | |
| Balance form | |
| Deposit placement timing | |
| Insurance claim | |
| Covered failure | |
| Withdrawal rail | |
| Formal error contact | |
| Alternate access route |
Unknown fields are a result, not an invitation to guess.
Common questions
Is a neobank a bank?
The marketing category does not answer the legal question. Some brands are chartered banks; others provide access to bank products through partner arrangements.
Does naming an FDIC-insured partner mean my app balance is insured?
No automatic conclusion follows. Verify deposit placement, ownership, recordkeeping, limits, and the event covered.
Can the partner bank unlock my app account?
Not necessarily. The nonbank may control the interface and identity system. Ask who controls access and who maintains the ledger.
What record matters most?
No single record answers every issue. Preserve the agreement, bank identity, statements, transaction references, and customer-level balance history together.
In this guide
- How to verify who holds and protects money in a finance appFinance app verification method for finding legal entities, confirming partner banks, tracing fund placement, testing insurance claims, and saving evidence.
- Bank account, prepaid account, brokerage cash, and app balance comparedBank accounts, prepaid accounts, brokerage cash, and app balances compared by provider, ownership, ledger, insurance, fees, access, transfers, and failure risk.
- Digital bank and finance app due-diligence checklistDigital bank and finance app checklist covering legal identity, charter, partners, custody, records, insurance, fees, data, security, support, and exit risk.
- Account freezes, partner-bank confusion, sweep failures, and inaccessible fundsDigital account problems guide to freezes, unclear partner banks, sweep and subledger failures, inaccessible funds, broken support handoffs, and documented fixes.
- Mapping a fintech app's bank, ledger, and insurance disclosures caseFintech account mapping case showing how to identify a nonbank, partner bank, pooled ledger, deposit placement, insurance conditions, support roles, and gaps.







