A neobank that is not itself a chartered bank cannot hold deposits directly, so it usually keeps customer cash in a for-benefit-of (FBO) account at a partner bank. Stablecoin balances sit in a wallet the neobank or its provider controls, or in one the customer controls. Each place decides who keeps the records and which protections apply.
A founder who thinks the money is "at the bank" may promise protection that exists for only one of the three places. This post covers the US structure and leans on primary sources: the models, the FDIC rules and fact sheet, the GENIUS Act text and OCC Bulletin 2026-50, each with the date its status was checked. It also says when holding funds is the wrong move, and what Lumx does at each point. Other countries have their own safeguarding rules, not covered here. The custodial wallet explainer defines custody and the custodial vs non-custodial comparison ranks wallet options; neither is repeated here.
What are the three places a neobank can hold customer funds?
An FBO account at a partner bank, a wallet the neobank controls, and a wallet the customer controls. What separates them is who holds the money, or the keys to it, between two transactions.
The first is where most US dollar apps start: a bank account titled for the benefit of the neobank's customers. The bank sees one account holder, and the neobank's ledger divides the balance.
The second is a stablecoin balance in a wallet whose private keys sit with the neobank or its provider, with the ledger recording each customer's share.
The third is a wallet the customer controls. A provider touches it only to execute an amount the customer authorized for one transaction, and holds nothing in between. Most neobanks mix them: a stored balance in the first or second, a transfer feature on the third.
On Lumx, the cash side is an account issued by a banking partner in the customer's name, and the stablecoin side is a custodial wallet per customer, so Lumx does not use the third model (accounts and wallets in the docs). A neobank can open that account in its own end user's name, and the neobank itself needs no Central Bank of Brazil authorization.
How do the three holding models compare?
They trade simplicity and control against counterparty exposure and record-keeping work. The table compares the three on the points a risk review asks about.
Three models for holding customer funds, compared on who holds the money and what fails.
Point | FBO account at a partner bank | Wallet the neobank controls | Wallet the customer controls |
Who holds the funds | Partner bank, in an account titled for customers | Neobank or its provider, which holds the keys | The customer |
Who keeps the record of ownership | The neobank's ledger, and sometimes the bank | The neobank's ledger against blockchain balances | The blockchain, per customer wallet |
Who reconciles, and how often | The neobank, against bank statements; the FDIC's 2024 proposal would require daily | The neobank, against blockchain balances | Nobody at the neobank |
US deposit insurance | Can pass through to each customer if the records are clear | None for stablecoins (GENIUS Act, Section 4(e)) | None for stablecoins |
Who can move the money | The neobank, through the partner bank's rails | The neobank or its provider, which holds the keys | The customer, by signing each transaction |
What the customer sees in the app | A balance from the neobank's ledger | A balance from the neobank's ledger | The wallet's own balance, read from the blockchain |
US regulatory perimeter | Bank supervisors oversee the partner bank | GENIUS Act rules apply to the issuer; the neobank's own status is a question for counsel | GENIUS Act rules apply to the issuer |
What you need before launch | A bank agreement, a ledger, a reconciliation routine | A custody agreement, a key policy, a ledger | A wallet connection and an authorization flow |
Each model moves a different risk. The first puts it on the bank and the neobank's ledger, the second on the custodian and the issuer, the third on the customer's own key security. Picking the second to avoid a bank agreement trades a paperwork problem for a key-management one.
The neobank's ledger is the record that matters in an FBO account
An FBO account works only as well as the ledger behind it, because the bank sees one account holder and the ledger is the only record of who owns each dollar.
The FDIC's rules recognize the arrangement. Under 12 CFR 330.7(a), funds owned by a principal and deposited in the name of an agent, custodian or nominee are insured "to the same extent as if deposited in the name of the principal(s)." The catch is that the records have to show who the principals are. The rule was read in the eCFR on November 1, 2026.
The public record shows what a ledger gap costs. The FDIC tied its September 17, 2024 recordkeeping proposal to the failure of a nonbank middleware provider that kept records for banks. The CFPB director said the firm "appears to have failed to properly track customer account balances" and that "tens of thousands of customers have had their funds frozen for months" because the banks "have been unable to reconcile all the records."
The FDIC proposal, published October 2, 2024 (89 Fed. Reg. 80135, RIN 3064-AG07), would make banks holding custodial accounts with transactional features identify each beneficial owner and reconcile the account for each owner daily. Its final-rule status was not confirmed as of November 1, 2026; check the FDIC rulemaking page before planning around it.
On Lumx, each end user is its own customer with a wallet and, where needed, an account, so records are kept per customer under the neobank's own ledger (customers in the docs). The KYC (know your customer) check can be reused through Sumsub token sharing.
Deposit insurance does not cover the neobank itself
A customer who sees "FDIC" on a neobank's website may assume the neobank is insured. It is not. The FDIC insures deposits held at insured banks, and only when an insured bank fails. In its July 28, 2022 fact sheet on crypto companies, the FDIC says that insurance "does not protect against the default, insolvency, or bankruptcy of any non-bank entity, including crypto custodians, exchanges, brokers, wallet providers, and neobanks."
So the partner bank's charter protects nothing the neobank holds itself. The ledger is what links a customer to an insured deposit, which is why it comes first in the section above.
Lumx accounts are issued by a banking partner that holds the funds and executes the rails; each customer's wallet balances come back from Read a customer.
What the GENIUS Act says about stablecoin balances
A customer who holds stablecoin through a neobank does not get a smaller version of deposit insurance. The law says there is none. The GENIUS Act (Public Law 119-27, signed July 18, 2025) separates the stablecoin from the deposit. Section 4(e) says payment stablecoins are not subject to FDIC deposit insurance and makes it unlawful to represent that they are. Section 4(a)(1)(A) requires issuers to hold identifiable reserves of at least 1 to 1, and Section 11 gives holders priority over those reserves in an issuer insolvency.
Three limits matter for a neobank. First, those protections run against the issuer and its reserves, not the neobank that holds the wallet. Second, Section 10(c) gives customers priority in a custodian's insolvency, but Section 10 covers custody of the reserve, collateral and issuer private keys, not a neobank's customer wallets. Third, the Act takes effect on the earlier of January 18, 2027 or 120 days after the primary regulators issue final regulations (Section 20). The OCC issued its final rule (OCC Bulletin 2026-50, October 21, 2026, effective January 18, 2027); other regulators' final rules were not confirmed as of November 1, 2026, so the date can only move earlier. The GENIUS Act explainer has the full reading.
On Lumx, stablecoin sits in a custodial wallet per customer that holds USDC or USDT between on-ramps and off-ramps (wallets). BitGo is the custodian and carries insurance of its own, which is not deposit insurance: the balance is stablecoin, not a deposit, because Lumx is not a bank.
A neobank needs to hold funds only when the product stores value
A neobank needs to hold funds only when its product stores value for a while. If customers keep a balance for weeks, spend from it with a card, or expect to log in and see money waiting, someone has to hold the funds and keep a ledger. Paying a party Lumx has not onboarded needs written approval from compliance (nested payments), so a neobank needs an approved structure before it holds anyone's money. Holding customer stablecoins may also make a neobank a VASP (virtual asset service provider) under local rules; the VASP explainer covers it.
When is holding customer funds the wrong move for a neobank?
Holding funds is wrong when the product does not store value, or when the neobank cannot yet carry a balance's duties. Three cases:
A pure transfer product. If every payment leaves within minutes, a stored balance only adds a reconciliation job and an implied safety claim.
No agreement with a bank. An FBO account needs a partner bank that accepts the neobank as an account holder. A neobank without one that stores dollars anyway is pooling money it has no structure for.
A product that needs a US chartered-bank structure. A neobank that must itself take insured deposits, or pay interest on them, needs a charter or a bank partner that runs those accounts. A wallet does not substitute for either.
I recommend listing every feature of the app and marking each as "stores value" or "passes through" before choosing a model, because only the first group needs a holder. I would keep an internal ledger even when a partner also keeps one, since the day the two disagree is the day the neobank needs its own record to say who owns what. And I would never let a stablecoin balance carry language that sounds like deposit insurance, however good the reserve story or the custodian's own cover, because the customer who reads "protected" hears "insured".
How to check where a neobank holds funds
Three checks, in order of cost. Read the terms of service or deposit agreement for the partner bank's name and the words "for the benefit of". Look the bank up in the FDIC's BankFind tool, which the FDIC fact sheet names as the way to confirm an insured bank. Then ask the neobank in writing who keeps the ledger, how often it is compared to the bank statement, and where stablecoin balances sit.
A neobank built on Lumx can answer part of this from its own systems: Read a customer returns each customer's wallet balances.
What Lumx does at each of these points
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
On the cash side, a named virtual account is a fiat account issued by a Lumx banking partner in the customer's name. Each account is tied to one currency, and the banking partners hold the funds. BRL, MXN, USD, EUR and GBP accounts are issued in the customer's name; the COP account runs under a banking partner's sponsored program, so for a customer who is not Colombian the account holder shown is the partner. Lumx is not a bank, and the structure behind each account is the partner's.
On the stablecoin side, the wallet is custodial, held by BitGo with insurance and fully segregated per customer, with no omnibus account. Creating a customer provisions a wallet on each supported blockchain, enabled once the customer reaches APPROVED. It holds USDC or USDT between on-ramps and off-ramps, so a platform can fund a customer once and pay out from the same balance many times. See the custodial wallet product page.
The piece that makes the neobank case work is one Lumx customer per end user: each is onboarded with its own KYC check, wallet and, where needed, account, instead of holding all balances in one pot. The neobank keeps its own ledger for what it promises users, with Lumx records under it per customer. Outside the US, a neobank that runs through a licensed partner can be a Lumx customer without its own Brazilian central bank authorization. The named virtual account explainer defines the object; named virtual accounts vs pooled accounts covers the one-pot model.
No stablecoin balance in a Lumx wallet carries deposit insurance. Lumx US OP LLC, in Wyoming, is a FinCEN-registered MSB (FinCEN MSB explainer); the supported countries page lists where the regimes apply.
Methodology and sources
Checked on November 1, 2026 against primary text.
12 CFR 330.5 and 330.7 in the eCFR; FDIC fact sheet of July 28, 2022, and FDIC press release of September 17, 2024, on fdic.gov; GENIUS Act, Public Law 119-27, in the govinfo.gov text; OCC Bulletin 2026-50.
The Federal Register (89 Fed. Reg. 80135) and the CFPB director's statement block automated access, so they are cited without a link. Lumx behavior was read from docs.lumx.io on November 1, 2026.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Mikheil Kuzmidi on Unsplash.
Where does a neobank hold customer funds?
Usually in a for-benefit-of account at a partner bank, with the neobank's ledger dividing the balance by customer. Stablecoin balances sit in a wallet the neobank or its provider controls, or in one the customer controls. On Lumx, accounts are issued by a banking partner in the customer's name, except COP, where the holder shown can be the partner, and stablecoin sits in the customer's custodial wallet.
Are neobank customer funds FDIC insured?
Cash in a properly titled FBO account at an insured bank can be insured to each customer, up to the limits, if the records show who owns what. The FDIC says insurance does not cover a non-bank failure, neobanks included, and the GENIUS Act says payment stablecoins are not deposit insured. Lumx does not describe a stablecoin balance as deposit insured; the custodian's own insurance is a different thing.
What is an FBO account?
An FBO account is a bank account opened in the name of a company, for the benefit of the customers whose money it holds. The bank sees one account, and the company's ledger records who owns what. It is a US structure.
Does a neobank need to hold stablecoins in custody?
Only if the product stores value, such as a balance customers keep or a card. A pure transfer feature can run on an amount the customer authorizes for one transaction. On Lumx, the custodial wallet holds stablecoin between operations.
Who keeps the record of who owns what?
In an FBO account, the neobank's ledger, because the bank sees one account holder. For a wallet the neobank controls, the neobank's ledger against blockchain balances. For a wallet the customer controls, the blockchain. On Lumx, the neobank keeps its own ledger for what it promises users.
