Where does a neobank hold customer funds? FBO accounts, custodial wallets, and non-custodial flows

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

  • FBO accounts hold cash for many customers under one bank account. Your ledger is the only record of who owns what, so it has to be right every day.
  • Custodial stablecoin wallets add issuer and key risk and carry no deposit insurance.
  • Non-custodial flows keep funds with the customer and move only the authorized amount, which shrinks the balance a provider holds.
  • Custody is a product decision. Stored balances, cards, and interest need it. Pure transfers mostly don't.

What are the three places customer funds can sit?

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.

How do the three models compare?

They trade control and simplicity against counterparty exposure. Nine points:

PointPooled FBO accountCustodial walletCustomer-controlled wallet
Who holds fundsPartner bank, titled to the neobank or provider for customersNeobank or provider, holding keysThe customer
ReconciliationDaily ledger vs bank statement, per userLedger vs on-chain balances, per userPer transaction; no provider balance
Failed paymentsMoney returns to the pooled account, then the ledgerBack to the custodial walletRefunded to the wallet that sent it, per provider rules
Counterparty riskBank and whoever keeps the ledgerCustodian, key management, issuerIssuer and the customer's own key security
Deposit insuranceCan pass through to each customer if records are clearDoes not apply to stablecoinsDoes not apply to stablecoins
Regulatory perimeterMoney transmission, bank partner rulesMoney transmission, custody and virtual asset rulesLighter on custody; payment rules still apply
Time to launchWeeks to months, needs a bank partnerWeeks, needs a custodianFastest for transfer features
Best forStored balances, cards, domestic transfersHolding dollars across bordersPass-through transfers and payouts
Watch outsLedger breaks, comminglingKey loss, depeg, custodian failureUsers 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.

How does deposit insurance work on an FBO account?

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:

  1. The account title has to show that it is held for customers, not for the neobank.
  2. Someone has to be able to show which customer owns which dollar on any given day.
  3. Insurance only pays when an insured bank fails. It does nothing if the neobank or a middleware provider fails and its ledger is wrong.

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 is custody the right choice?

When the product stores value for a while. Custody fits if users:

  • Keep a dollar balance for weeks or months.
  • Spend from that balance with a debit card.
  • Earn interest or rewards on it.
  • Expect to log in and see money waiting, not just a transfer history.

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 is a non-custodial flow the right choice?

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:

  • No provider balance to reconcile.
  • Less money exposed if a provider has an outage or worse.
  • A smaller regulatory surface for the custody piece.

Non-custodial payments explained covers the mechanics. To check a provider's claim, use 8 checks to verify a provider is really non-custodial.

What does a mixed setup look like?

Illustrative example. A neobank for Brazilian freelancers paid by US clients. Volumes are invented.

MoneyWhere it sitsModel
Client payments arriving by ACHEach user's US virtual account, converting to USDCPass-through on arrival
Dollar savings users keepCustodial wallet run by the neobank, one ledger entry per userCustodial
Transfers home to a Brazilian bankPulled from the user's balance at send time, paid over PixNon-custodial payout leg
Fees the neobank earnsNeobank's own operating accountCompany 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.

What are the common mistakes?

  • Commingling. Company money and customer money in the same account or wallet. Keep them apart from day one.
  • Trusting one ledger. If a middleware provider keeps the only ledger and fails, nobody can prove who owns what. Keep your own and reconcile it daily.
  • Promising insurance you can't deliver. Never imply FDIC coverage on a stablecoin balance.
  • Choosing custody by default. Holding funds you don't need to hold adds risk, rules, and reconciliation work.
  • No failure plan. Write down what happens to user funds if your bank, custodian, or payout provider goes offline. What happens if a stablecoin payment provider fails is a starting checklist.

How BlindPay fits

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.

What to do next

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.

FAQ