Card explaining frozen app accounts, partner banks, and sweep failures. Account freezes, partner-bank confusion, sweep failures, and inaccessible funds
Image: Fintech Notes

Rules

Part of Digital account guide: banks, nonbanks, balances, insurance, and access

Account freezes, partner-bank confusion, sweep failures, and inaccessible funds

Digital account problems guide to freezes, unclear partner banks, sweep and subledger failures, inaccessible funds, broken support handoffs, and documented fixes.

What to take away

  • An app freeze can involve identity, compliance, ledger, payment, or legal controls; ask which function is restricted.
  • A partner bank may hold pooled funds without operating the customer-facing account or knowing the app transaction ID.
  • Sweep and subledger failures can separate the displayed balance from the institution-level records.
  • Deposit insurance does not make a nonbank outage or insolvency disappear.
  • Escalation works best with a role map, balance proof, chronology, and requested action.

When a digital account fails, the user encounters one brand while the problem spans several entities. The app may control login, a processor may maintain customer balances, a bank may hold pooled money, and another vendor may send payments.

The right first question is not "Who advertises the account?" It is "Which party controls the blocked function and which record proves the balance?"

Problem 1: The account is frozen without a usable explanation

Possible restrictions

  • login blocked;
  • outbound payments blocked;
  • withdrawals paused;
  • card disabled;
  • incoming deposits accepted but unavailable;
  • only one transaction under review;
  • full account closure initiated.

Diagnose the scope

Record which actions work and which fail. Capture the notice, time, error code, affected balance, pending payments, payroll deposits, and bill deadlines. Ask support to identify the restriction type, responsible entity, required information, review state, and next update date.

Diagnose frozen account scope

  • Record which actions work and fail
  • Capture notice, time, error code
  • Note affected balance and pending payments
  • List payroll deposits and bill deadlines
  • Ask support for restriction type
  • Identify responsible entity and review state

Do not send identity documents to an address obtained from a public comment or unsolicited message. Use the verified channel in the agreement or official app.

Repair

Submit only requested documents, preserve confirmation, and ask for a receipt. If the review exceeds a promised time, escalate through the formal complaint route. Explain immediate harm such as rent, payroll, or medication without inventing urgency.

Problem 2: The app and the bank each send the user to the other

The app says, "Contact our bank partner." The bank says, "You are not our direct customer." Both responses can reflect the structure rather than bad faith.

Map the roles:

Who controls each function

Function

Login and identity
App company
Customer subledger
Program manager or processor
Pooled deposit
Partner bank
Card authorization
Issuer and processor
ACH instruction
App, processor, originating bank
Complaint
App, bank, or both

Possible controller

Login and identity
Customer subledger
Pooled deposit
Card authorization
ACH instruction
Complaint
RoleExample: Chime programAsk
AppChimeWhich restriction applies, and what lifts it?
ProcessorChime's balance systemsWhat is my ledger balance today?
Partner bankThe Bancorp Bank, Stride BankCan you find my funds by the app reference?
RailCard network, ACHWas my payment settled, returned, or pending?

Chime is not a bank.

Send each party the identifier it can use. Ask the app for a bank or rail reference. Ask the bank whether it can search the pooled account using that reference and whether the app is the recordkeeping agent.

Problem 3: The displayed balance does not match the pooled account

A nonbank can maintain user-by-user entries while the bank holds one or more omnibus accounts. Reconciliation should tie the sum of valid customer balances and in-transit items to institution-level cash.

Reconcile app balance to bank

  • Preserve every statement and transaction export
  • Ask for opening balance and all debits
  • Request closing balance and funds-in-transit treatment
  • Ask for bank placement details
  • Request any reconciliation exception affecting account
  • Do not accept screenshot as complete ledger

Differences can arise from:

Displayed balance vs pooled funds

  • duplicated or missing entries;
  • settlement timing;
  • returns not allocated to users;
  • fees recorded on only one ledger;
  • unresolved negative balances;
  • incorrect sweep files;
  • account migration;
  • processor or data-export failure.

The FDIC's proposal on third-party deposit recordkeeping was designed to address whether deposits were placed at banks, whether banks knew their actual owners, and whether banks could provide funds if a third party failed. Those questions are directly relevant to diagnosing a balance that exists in an app but cannot be tied to institution records.

Repair

Preserve every statement and transaction export. Ask for opening balance, all debits and credits, closing balance, funds-in-transit treatment, bank placement, and any reconciliation exception affecting the account. Do not accept a screenshot of the current total as a complete ledger.

Problem 4: A sweep does not complete as described

A cash-management program may move money among banks or between brokerage cash, a money market fund, and bank deposits. A failure can leave money in transit, at the prior destination, or recorded differently across systems.

Ask:

