Supported currencies
- Fiat: EUR, GBP, USD.
- Stablecoins: USDC (Ethereum, Solana, Polygon).
Create a payout
Sending money is two API calls: save the destination once as a counterparty, then create the payout against itscounterparty_id. The counterparty is reusable: for every later payout to the same destination, only the second call runs. Create a separate counterparty for each bank destination or wallet address.
- 2026-05-01
- 2023-01-01
New fiat counterparties created through the API start in POST
active. New crypto counterparties start in pending while Augustus verifies them; wait for active before payouts. The USDC example uses a saved counterparty and checks that it is active and unblocked. See Counterparty lifecycle for initial states, review and payment eligibility.Find each Account ID in the Dashboard under Accounts → Details.
/v1/counterparties in the API Reference →POST /v1/payouts in the API Reference →Key fields
Rail behavior (timing, limits, returns) lives on the rail pages: ACH, Fedwire, SWIFT, SEPA, Faster Payments, Blockchain.
List payouts
Fetches all payouts on your account. Filter and paginate as needed.- 2026-05-01
- 2023-01-01
Narrow the list with any combination of these optional query parameters:Keep the same filters on every page: a cursor is tied to the filters it was issued for. See Pagination.GET
/v1/payouts in the API Reference →Retrieve a payout
Fetches the details of a single payout by its ID.- 2026-05-01
- 2023-01-01
Tracking reference
tracking_reference holds the identifier the payment network assigned to the payout, as an object with a type and a value:
null when no reference is available yet, and on SEPA, Faster Payments and blockchain rails. A Fedwire payout gets its IMAD, and an ACH payout its trace number, no later than when the payout moves to sent. Some payouts get it earlier: a wire once it is submitted to the Fed, an ACH entry once the batch file carrying it is accepted. Until then tracking_reference is null. Stablecoin payouts carry their on-chain hash in tx_hash. Quote the reference when you or your counterparty’s bank trace a payment.
View payouts in the Dashboard.
Statuses
For international USD payouts over the correspondent network, see SWIFT.
Status transitions
returned is final. failed ends normal processing; in exceptional cases Augustus corrects a payout from failed to sent after an investigation, and payout.sent fires. sent is final on the rail, but the payout can still move to returned when a matched return arrives, which can be days later; the rail pages give the windows. No other transition exists: a payout never moves from sent to failed, and a return that cannot be matched leaves the payout at sent and arrives as a new deposit.
When to retrieve a payout. Every webhook payload is a full snapshot of the payout at the time of the event, so you do not need to retrieve the payout to learn its status. Deliveries can arrive out of order or more than once: rank the statuses initiated < submitted < sent < returned and ignore an event whose status ranks below the one you already stored. If you receive payout.sent after payout.failed, retrieve the payout rather than discarding the event. Otherwise retrieve the payout only when an event references one you do not know, or to catch up after your endpoint was unavailable. See Event ordering.
Returned payouts
The receiving bank can send a payout back after it was sent, for example when the account is closed or the receiver refuses the payment. What happens next depends on whether Augustus can match the return to the payout it undoes:- Linked. The return references the original payment (ACH: a return entry carrying the trace number; SWIFT and Fedwire: a pacs.004 carrying the UETR). The payout moves to
returned, thepayout.returnedwebhook fires, and the amount is credited back to your account as a transaction that points at the payout. No deposit is created. - Unlinked. The funds come back as a fresh, unreferenced payment. They arrive as a new deposit that looks like any other incoming transfer, and the payout stays
sent. This is the usual case on Fedwire: a settled wire is final, and a receiving bank that agrees to send funds back does so with a new wire; see Finality and cancellation.
Tracking events
A payout’s status says where it stands. Its tracking events say how it got there: Augustus records each step of a payout to a counterparty as a payout tracking event, numbered in order. List them for a payout with GET/v1/payout_tracking_events, which needs the payout_tracking_events:read scope, or subscribe to payout_tracking_event.created to receive each event as it is recorded.
source: "augustus":
For SWIFT payouts, Augustus also records the hops SWIFT gpi reports as the payment moves through the correspondent chain, with
source: "swift_gpi":
When the beneficiary’s bank reports that it received the payment but is holding it before crediting, Augustus records a
forwarded step that is not terminal, with status_reason.code set to CREDIT_PENDING. Tracking continues until the bank credits or rejects the payment.
The API also defines accepted and settled, which Augustus does not record today, and source can also be other. New values may be added to milestone, source, scope and status_reason.code: ignore a value you don’t recognise rather than failing.
institution and from_institution each carry a name and an identifier ({ "type": "bic", "value": "CHASUS33XXX" }); either can be null when the source doesn’t report it. A BIC is always 11 characters: an 8-character BIC is padded with XXX, so you can compare the same bank across events. Two banks can share a name, so match on the BIC when there is one.
Filter the list by milestone, is_terminal, or created_at.gte and created_at.lte, and retrieve a single event with GET /v1/payout_tracking_events/{id}. The list is newest first and uses cursor pagination.
Tracking events complement the payout status and its payout.* webhooks; they don’t replace them. Keep driving your payout state from the status.
Webhooks
Subscribe to payout events for real-time updates.- 2026-05-01
- 2023-01-01
FAQ
Which rail does a payout travel on?
Which rail does a payout travel on?
EUR payouts go over SEPA, GBP over Faster Payments, and USD over ACH, Fedwire, or SWIFT depending on the
rail you select. USDC payouts settle on-chain; see Blockchain. In the Dashboard, the payout dialog lists only the rails the destination can be paid on and lets you choose one; see Dashboard.Can I cancel a payout?
Can I cancel a payout?
Not through the API. Once a payout is submitted to the network, cancellation is no longer possible; before submission, support may be able to stop it. The rail pages carry the specifics.
What happens when a payout fails?
What happens when a payout fails?
The payout moves to
failed and payout.failed fires. Funds remain in your account, and the failure field carries the reason.