- An operating account, using its rail-specific payment details (IBAN, sort code, ABA).
- A stablecoin wallet, from a crypto counterparty on a supported chain.
- An FBO account, whose payment details are issued in your customer’s name. See FBO accounts.
rail field specifies over which rail the funds were received. Rail-specific behavior (timing, availability, returns) is documented in ACH, Fedwire, and SWIFT.
Stablecoin deposits
Your Augustus wallet address can be retrieved from the Dashboard under Accounts → Details. Incoming deposits must come from a crypto counterparty on a supported chain; see Blockchain.Statuses
A deposit is a record of money that arrived: it appears once the funds are final and has a single status.
A deposit never changes status after that. Returning it does not touch the deposit: the return is its own resource with its own lifecycle, linked through the deposit’s
returns array; see Returns. The sender is referenced on the deposit as its counterparty_id where the rail delivers the sender’s account details. ACH does not share the originator’s account number, so inbound ACH deposits have counterparty_id: null.
Webhook events
Subscribe to the following events to be notified about deposits and returns:
A return is an outbound payment, so the
return.* events mirror the payout.* events one-to-one: same statuses, same order. See Returns.
Retrieve a deposit
Get a deposit ID from thedeposit.settled webhook payload or by listing deposits.
- 2026-05-01
- 2023-01-01
tracking_reference holds the identifier the payment network assigned to the incoming payment, as an object with a type and a value: uetr on SWIFT, imad on Fedwire, trace_number on ACH. It is null when no reference is available, and stablecoin deposits carry their on-chain hash in tx_hash. See Tracking reference for the format.
Returns
A return sends a deposit back to the original sender. Use it for deposits you cannot apply: an unexpected payment, a sender error, or funds you are not able to accept. The full amount travels back over the rail the deposit arrived on, to the account it came from. The rail pages state whether a return can be created through the API, within which window, and what the sender sees. A return is an outbound payment with the same lifecycle as a payout. It references the parent deposit and emitsreturn.* webhook events as it progresses; the deposit itself stays settled throughout.
The transitions are the same as for payouts, see Status transitions:
initiated to submitted to sent, failed from initiated or submitted, and sent to returned. failed and returned are final: to send the money back again, create a new payout.
Create a return
- 2026-05-01
- 2023-01-01
Retrieve a return
- 2026-05-01
- 2023-01-01
FAQ
What happens if a deposit doesn't match what I expected?
What happens if a deposit doesn't match what I expected?
The API has no concept of a matched or unmatched deposit: the payment is accepted and recorded like any other. Reconcile it against your own records, or return the funds if you can’t apply it.
How do deposits affect my balance?
How do deposits affect my balance?
Each successful deposit immediately increases the account’s available balance. See Balances.
Can I partially return a deposit?
Can I partially return a deposit?
No. Only full returns are supported. To send back a partial amount, use a payout.