Skip to main content
Every balance at Augustus is an account. A product is defined by the program the account sits in, who holds it, and how many addresses point at it. This page explains the four objects, how the three products are composed from them, and where the API stops short of the model today.

Account structure

List the programs Augustus has configured for you. A program is active or frozen; closed programs are not returned.
Register a holder by passing the program ID, the holder type, and the identity data for that type. The data is screened against the program’s policy. On a positive decision the holder becomes active and the account_holder.active event fires. A holder is pending, active or closed.
  • legal_name
  • residential_address
  • date_of_birth
  • identification, ssn or itin for US persons, id (generic government-issued ID) for non-US
  • country_of_citizenship
To onboard an existing holder onto another program, register them again against that program ID. This triggers a separate screening and may require additional information.
Where the program allows it, you open an account by passing the program ID and the holder ID. The account opens in pending with one address allocated, and Augustus activates it once verification clears. Where the program does not allow self-service, Augustus opens the accounts for you.
Every entry in financial_addresses carries a type and the fields a sender needs on that rail. account_holder_name is the name the address carries on the rail: yours on an operating account, your customer’s on an FBO account.An address is allocated when the account opens. Additional addresses are requested from Augustus based on the program’s policy and supported rails.

How the products are built

Operating, FBO and correspondent are product names. The API has one account type, account, and a product is defined by the program an account belongs to and how many addresses point at it. The example names below run through all three guides: Acme Inc is the Augustus customer, Acme Bank is that customer when it is a bank, and Jane Doe, John Roe and Globex LLC are its customers.
Three panels side by side. A, operating account: one account program containing one account for Acme Inc with one address. B, FBO accounts: one account program held for the benefit of Acme Inc's customers, containing separate accounts for Jane Doe, John Roe and Globex LLC, each with its own address. C, correspondent account: one account program containing a single Acme Bank account carrying three addresses, one per bank customer.Three panels side by side. A, operating account: one account program containing one account for Acme Inc with one address. B, FBO accounts: one account program held for the benefit of Acme Inc's customers, containing separate accounts for Jane Doe, John Roe and Globex LLC, each with its own address. C, correspondent account: one account program containing a single Acme Bank account carrying three addresses, one per bank customer.

How the three products are composed from the four objects

Operating accounts (DDA)

Accounts in your own name for operations and treasury.

FBO accounts

Accounts you open for your customers, each with its own balance and account number.

Correspondent accounts

One account with many addresses, for banks paying and collecting in their customers’ names.

Account status

The optional status filter on GET /v1/accounts accepts pending, active, and frozen only. You cannot filter for closed accounts; they are still returned by an unfiltered list, and closed is a valid value on the account resource.

What the API does not show yet

The structure above is how accounts are organised. The API exposes it only in part today:
  • Program and holder are write-only on the account. account_program_id and account_holder_id are supplied on create and are not returned on the account resource. To find the accounts in a program, filter GET /v1/accounts by account_program_id. To find one customer’s account, store the account ID against your customer record when you create it.
  • One address per account. financial_addresses is an array and holds one entry. Additional addresses cannot be requested through the API yet.
  • Programs are read-only. Augustus creates and configures them. In the sandbox, POST /v1/simulations/account_programs creates one so you can test the FBO flow end to end.
  • No address endpoints. Addresses exist only as the financial_addresses field on the account.
  • Program balance for FBO programs only. Other programs hold their accounts side by side without a total, and the program balance endpoint returns an error for them. Read the balance of each account instead.
  • Two balance shapes. The account balance resource keys on account_id; the program balance resource keys on id.