Trace a failed sweep

  1. Identify pre-sweep asset or claim
  2. Find when sweep instruction ran
  3. Confirm destination institution accepted it
  4. Check amount allocated to each destination
  5. See if source ledger reduced early
  6. Determine protection at each stage
  7. Decide display issue or asset-location issue
  1. Which program moved the cash, and when?
  2. What was the source and destination?
  3. Is it settled, pending, or failed?
  4. If it failed, where is the money?
  5. Which ledger holds it, and can you send detail by date?
  6. Who approves the correction?
  7. When will it post, and under what reference?

Problem 5: Funds are held at a bank but the nonbank controls access

Deposit placement and user access are separate. A bank can hold a pooled deposit while the nonbank controls the customer identity, instructions, and detailed balances. If the nonbank's systems fail, the bank may lack a direct process for each user.

Access funds held at bank

  • Ask bank to verify pooled account
  • Ask if bank has customer-level records
  • Ask who can authorize withdrawals
  • Request beneficial-owner ledger export
  • Get escalation contact at bank program
  • Preserve responses without assuming instant access

The Federal Reserve's review of third-party risk management notes arrangements where customers interact directly with a third party for account opening, transactions, account details, and support, and it identifies risks from misleading disclosures and failures in dispute resolution. The arrangement can therefore create a support and access dependency even where a regulated bank participates.

Repair

Ask whether the bank can verify the pooled account, whether it has customer-level records, and who is authorized to issue withdrawals. Ask the app for an export of the beneficial-owner ledger and the escalation contact at the bank program.

Problem 6: A bank partner changes midstream

Migration can change routing numbers, account identifiers, cards, sweep destinations, terms, and record custodians. Errors cluster at the boundary between old and new systems.

Before migration:

Bank partner migration checklist

  1. Before
    Download statements and balance history
  2. Before
    Record pending items
  3. Before
    Save old and new agreements
  4. Before
    Confirm effective dates
  5. Before
    Identify responsibility for old disputes
  6. Before
    Reduce avoidable in-transit funds
  7. Before
    Schedule post-migration reconciliation
  8. After
    Test small inbound and outbound transfer
  • Save the full transaction ledger and the latest statement.
  • Record the routing number, account number, and card details.
  • List every recurring deposit and debit, with amounts.
  • Confirm the migration date, the new institution, and the cutover window.
  • Ask who keeps records after migration and where disputes go.

After migration, test a small inbound and outbound transfer. Do not assume a successful login proves direct deposits and recurring debits were updated.

Problem 7: Closure removes access to records

An app may close the account and later disable login. The user then lacks statements needed for taxes, disputes, or proof of balance.

Before voluntary closure, export everything. During involuntary closure, request the complete ledger, final statement, balance-return method, tax documents, pending-transaction treatment, and retention contact in writing.

Repair

Ask for the full ledger rather than a summary. If the app refuses, send the same request to the bank program contact and file with the CFPB. Keep the closure notice and the last statement you can download.

Escalation packet

Build one PDF or folder containing:

  • One-page role map.
  • Legal agreements and named entities.
  • Opening balance and complete transaction ledger.
  • Bank or sweep placement statements available to the user.
  • Chronology of restriction, notices, and contacts.
  • Pending payroll, bills, or withdrawals affected.
  • Support case IDs and responses.
  • Exact requested action.

Where to escalate

CFPB. File at the CFPB complaint portal, consumerfinance.gov/complaint. Companies generally answer in 15 days and give a final response in 60. It can press the company for a reply. It cannot order a payment or decide contract terms.

State banking regulator. File with the state that charters the partner bank, such as the New York State Department of Financial Services, or with the state that licenses the nonbank as a money transmitter. A typical turnaround is 30 to 60 days; confirm the timeframe when you file. It can question the bank's records. It cannot rule on app fees.

FDIC. Call 877-275-3342 for an FDIC-supervised bank. It can examine deposit recordkeeping. It cannot act against the nonbank.

Sample wording

Copy this wording:

  1. "Restore access to account [identifier], or state the restriction and what lifts it."
  2. "Release any balance not tied to the review to my verified external account."
  3. "Produce the full ledger from opening to today, including funds in transit."

Timeline

Day 1. Save the full ledger and latest statement. Record the notice, time, and error code. Open one ticket and note the case ID.

Week 1. Send the written request to the app and the bank program contact. Log replies. File with the CFPB and the state regulator if nothing substantive arrives by day 7.

Month 1. If the restriction stands, ask for the bank's reconciliation exception record. Move recurring bills to another account.

Common questions

Does a freeze mean the funds are gone?

No. It means some access or transaction function is restricted. Locate the balance and restriction separately.

Can the partner bank always see my app balance?

No. It may see a pooled account while another party maintains customer-level records.

Does deposit insurance require immediate access during an app outage?

Deposit insurance addresses eligible deposits when an insured bank fails. It does not by itself operate the nonbank app or resolve every access failure.

What is the first record to export?

Export the complete transaction ledger and latest statement, then save agreements, partner disclosures, and support history.

More in Rules

Latest from Trade Desk