Compliance & Structure
FBO Account Structure: How Embedded Finance Programs Hold Customer Funds
FBO (For Benefit Of) accounts are the mechanism that allows non-bank platforms to hold customer funds with FDIC insurance. Here is how they work, what they require, and where programs go wrong.
FBO Structure Explained
The FBO account sits at the intersection of banking law, FDIC insurance, and embedded finance operations.
A For Benefit Of (FBO) account is a bank account held by a non-bank entity (the platform) at a sponsor bank, with customer funds pooled in that account and tracked at the individual customer level in the platform's sub-ledger. The structure enables FDIC pass-through insurance coverage for each customer without requiring each customer to have a direct bank account.
What it enables
Non-bank platforms can hold customer funds in a regulated bank account with FDIC pass-through coverage up to $250K per beneficial owner without each customer needing a direct bank relationship.
What it requires
Precise sub-ledger records mapping every dollar in the pool account to individual customer balances, reconcilable on demand. The sponsor bank requires daily reconciliation and audit access.
Where it fails
Sub-ledger synchronization failures — when the platform's internal records diverge from the bank account balance. This is a compliance violation and one of the most common BaaS program failures at scale.
Questions about your program architecture? We diagnose the specific decisions that apply to your program in 30 minutes.
Talk with us →