Skip to main content
A virtual account is an end-user subledger under an FBO deposit account. It tracks your customer’s balance. It sits in a program that Augustus holds for the benefit of your customers, it has its own balance and its own account number, and it sends and receives payments in that customer’s name. FBO stands for “for benefit of”: the program is titled Augustus for the benefit of Acme Inc’s customers, and Augustus sets that title when it configures the program. Each virtual account holds its own balance in the ledger. Augustus reports that balance per customer and the total per program.

How it is built

The objects are explained under Account structure.

FDIC insurance

FDIC coverage can pass through the FBO program to each account holder who owns the funds, whether an individual or a legal entity. The limit is $250,000 per account holder. Accounts owned by the same account holder at Augustus National Bank count toward one limit, including deposits held directly or through other FBO programs. Multiple accounts, account numbers or programs do not increase that limit. Example: Globex LLC holds $200,000 in each of two FBO virtual accounts at Augustus National Bank. Assuming pass-through requirements are met, both accounts are in the same ownership category and Globex has no other deposits counting toward that limit, the $400,000 total has $250,000 insured and $150,000 uninsured. See the FDIC guide to pass-through coverage.

Status

Virtual accounts use the model shared by every Augustus account: pending, active, frozen, closed. See Account status. If you have permission to manage the accounts in a program, you can freeze, unfreeze and close them through the API. That is the case for your FBO program; operating accounts are managed by Augustus. A new virtual account opens in pending and is activated by Augustus once verification clears, usually within minutes. If additional information is required (enhanced due diligence, a sanctions hit, or an identity mismatch), the virtual account stays pending and Augustus contacts you with next steps.

Money in

Each virtual account has its own account number, so funds arriving over US rails settle into the right virtual account without any routing on your side. When a credit arrives, Augustus matches the destination account number to the virtual account, performs sanctions and AML screening, credits its balance and fires deposit.settled. If a credit cannot be matched (wrong account number, sanctions hit, frozen account), Augustus returns it over the originating rail and notifies you with the reason. See Deposits.

Money out

You initiate payouts from the customer’s virtual account: pass its ID as account_id. The customer’s name appears as the originator on the rail, which is payment on behalf of (PoBo). Funds are debited from the virtual account when the payout is initiated. The request and response shapes are the same as for any other payout. When the counterparty’s address belongs to an Augustus account, the payout settles on Augustus’s books instead of going out on a rail. It reaches sent within seconds, the receiving account gets a deposit.settled event, and both records carry rail: "internal". Statuses and webhooks are the same as for any other payout, and no configuration is needed.

Integration

Account, account holder and account program endpoints sit under /v1/accounts, /v1/account_holders and /v1/account_programs. They follow the same auth, error, and pagination conventions as the rest of the 2026-05-01 API.
Sandbox. Create a test program with POST /v1/simulations/account_programs, then run the steps below against it. The Simulations walkthrough covers the full flow including deposits and payouts.
1

Register the account holder

Pass the program ID, the holder type and the identity data for that type. The fields per type are listed under Account structure.
The holder is screened asynchronously and starts in pending. Subscribe to account_holder.active to know when it clears.
holder_type accepts natural_person or business. individual is not a valid value.
POST /v1/account_holders in the API Reference →
2

Create the virtual account

The response does not repeat account_program_id or account_holder_id. Store the virtual account’s ID against your customer record; to list a program’s virtual accounts later, filter by account_program_id.POST /v1/accounts in the API Reference →
3

Give the customer their payment details

The routing and account number on the aba entry in financial_addresses, together with the customer’s name, are what a sender needs to pay in over ACH or Fedwire. The bic entry carries the bank’s BIC with the same account number. For SWIFT, the sender needs the full wiring instructions; see Receive USD internationally.
4

List the virtual accounts in the program

account_program_id is required, so the list only returns the virtual accounts in that program. Your operating accounts sit in their own program.GET /v1/accounts in the API Reference →
5

Read balances

Each virtual account has its own balance. The program balance is the sum across every virtual account in the program.
Program balance
Note the two shapes: the account balance keys on account_id, the program balance on id.GET /v1/account_programs/{id}/balance in the API Reference →