Every fintech app, crypto exchange, and neobank you use sits on top of one of three account structures: omnibus, segregated, or nested. The difference between them decides who legally owns your money, who sees your transactions, and what happens if the company you trust goes under. This article breaks down each structure, the regulatory and user-protection trade-offs of each, and where the industry is moving.
What is an omnibus account?
An omnibus account is a single pooled bank account held in the operator's name that aggregates funds belonging to many end users.
The bank sees one balance and one account holder, while the operator (a fintech, exchange, broker, or payment company) maintains an internal ledger that tracks how much of the pooled balance belongs to each individual user. Omnibus structures are operationally efficient — one bank relationship can support millions of users — and they are standard practice for crypto exchanges, neobanks, brokerage apps, and most payment fintechs.
The trade-off is that end users do not have a direct legal relationship with the underlying bank. Their claim on the money runs through the operator's books, which is why the quality of those books, and the operator's solvency, becomes the protection mechanism.
What is a segregated account?
A segregated account is a bank account opened in the end user's own name, where funds are legally the user's property and not the operator's.
Traditional retail bank accounts are segregated by default, held under your name, and visible to the bank as belonging to you. Regulated custodians use the same model: each client's assets are ring-fenced in dedicated accounts that cannot be commingled with the custodian's own balance sheet.
Segregation is the strongest form of user protection because it survives the operator's insolvency. If the platform collapses, the user's funds are not part of the bankruptcy estate.
What is a nested account?
A nested account is a sub-account opened by an intermediary inside another financial institution's account, where the upstream bank typically cannot see the end customer.
Nested arrangements are common in correspondent banking, where a smaller bank or payment processor accesses the global financial system through an account held at a larger bank. They are also how some fintechs historically reached card networks or SWIFT before securing direct membership themselves.
Because the upstream bank only sees its direct customer, it cannot directly perform KYC, monitor transactions, or enforce sanctions screening against the end user. This visibility gap is precisely why nested accounts have become a regulatory flashpoint.
What's the difference between omnibus, segregated, and nested accounts?
The differences come down to who holds the account, who sees the users, who carries the compliance liability, and what happens to user funds if the operator fails.
Omnibus accounts pool many users under one operator-owned account. Segregated accounts hold funds in each user's own name at a licensed institution. Nested accounts layer one operator's customers behind another institution's account, hiding the end user from the upstream bank. The table below sets the three structures side by side.
Why do most fintechs, neobanks, and crypto platforms use omnibus accounts?
Most fintechs, neobanks, and crypto platforms use omnibus accounts because omnibus accounts are dramatically cheaper to operate, faster to scale, and the only realistic option for operators without their own banking license.
Onboarding a new user into a segregated account requires opening a real bank account in that user's name. That means full KYC by the bank itself, account-opening operations, and a regulatory perimeter the operator usually does not own. For a fintech adding 100,000 users a month across multiple countries, the per-user cost and latency are prohibitive.
Omnibus structures collapse the problem into a single bank relationship. The operator handles user-level KYC and ledger tracking on its own infrastructure, and the bank only needs to know and trust the operator. The cost is concentration of risk: the user's protection rests on the operator's internal records and the operator's solvency, not on the bank.
What are the risks of omnibus and nested accounts for end users?
The core risk is that end users do not have a direct legal claim on the bank holding their funds, which makes their balances vulnerable to the operator's bookkeeping and solvency.
In an omnibus structure, if the operator's internal ledger is incomplete, inaccurate, or fraudulent, users may not be able to prove what they are owed. If the operator becomes insolvent, the pooled balance is often treated as part of the operator's estate, leaving users as unsecured creditors. The Wirecard, FTX, and Synapse collapses are all variations on this theme: customer funds were nominally held somewhere, but the ledger linking them back to individual users was either compromised or contested.
Nested arrangements compound the problem. The end user has no relationship with the upstream bank, the upstream bank has no visibility into the end user, and any failure or freeze at the intermediary cuts the user off entirely. This is why most regulators now treat nested accounts as a high-risk pattern that demands enhanced due diligence or outright restriction.
How does account structure affect AML, KYC, and compliance liability?
Account structure decides which entity carries regulatory liability for knowing the customer (KYC), monitoring transactions, and reporting suspicious activity.
In a segregated structure, the licensed bank is the regulated entity of record. It performs KYC, applies sanctions screening, monitors transactions, and files suspicious activity reports under its own license. In an omnibus structure, the bank only sees the operator, so the operator must hold a license (e-money, MSB, payment institution, or banking license) and carry the same obligations for its end users. In a nested structure, the chain becomes ambiguous — and ambiguity is what regulators have been actively eliminating.
What is a named IBAN, and how does it relate to account segregation?
A named IBAN is a unique account number issued in the end user's own name, which makes segregation visible and verifiable at the payment-rail level.
Without a named IBAN, segregation can only exist on the operator's internal ledger — a promise that funds are tracked correctly, rather than a fact that any counterparty bank can verify. With a named IBAN, the user's account exists in the payment network itself: SEPA and SWIFT route funds directly to the user, the user appears as the legal account holder, and the relationship to the operator becomes a service layer rather than a custody layer.
Named IBANs are the structural enabler that lets a platform offer segregated accounts at fintech speed. They turn segregation from an internal accounting convention into a public, network-verifiable fact.
How does UR's account layer compare to omnibus, segregated, and nested structures?
UR provides a named-IBAN, segregated account architecture delivered through an API, so partners get the user protection of segregation with the integration speed of an omnibus model. Unlike pooled omnibus accounts, where many users sit behind one shared structure, UR enables user-attribution for balances, payments and compliance checks.
UR operates under SR Saphirstein AG, a fintech company regulated under Article 1b of the Swiss Banking Act and supervised by FINMA. End users onboarded through any UR partner — a wallet, exchange or payments app — receive their own Swiss IBAN in their own name, plus access to 7 tokenized fiat currencies (EUR, USD, CHF, CNH, SGD, JPY, HKD), USDC, USDe, principal Mastercard issuance, and SEPA / SWIFT / SIC rails through the same account.
Functionally, this means UR partners do not have to choose between omnibus speed and segregated safety. Each user has a named, legally segregated account, KYC and AML are carried by UR as the licensed operator of record, and balances are protected at the protocol level rather than depending on an operator's internal ledger. There is no nesting — every account is visible to the regulator, the bank, and the user as belonging to that user.
Omnibus accounts solved a real problem: how to onboard millions of users without forcing each of them through a traditional bank-account-opening process. Nested accounts solved a different problem: how to reach payment networks without direct membership. Both were pragmatic responses to infrastructure that did not exist yet.
That infrastructure now exists. Named-IBAN account layers like UR let platforms keep the speed and unit economics of an omnibus model while giving each user the legal protection of a segregated account, under a single regulated perimeter. As regulators push for more visibility and as users push for stronger protection, the structures that were tolerated for a decade are quietly being replaced by structures that no longer require the trade-off.
FAQ
Is an omnibus account the same as a pooled account?
Yes. “Omnibus” and “pooled” are used interchangeably to describe a single account that aggregates funds belonging to many users under one operator-owned account holder of record.
What does “segregated” actually mean in banking?
Segregated means the funds are legally and operationally separated from the operator's own assets and from other users' funds, usually by being held in an account opened in the individual user's name at a licensed institution.
Can a customer have a named IBAN without opening a bank account themselves?
Yes. A licensed account-layer provider can issue a named IBAN to an end user through a partner platform, which is how UR delivers Swiss IBANs to users of wallets, exchanges, and apps without those users going through a manual bank-account-opening process.
Are stablecoin balances at fintechs and exchanges held in omnibus accounts?
Almost always, yes. Most exchanges and crypto fintechs hold stablecoins in pooled custodial wallets and reconcile user balances on internal ledgers, which is the crypto-native equivalent of an omnibus bank account.
Why did regulators take action on nested accounts?
Because nested arrangements break the line of sight between the regulated bank and the end customer, which makes KYC, sanctions screening, and AML monitoring unreliable. Several high-profile fintech and crypto failures involved nested structures used to bypass direct supervision.
Is segregated always better than omnibus?
Segregated is stronger for user protection, but historically it was operationally heavier and slower to scale. The reason segregated accounts have not been the default in fintech is cost and speed, not regulatory preference. Named-IBAN account layers close that gap.
