Demystifying fintech account structures: Demand deposit accounts (DDAs) vs. for-benefit-of (FBO) accounts

It’s rare that you’ll want to know the innermost workings of your bank or banking provider. In most cases, the main things you’ll care about are that your money is safe, and that you’re able to move or access it reliably. But in some moments — and particularly in moments of uncertainty — there’s peace of mind in knowing how things work; in having all the facts so that you can make informed decisions about how and where you store your money.

Understanding the distinctions between demand deposit accounts (DDAs) and for benefit of (FBO) accounts is one way to achieve this peace of mind. Each type of account has specific implications about the type of relationship an end-user has with their bank, the level of ownership they have over their account, and their insurance eligibility. Knowing these core differences can help you navigate your own banking relationship with more confidence.

Key takeaways

• DDAs give end-users a direct relationship with the bank, whereas FBOs involve a third-party intermediary, like a fintech.
• DDAs have direct FDIC insurance up to $250,000 per depositor (subject to aggregation rules), while FBOs may have "pass-through" insurance if properly structured. There are also special cases with types of custodian accounts, such as sweep network structures, where funds are only eligible for pass-through insurance.
• Neither DDAs or FBOs are inherently safer — both are subject to traditional regulatory compliance, and potential layers of fintech-specific compliance, depending on the setup.

A demand deposit account (DDA) is a type of bank account where the end-user has direct ownership over the account — in other words, what you’d commonly think of as a checking or savings account.

A demand deposit account is defined by two characteristics: 

1. You can withdraw your funds at any time without penalty or prior notice
2. You hold a direct contractual relationship with the bank where the account is held. Your name (or your company’s name) is on the account as the legal owner, and the bank’s records reflect that directly.

Because DDAs are held at FDIC-insured banks, deposits are insured up to $250,000 per depositor, per insured bank, per ownership category. There’s no intermediary involved in that coverage — if the bank fails, the FDIC knows exactly who owns what.

It’s worth noting that money market deposit accounts (MMDAs) are sometimes classified alongside DDAs, but money market funds are a different product entirely. Money market funds are investment vehicles, not bank deposits, and they’re not FDIC-insured.

An FBO — meaning “for the benefit of” — could actually refer to a few different types of accounts, particularly because it’s not a strict regulatory term but rather a general industry term that can have a bit of nuance. That said, the common factor is that it refers to a model where there’s an intermediary, such as a fintech, that holds an account on behalf of its customers. The FBO model is usually used when a company wants to provide an online wallet, like your PayPal account or your CashApp balance. Fiat currency used on crypto exchanges is also often held in an FBO account.

FBO accounts are also used in real estate (escrow accounts) and by investment firms.

There are two primary kinds of FBO accounts in fintech.

Company-held FBO

The fintech company holds an account for the benefit of its customers. In this model, the fintech is the account owner for legal purposes and manages funds on behalf of its customers, but the funds in the account may still be payable on demand to the end user.

Bank-held FBO

In this model, a fintech’s partner bank that holds an account for the benefit of a company’s customers. In this model, the bank is the legal owner of the account and manages funds on behalf of the fintech’s customers using instructions from the fintech on how to allocate and disburse the funds based on customer transactions.

In both cases, the FBO account is also called a “pooled” account or “omnibus account”, because it essentially pools together customer funds into a single account at the bank. It’s then the job of the fintech intermediary to maintain a detailed record — a ledger — of which funds in the pooled account belong to which customers. This requires meticulous transaction tracking and matching, including recording all deposits, withdrawals, transfers, and other transactions, as well as matching individual customer transactions with the aggregate transactions reflected on a pooled account to ensure that all account balances are accurate and up to date.

DDAs and FBOs are fundamentally different types of accounts that may stand on their own or may need to work hand-in-hand. For example, an FBO model like one of the two primary fintech models mentioned above may have an underlying DDA — but the FBO layer ultimately changes the level of access that an end-user has to that account.)

Below, we break down some of the core areas where DDAs and FBOs are considerably different, and help shed light on what this means for an end-user in each of the cases.

Here are the key structural differences between a DDA and an FBO:

Ownership and access to the account

