At a glance
FBO accounts (For Benefit Of) are single bank accounts held by fintech platforms on behalf of many end users. The platform is the legal account holder. The end users own the funds. The bank sees one pooled balance. The platform maintains an internal ledger tracking individual ownership. Most US fintech custody architecture is built on this structure.
Key distinction: When a platform's ledger and the bank's balance diverge, as happened with Synapse in 2024, end users lose access to their funds and FDIC pass-through insurance does not apply. Named account custody removes this structural risk by design.
An FBO account, short for "For Benefit Of", is a single bank account held by a fintech platform on behalf of many end users. The platform is the legal account holder. The end users own the funds. Most platforms running custodial wallets, payroll, marketplace payouts, or stored value sit on FBO structures today. When Synapse collapsed in 2024, the structure left more than 100,000 end users locked out of their funds. The architecture was working as designed.
How an FBO account works in practice
The platform opens an account at a bank in its own name, labelled "Platform Inc FBO Its Customers". Customer funds flow into this single account. The platform maintains an internal ledger that tracks how much of the pooled balance belongs to each user. The bank does not see the end users. It sees one account with one balance.
This structure exists because most fintech platforms are not banks and cannot hold customer funds directly. The bank holds the legal account. The platform holds the operational relationship with the user. The ledger sits with the platform. When a user logs in and sees a balance, that balance is a representation of their share of the FBO pool, not a direct account at the bank.
Reconciliation runs daily. The platform compares its internal ledger against the bank's view of the FBO account. If the totals match, the platform has correctly attributed funds. If they do not, somewhere in the system, a user's balance does not reflect what the bank actually holds.
Why platforms use FBO accounts
The model is operationally efficient:
- Account consolidation. One bank account replaces thousands of individual accounts.
- Lower regulatory burden. The platform avoids the regulatory and compliance burden of being a bank.
- Fast onboarding. Onboarding a new customer takes minutes because the bank is not involved in the relationship.
- Low cost. The platform pays for one account, not many.
It also fits the way fintech platforms scale. A marketplace can launch in a new currency corridor by opening a single FBO account. A neobank can onboard millions of users without each requiring a direct bank relationship. Stored value businesses, BaaS providers, payroll platforms, and digital wallets are almost all built on FBO architecture for these reasons.
Insurance for FBO funds depends on the structure. In the US, FDIC pass-through insurance can apply if records are kept correctly, which is why the FDIC finalised stricter recordkeeping rules for custodial deposit accounts in late 2024. In the UK, safeguarding rules require funds to be segregated. In both cases, the protection is contingent on the platform demonstrating, in real time, which funds belong to which user.
Where the FBO structure breaks
The failure mode is well-documented. When a platform's ledger and the bank's balance diverge, the structure collapses. The bank cannot determine who owns what. The customer cannot demonstrate ownership. Pass-through insurance fails because the records that establish each user's share are unreliable.
Synapse is the canonical example. When the company filed for bankruptcy in April 2024, the trustee found that internal ledgers and bank balances disagreed by tens of millions of dollars. Over 100,000 end users were locked out of accounts. Pass-through insurance did not apply because the records of beneficial ownership were not reliable.
Synapse was not an outlier. The FCA's review of failed UK e-money and payments firms found an average safeguarding shortfall of 65% of customer funds across the population studied. That data, which informed PS25/12, came from firms running pooled structures comparable to FBO accounts.
The named account alternative
A named account flips the structure. Instead of one FBO account holding many users' funds, each end user has an individual account at the institution. The account is held in the user's name. The institution sees the user directly. Reconciliation is replaced by balance verification: the sum of all named accounts at any moment equals the total funds under custody, by construction.
Lorum's Named Account Custody model is built on this architecture. Each account holder has a legal and operational relationship to the custody framework. There is no platform-maintained ledger sitting between the bank and the user. The structural risk of divergence between ledger and balance is removed because there is no separate ledger to diverge.
For platforms, the operational implication is significant. Daily reconciliation under the FCA's supplementary safeguarding regime becomes trivial when each user has a named account. Pass-through insurance issues disappear because each account is individually held. Audit trails are clean because the institution itself is the system of record.
What changes ahead of PS25/12 and PSD3
The regulatory direction is converging on segregation. The FCA's supplementary safeguarding regime, which takes effect on 7 May 2026, requires daily reconciliation, resolution packs, and senior manager accountability for safeguarded funds. The European Commission's PSD3 and PSR proposals narrow the commercial agent exemption and require funds to enter a safeguarding account immediately on receipt.
For platforms running FBO architecture, this means the cost of maintaining accurate ledgers is increasing. Daily reconciliation requires daily attention. Senior managers carry personal liability for getting it wrong. Audit submissions become continuous rather than periodic. The compliance overhead of pooled structures grows even as the structural risk remains.
Platforms reviewing their custody architecture ahead of 2026 have a choice. Maintain an FBO model and absorb the rising operational cost of meeting the new requirements. Or move to a named account structure where the compliance burden is reduced by design. The decision shapes everything that follows: reconciliation, audit, insurance, and what happens to customer funds if the platform fails.
FBO accounts vs named account custody
The structural differences between the two architectures determine reconciliation complexity, regulatory exposure, and what happens to customer funds if the platform fails.
| Dimension | FBO account | Named account custody |
|---|---|---|
| Account holder | Platform (legal), users (beneficial) | End user (legal) |
| Reconciliation | Daily ledger-to-bank reconciliation | Balance verification by construction |
| Bank's view of end user | None (sees only the platform) | Direct relationship |
| Pass-through insurance | Conditional on accurate records | Each account individually held |
| Failure mode | Ledger and balance divergence (Synapse) | Structurally eliminated |
| Audit complexity | High (continuous reconciliation) | Low (institution is system of record) |
Frequently asked questions
What does FBO stand for in banking?
FBO stands for 'For Benefit Of'. An FBO account is a single bank account held by one entity (typically a fintech platform) on behalf of multiple end users. The account is titled in a format like 'Platform Inc FBO Its Customers', with the platform as the legal account holder and end users as the beneficial owners.
Are FBO accounts insured by the FDIC?
FBO accounts can qualify for FDIC pass-through insurance if records of beneficial ownership are accurate and complete at the time of bank failure. The Synapse collapse in 2024 demonstrated that when those records are unreliable, pass-through insurance does not apply. The FDIC finalised stricter recordkeeping rules for custodial deposit accounts in late 2024 in response.
What is the difference between an FBO account and a named account?
An FBO account holds funds for many users in a single pooled balance, with ownership tracked by the platform's internal ledger. A named account is opened in each end user's name at the institution level, with the bank seeing each user directly. Named accounts eliminate the reconciliation risk inherent in FBO structures.
Why did Synapse's FBO accounts fail?
Synapse's internal ledger and the underlying bank balances diverged by tens of millions of dollars. When Synapse filed for bankruptcy in April 2024, the bankruptcy trustee could not reconcile the records to determine which funds belonged to which end user, freezing access for over 100,000 customers.
Will PS25/12 affect FBO accounts in the UK?
Yes. The FCA's supplementary safeguarding regime, effective 7 May 2026, requires daily reconciliation, resolution packs, and senior manager accountability for safeguarded funds. Firms running pooled structures comparable to FBO accounts must demonstrate accurate beneficial ownership records continuously.
