Payments Industry, chapter 13 of 20
Treasury & Bank Operations
The bank accounts behind a payments ledger: custodial FBO accounts, pass-through insurance, funding and prefunding, bank reconciliation, moving money safely.
A ledger says who owns what. A bank account says what exists. Payouts & Settlement follows a merchant's balance until it becomes a deposit; this chapter is the other side of that line: the accounts a provider actually holds, the money that moves between them every day, and the discipline that keeps the ledger and the bank telling the same story. It's the least visible part of a payments company and the one that ends it fastest. A provider that can't say whose money sits in an account, or that borrowed customers' money to cover its own gap, has a problem no amount of good API design will fix.
The Accounts You Run#
Separate accounts by whose money it is, never by convenience:
| Account | Whose money | What moves through it |
|---|---|---|
| FBO (custodial) | Merchants' | Settlement in, payouts out. In your name, titled for the benefit of the people it's held for |
| Reserve | Merchants', held against risk | Holdbacks in; releases and covered losses out. Some sponsor banks require it as its own account |
| Operating | Yours | Fees you've earned, payroll, vendors, every expense |
| Clearing | In transit | Where some setups land funds before sweeping them on. Zero balance by design, so anything left in it is a question |
| Collateral | Yours, pledged | What the sponsor bank or acquirer requires you to post (Becoming a Payment Provider) |
The cardinal sin is commingling: paying an expense out of the custodial account, even for a day to bridge a payroll gap, or leaving earned fees in it indefinitely so nobody can say which dollars are yours. Money crosses between custodial and operating only as a sweep the ledger computed, recorded on both sides, so at any moment the custodial account holds exactly what you owe the people it's for.
FBO Accounts and Pass-Through Insurance#
An FBO account holds many owners' money in one pool at the bank, in the provider's name. Whether those owners are protected if the bank fails depends on pass-through deposit insurance, and the FDIC only recognizes the custodial relationship if two things are true. The relationship has to be expressly disclosed in the bank's deposit account records, and the details of each owner's interest have to be ascertainable, either from the bank's records or from records the depositor (or someone it engaged) maintains "in good faith and in the regular course of business" (12 CFR 330.5(b)).
That second condition is your ledger. If it can't produce, on demand, who owns how much of the pool, the insurance the account was supposed to carry may not reach anyone. And the insurance has a limit people forget: it pays only when an insured bank fails. In the FDIC's words, it "does not provide consumers and businesses with general protection against the default, insolvency, or bankruptcy of any non-bank entities", which is to say it doesn't protect anyone from you, or from the middleware between you and the bank.
Synapse showed what that looks like. When the banking-as-a-service middleware company went bankrupt in 2024, its partner banks had, as the FDIC put it, "significant difficulties in obtaining, reviewing, and reconciling Synapse's records", and consumers lost access to their money for months. The FDIC responded on October 2, 2024 with a proposed rule for custodial accounts with transactional features: banks would keep records of each beneficial owner, the balance attributable to each, and their ownership category, and reconcile against those records "no less frequently than at the close of business daily". The comment period ran to January 16, 2025. As of October 2026 the Federal Register shows the proposal and its extension, and neither a final rule nor a withdrawal.
Build as if it were final anyway. A ledger that can hand your bank a per-owner balance file every day, summing to the account balance to the cent, is what makes the insurance real, and it's what every sponsor bank will ask for after Synapse whether or not the rule ever lands.
Funding the Day#
Money arrives on the acquirer's schedule and leaves on yours, and the gap between them is a treasury problem.
- Settlement arrives net or gross. Net settlement deposits sales minus refunds, chargebacks and fees as one number; gross settlement deposits sales and bills fees separately, often monthly. Net is simpler to fund and harder to reconcile: one deposit has to be decomposed into thousands of ledger entries from the processor's reports before anything can match (Interchange & Pricing covers where the fees come from).
- Payouts can lead settlement. Next-day or instant payouts promise merchants money before the acquirer has sent it. The difference comes from your own funds or a credit line, and it's a loan to your merchants until settlement lands: record it as a receivable from the acquirer, moved into the custodial account explicitly, never covered by letting the account run short.
- Float has an owner. Money sits in the custodial account between settlement and payout. Who earns interest on it, if anyone, is a question for your bank agreement and your counsel, not an assumption to build a business model on.
- Fees are swept, not skimmed. Once a day, the ledger computes what you've earned and the system moves exactly that from custodial to operating. The balance in the custodial account is never a number anyone eyeballs to decide what's theirs.
Bank Reconciliation Is Its Own Discipline#
Ledger reconciliation asks whether your books balance. Bank reconciliation asks whether the bank agrees, and they fail in different ways: a ledger can balance perfectly while a wire you think you sent never left.
Banks report in two families of formats. In the US, BAI2 files are still everywhere. ISO 20022 replaces them with camt.053, the end-of-day statement of booked entries; camt.052, an intraday report of the account; and camt.054, notifications of individual debits and credits. Expect several versions across your banks and build a parser per bank, not one that assumes the standard means one shape.
Reconciliation is matching, and the shapes are uneven:
- One to one: a wire matches a transfer you initiated, by your end-to-end reference.
- One to many: a net settlement deposit matches the thousands of transactions, refunds and fees it settles.
- Many to one: a payout batch leaves as one debit and has to match every payout in it.
What doesn't match goes to an unmatched-items queue, each item with an owner, an age and a deadline. Tolerances exist only for documented costs with a reason, like a wire fee your bank charges per transfer; "within five dollars" is how a slow leak becomes a large one. Run it three ways every day, ledger against processor reports against bank statements, and treat an unexplained break as a stop: no payout run until someone knows whether it's a bug or a loss (Payouts & Settlement has the merchant-facing side of the same check). Intraday reports earn their keep here too: they tell you whether today's payouts are funded before the bank's cutoff, not after.
Reserves and Negative Balances Are Cash#
A reserve in the ledger is a promise that the money exists. Whether it's an earmarked part of the custodial account or a separate account the sponsor bank requires, the cash has to be there on the day a dispute or a risky merchant needs it, and its release dates are treasury events: they change what you can pay out that day.
Negative balances are the reverse. When refunds and lost disputes take a merchant below zero and you've already paid them out, the custodial account is short by that amount until you recover it. Fill the gap from operating funds, recorded as a receivable from the merchant, the moment it appears. The alternative, letting other merchants' money cover it, is commingling by another name.
Moving Money Safely#
Every transfer out of a custodial account is irreversible enough to deserve ceremony.
- Know the cutoffs. The Fedwire Funds Service runs from 9:00 p.m. ET the previous day to 7:00 p.m. ET, with customer transfers cut off at 6:45 p.m. ET; your bank's own cutoffs are earlier, and they're the ones that matter. ACH & Bank Transfers covers the ACH windows. Schedule sweeps, prefunding and payout runs backward from them.
- Wires for large, final moves. Prefunding, collateral and bank-to-bank rebalancing go by wire because a wire is final; volume goes by ACH because it's cheap. The finality cuts both ways, which is why wires get the strictest controls.
- The system initiates, people approve. No movement out of a custodial or operating account is typed by hand. The system creates the instruction from the ledger, and a second person approves it, with thresholds that add approvers as amounts grow. Nobody can both create and release a wire, and a change to a beneficiary's bank details is its own approved change, for the reasons Vendor Payouts gives.
- Lock what shouldn't move. Positive pay on any account that issues checks, and ACH debit blocks or filters on accounts nobody should be debiting, which is usually all of them.
- Initiate idempotently. A transfer instruction carries a key derived from what it represents, like the date and purpose of a sweep (Idempotency). Many bank APIs don't honor idempotency keys, so store the intent before sending, put your own end-to-end reference on the payment, and after a timeout ask the bank about that reference before sending anything again (Retries & Timeouts).
- Plan for a second bank. One sponsor bank is one point of failure for every payout you make. A second relationship gives you somewhere to go, at the price of splitting custodial funds and doubling reconciliation, the same trade Processor Routing makes for card processing.
- Unclaimed money still has an owner. Uncashed checks and abandoned balances eventually belong to a state, not to you; Vendor Payouts covers escheatment.
Safeguarding Outside the US#
In the UK, payment and e-money institutions don't rely on deposit insurance; they safeguard customers' funds under the FCA's rules, and those rules just got stricter. The FCA published PS25/12 on 7 August 2025, and its Supplementary Regime came into force on 7 May 2026. Firms now reconcile safeguarded funds at least once every reconciliation day (weekends, bank holidays and days when the relevant foreign markets are closed excepted), keep a resolution pack describing where funds are held and how they'd be returned, file a new monthly safeguarding return, and, unless they've safeguarded no more than £100,000 over the past 53 weeks, arrange an annual safeguarding audit by a qualified auditor. A CASS-style end state is planned for after the underlying legislation is repealed.
Read it as the US direction of travel written down: daily reconciliation, records that let someone else return the money if you can't, and an outside party checking.
The Engineering#
- A treasury ledger, separate from the merchant ledger. One account per real bank account, every movement as double entries (Payment States & Ledgers). The merchant ledger's total liability to merchants, plus anything in transit, equals the cash in custodial accounts; that equation is checked daily and alerts when it doesn't hold.
- Per-owner balances on demand. The file your bank or a regulator would need to pay each owner directly is a scheduled job, not a project you start during a crisis.
- Every movement is a record before it's a transfer. Intent stored, approvals attached, bank reference captured, bank confirmation matched. A transfer that exists at the bank and not in your records is the worst finding a reconciliation can produce.
- Breaks stop payouts. A reconciliation job that only reports is a dashboard. One that holds the next payout run on an unexplained difference is a control.
References#
Specifications
- 12 CFR 330.5: Recognition of deposit ownership and fiduciary relationships, the disclosure and recordkeeping conditions for pass-through deposit insurance
- FDIC: Recordkeeping for Custodial Accounts (proposed rule, October 2, 2024), beneficial-owner records, daily reconciliation, Synapse, and what deposit insurance doesn't cover
- FDIC: Recordkeeping for Custodial Accounts; Extension of Comment Period, the comment period extended to January 16, 2025
- FCA: PS25/12, Changes to the safeguarding regime for payments and e-money firms, published 7 August 2025, Supplementary Regime in force 7 May 2026
Reference
- Federal Reserve Financial Services: Fedwire Funds Service Operating Hours, the funds-transfer day and the 6:45 p.m. ET customer transfer cutoff
In practice
- CMS: FCA strengthens safeguarding regime for payments and e-money firms, daily reconciliations, the resolution pack, the monthly return and the audit exemption
- SEPA for Corporates: The difference between camt.052, camt.053 and camt.054, intraday reports, statements and notifications