As mentioned already, the first way in which DDAs and FBOs differ considerably from one another is the way in which an end-user can engage with the account. With a DDA, an end-user has a direct relationship with their bank, and — by extension — direct, on-demand access to their funds. Funds in a DDA are payable upon demand, providing startups with the flexibility to manage their cash flow efficiently. This is particularly important for operational activities such as payroll, vendor payments, and other day-to-day expenses.

With an FBO, the end-user has an indirect relationship with the bank, because there’s an intermediary that facilitates that relationship. So a fintech that serves as a functional player between a banking customer and a chartered partner bank, for example, might operate under the FBO model.

While both DDAs and FBOs allow startups to make decisions about withdrawals, deposits, and transfers without needing approval from a third party, the direct relationship facilitated by DDAs also allows startups to take actions like executing a DACA (deposit account control agreement). 

A DACA allows the startup to use the deposit accounts as collateral on a credit facility or loan. You can also transfer ownership of the account in a contract or will.

Deposit insurance

The other major area of differentiation between DDAs and FBOs is how the two types of accounts are insured. With a DDA, insurance is pretty straightforward — deposits are directly insured by the FDIC up to $250,000 per depositor, per insured bank. This is simple and can give users peace of mind that any funds up to that insurance maximum would be recovered in the case of a bank failure, for example.

If a depositor needs more than the $250,000 of FDIC insurance, a sweep network can provide additional protection. A sweep network is a financial service that automatically spreads deposits in excess of $250,000 across multiple FDIC-insured banks. This gives the account holder millions in total coverage, while still managing a single primary bank account.

Things are less clear cut with FBOs, in which funds may be insured if properly structured and disclosed, but the coverage can depend on how an account is managed and the specific customer disclosures. FBOs may only qualify for what is known as “pass-through” FDIC insurance, where the end-user (and owner of the funds) won’t be directly insured. Instead, the insurance would need to pass through the intermediary account owner before going on to the end-user. In order for this to work well, all parties involved need to structure the accounts in proper accordance with FDIC requirements. Then in the event of a bank failure, it’s up to the FDIC to decide whether the requirements for pass-through insurance have been fully met and, thus, whether funds will receive FDIC protection.

Security and compliance

The safety of each account will mainly come down to how the account is managed and the specific safety measures that are put in place by a bank or third-party intermediary.

In both cases, there is heavy regulation by banking authorities such as the Federal Reserve, the FDIC, and state banking agencies. These institutions enforce stringent regulations prevent fraud and maintain the stability of the financial system. This regulatory framework includes regular audits and examinations, ensuring that banks adhere to high standards of security and operational integrity.

Then there’s an additional layer of fintech-specific compliance requirements in the event that the banking relationship involves a partnership between a bank and fintech, which can be true for both DDA and FBO accounts, as explained above. So the Consumer Financial Protection Bureau (CFPB), for example, will expect fintechs to adhere to state-specific fintech laws. Some fintechs — particularly those that hold money-transmission licenses — are also held to high transparency standards, with requirements about disclosing how customer funds are managed.

As for security measures meant to further protect end-users — things like end-to-end encryption and multi-factor authentication (MFA) — it will be up to the individual banks or fintechs to implement stringent security measures to ensure the safety of their customers and end-users.

Depending on how your company uses banking, one type of account may serve you better than the other. Here’s what to consider:

DDA:

• Direct ownership gives you full control over the account, including the ability to execute deposit account control agreements (DACAs) if a lender requires one as part of a venture debt or credit facility.
• FDIC insurance is straightforward. Your company is the depositor, and coverage applies directly up to $250,000 per bank, per ownership category.
• Account portability is simpler. Because you’re the legal account holder, you can transfer ownership, close the account, or move banks without depending on a third party to release funds.
• Liens and garnishments attach directly to the account. If your company faces a legal claim, a creditor can pursue the account directly because it’s in your name.
• Audit and compliance are cleaner. Bank statements, reconciliation, and tax reporting all tie directly to your entity, which simplifies annual audits and investor reporting.

FBO: Pros and considerations

