Provision Sub-Accounts for Every Customer With Modern Treasury Payments

A programmatic sub-account is a unique account — with a real routing number and account number — provisioned via API on behalf of a platform’s end customer. Unlike ledger balances in a shared omnibus account, each sub-account is a distinct named account that can send and receive funds independently across ACH, RTP, FedNow, and wire rails.

A ledger balance tracks how much of a shared (omnibus) account belongs to a given customer. A sub-account is the customer’s own unique account — real routing number, real account number, separate from every other customer’s funds. Platforms that need true fund segregation, FBO compliance, or per-customer audit trails typically require sub-accounts, not ledger balances.

Sub-accounts are provisioned via a single API call and typically resolve in seconds. Routing and account numbers are returned in the API response. Platforms can provision thousands of accounts programmatically without manual bank setup or per-account onboarding delays.

Every sub-account can send and receive ACH, RTP, FedNow, and wire without reconfiguration. The same account number and routing number work across all rails. Platforms select the rail at the payment order level, not the account level.

Yes. Modern Treasury’s sub-account architecture supports FBO (for benefit of) structures in which a platform holds funds on behalf of its customers in legally segregated accounts. Each sub-account maintains its own real-time balance and transaction history, which supports the audit trail requirements common to FBO compliance.