Pooled FBO bank accounts, custodial stablecoin wallets, or customer-controlled wallets: who holds the money, who reconciles it, and what fails.
A neobank holds customer funds in one of three places: a pooled for-benefit-of (FBO) bank account at a partner bank, a custodial stablecoin wallet, or a wallet the customer controls that providers only touch per transaction. Each choice sets who reconciles the money, what happens if a partner fails, and which rules apply. BlindPay runs payouts non-custodially from customer-controlled wallets.
Most neobanks end up mixing these. A dollar account app might keep a stored balance in custody and run its transfer feature as a pass-through. This guide compares the three models on nine points and shows where each one fits. For the full build path, see how to build a neobank in 2026.
This is educational content, not legal advice.
Key takeaways
Pooled bank accounts, custodial wallets, and customer-controlled wallets. The difference is who holds the money between transactions.
1. Pooled FBO bank account. The neobank, or a provider on its behalf, opens a bank account "for the benefit of" its customers. All deposits land there. The bank sees one account holder. The neobank's ledger splits the balance into thousands of user balances.
2. Custodial stablecoin wallet. User funds are converted to a stablecoin such as USDC and held in wallets where the neobank or its provider controls the keys. The ledger again tracks each user's share, sometimes with one wallet per user, sometimes pooled.
3. Customer-controlled wallet. Funds stay in a wallet the customer, or the business acting for its own account, controls. A payment provider receives only the amount the customer authorizes for one transaction, executes it, and holds nothing in between.
They trade control and simplicity against counterparty exposure. Nine points:
| Point | Pooled FBO account | Custodial wallet | Customer-controlled wallet |
|---|---|---|---|
| Who holds funds | Partner bank, titled to the neobank or provider for customers | Neobank or provider, holding keys | The customer |
| Reconciliation | Daily ledger vs bank statement, per user | Ledger vs on-chain balances, per user | Per transaction; no provider balance |
| Failed payments | Money returns to the pooled account, then the ledger | Back to the custodial wallet | Refunded to the wallet that sent it, per provider rules |
| Counterparty risk | Bank and whoever keeps the ledger | Custodian, key management, issuer | Issuer and the customer's own key security |
| Deposit insurance | Can pass through to each customer if records are clear | Does not apply to stablecoins | Does not apply to stablecoins |
| Regulatory perimeter | Money transmission, bank partner rules | Money transmission, custody and virtual asset rules | Lighter on custody; payment rules still apply |
| Time to launch | Weeks to months, needs a bank partner | Weeks, needs a custodian | Fastest for transfer features |
| Best for | Stored balances, cards, domestic transfers | Holding dollars across borders | Pass-through transfers and payouts |
| Watch outs | Ledger breaks, commingling | Key loss, depeg, custodian failure | Users must manage authorization, or you build it in |
For a deeper look at the payout side, custodial vs non-custodial off-ramps walks through what happens when a provider becomes insolvent or loses its bank.
It can pass through to each customer, but only if the records hold up. Under 12 CFR 330.7, funds owned by a principal and deposited in the name of an agent or custodian are insured "to the same extent as if deposited in the name of the principal." Under 12 CFR 330.5, the FDIC presumes funds are owned as shown on the bank's deposit account records.
In practice that means three things for a neobank:
The FDIC's fact sheet on deposit insurance and crypto companies says it plainly: insurance does not cover crypto assets and does not protect against the default, insolvency, or bankruptcy of any non-bank entity, and it lists neobanks by name. The FDIC's deposit insurance overview covers the coverage limits.
When the product stores value for a while. Custody fits if users:
All of these need someone to hold the funds and a ledger that splits them. If you go custodial with stablecoins, read the issuer's reserve reporting and the rules that apply. In the US, the GENIUS Act sets reserve and custody requirements for payment stablecoins. What the GENIUS Act means for businesses summarizes it.
When money passes through. A transfer feature where a user funds a payment and it leaves within minutes doesn't need a provider to hold anything. Keeping funds with the customer until the moment of execution means:
Non-custodial payments explained covers the mechanics. To check a provider's claim, use 8 checks to verify a provider is really non-custodial.
Illustrative example. A neobank for Brazilian freelancers paid by US clients. Volumes are invented.
| Money | Where it sits | Model |
|---|---|---|
| Client payments arriving by ACH | Each user's US virtual account, converting to USDC | Pass-through on arrival |
| Dollar savings users keep | Custodial wallet run by the neobank, one ledger entry per user | Custodial |
| Transfers home to a Brazilian bank | Pulled from the user's balance at send time, paid over Pix | Non-custodial payout leg |
| Fees the neobank earns | Neobank's own operating account | Company funds, kept apart |
The neobank holds custody only for the savings feature. Deposits and transfers pass through. On a typical day, if users receive US$400,000 and send US$300,000 home, only the US$100,000 they choose to keep adds to the custodial balance.
BlindPay is built for the pass-through part of a neobank. BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set. On Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review.
If you want custody, optional BlindPay-managed wallets (beta) are custodial when you choose that path, and production access is granted on request. US virtual accounts sit on the money-in side: each customer gets account details in their own name, and each deposit converts to USDC or USDT in the wallet you linked.
That lets you pick custody per feature instead of for the whole app. Compare other providers in the best stablecoin infrastructure for neobanks.
List every feature in your app and mark each one "stores value" or "passes through." Only the first column needs custody. Then read the funding source section of the payouts docs to see how a customer-controlled wallet and a managed wallet differ at execution.
The evidence examiners expect from automated risk monitoring: a 10-item evidence table, good vs poor practice, SAR timelines, RFIs, and a 30-day plan.
How to add a low-fee remittance feature to a US neobank: when the Remittance Transfer Rule applies, disclosures, 30-minute cancellation, and pricing.
Blockchain payments are legal for businesses in the US, EU, UK, Brazil, and Mexico, under different rules. What each country regulates, as of October 2026.