• If you process transactions through digital wallets or crypto exchanges, you can expect that your money will be held in an FBO account.
• FDIC pass-through insurance is available but conditional. Coverage depends on whether the account is properly structured, the intermediary maintains accurate records, and the FDIC determines the requirements have been met at the time of a bank failure. Thoroughly review the fintech’s information on FDIC insurance before holding any substantial amount of money in an FBO account.
• DACAs and collateral assignments typically aren’t available in an FBO structure, since they don’t hold the account directly. This can affect your ability to secure certain types of financing.
• If the account is not FDIC-insured or you need to use the funds for a DACA, plan to transfer money from your FBO account to a standard DDA account on a regular basis.

Here’s how both a DDA and an FBO account would apply to a startup.

Scenario 1: Startup operating account

You’re a seed-stage SaaS company. You need a business checking account for payroll, vendor payments, and receiving revenue via ACH. Your also want to obtain a credit facility, and that needs a DACA.

In this case, a DDA is the standard fit. Your company opens a checking account directly at the bank (or through a fintech that provides individual DDAs, like Mercury). You’re the legal account owner. Your bank statements show your company name. The DACA can be executed because you hold the account directly. And if the bank were to fail, the FDIC would guarantee your funds.

Scenario 2: Fintech building a payment product

You’re building a marketplace that holds funds in escrow between buyers and sellers. You need to track balances for thousands of individual users and move money between them.

An FBO structure is designed for this. Your company opens an omnibus account at a partner bank, and each user gets a virtual sub-account tracked in your ledger. The bank sees one pooled balance, and your system tracks who owns what. 

You’ll need to maintain real-time reconciliation between your ledger and the bank’s records, and you’ll need to ensure the account is structured to qualify for FDIC pass-through insurance if you want to offer that protection to your users.

Your users don’t have a direct relationship with the bank. If something goes wrong with your platform (or your ledger), their access to funds depends on how well you’ve maintained records.

Just as you might care to dig into the financial health of your bank to feel more confident about where you’re storing your company’s money, you might be curious to better understand the exact structure and setup of an account.

The most straightforward way to know how your own account is set up is to review your account agreement and terms of service. These documents should explicitly state the type of account you have. In some cases, information about your specific account setup might also be available on your regular account statements or in any of the account information you can pull up in your online banking dashboard.

If all else fails, you can always reach out to your bank or fintech’s customer support team to make sure that you understand how your account is set up and what the implications of your particular account setup is.

Here’s a checklist you can use to determine what type of account you have.

• Check your account agreement or terms of service. Look for language like “demand deposit,” “checking account,” or “savings account” (DDA indicators) versus “for benefit of,” “omnibus,” “custodial,” or “pooled” (FBO indicators).
• Look at your account title. If it shows your company name directly (e.g., “Acme Corp — Business Checking”), that’s typically a DDA. If the title includes a third party’s name (e.g., “FinCo FBO Acme Corp”), you’re likely in an FBO structure.
• Check your FDIC coverage. If the provider’s website or disclosures reference “pass-through” FDIC insurance, that’s an FBO. Direct FDIC insurance (per depositor, per bank) indicates a DDA.
• Ask your provider directly. A straightforward question: “Is my account a direct demand deposit account at the bank, or is it held in a for-benefit-of (FBO) or omnibus structure?” Any reputable provider should be able to answer this clearly.

These terms appear throughout this article and in account documentation from banks and fintechs. 

DDA (demand deposit account): A bank account where the depositor can withdraw funds at any time without penalty or prior notice. Checking and savings accounts are common examples.

FBO (for the benefit of): An account held by one party (such as a fintech, a real estate company, or an investment firm) on behalf of another party’s customers. Not a formal regulatory term, but widely used in the industry.

Omnibus account: A pooled account that holds funds for multiple end users in a single account at the bank level. Often used interchangeably with FBO.

Sub-ledger (or virtual account): A record that tracks each individual user’s share of funds within an omnibus or FBO account.

Pass-through insurance: FDIC deposit insurance that “passes through” from a pooled or custodial account to individual beneficial owners, provided that certain recordkeeping and disclosure requirements are met.

DACA (deposit account control agreement): A legal agreement between a borrower, a lender, and the bank that gives the lender control over the borrower’s deposit account. A DACA is commonly used in venture debt and credit facilities.

Sweep network: A structure that distributes deposits across multiple FDIC-insured banks to increase total insurance coverage beyond the standard $250,000 limit at a single bank.