Skip to main content
Send funds from an Augustus account to a saved counterparty: a bank destination for an individual or business, or a verified crypto wallet for USDC.

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 its counterparty_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.
New fiat counterparties created through the API start in active. New crypto counterparties start in pending and need review 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.
POST /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.
GET /v1/payouts in the API Reference →

Retrieve a payout

Fetches the details of a single payout by its ID.
GET /v1/payouts/{id} in the API Reference →

Tracking reference

tracking_reference holds the identifier the payment network assigned to the payout, as an object with a type and a value:
It is null when no reference is available yet, and on SEPA, Faster Payments and blockchain rails. 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, the payout.returned webhook 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.
International returns can arrive net of correspondent fees, so reconcile a return on its reference, never on the amount. Windows and reasons are rail-specific: see ACH, SEPA, and SWIFT.

Webhooks

Subscribe to payout events for real-time updates.
POST /v1/webhook_subscriptions in the API Reference →

FAQ

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.
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.
The payout moves to failed and payout.failed fires. Funds remain in your account, and the failure field carries the reason.