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

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.

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 bank send the user to each 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:

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

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 pooled funds

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.

Differences can arise from:

• 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:

1. What was the pre-sweep asset or claim?
2. When did the sweep instruction run?
3. Which destination institution accepted it?
4. What amount was allocated to each destination?
5. Did the source ledger reduce before destination confirmation?
6. What protection applied at each stage?
7. Is the error a display issue or an asset-location issue?

Do not rely on a blended "cash" number. Obtain the position or deposit detail by date.

Problem 5: Funds are at a bank but inaccessible through the nonbank

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.

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. Preserve each response without asserting that deposit insurance requires instant app access.

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:

• download statements and balance history;
• record pending items;
• save old and new agreements;
• confirm effective dates;
• identify responsibility for old disputes;
• reduce avoidable in-transit funds;
• schedule a post-migration reconciliation.

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.

Do not treat a mailed residual-balance check as proof that every transaction reconciled. Compare it with the final statement.

Escalation packet

Build one PDF or folder containing:

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

Possible requests include restoring access, releasing an unaffected balance, correcting the ledger, identifying the holding institution, completing a payment trace, returning funds, or issuing a final statement.

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.