Skip to main content
A deposit is any incoming transfer credited to one of your accounts. Augustus creates a deposit record when funds arrive on:
  • An operating account, using its rail-specific payment details (IBAN, sort code, ABA).
  • A stablecoin wallet, from a linked wallet on a supported chain.
  • A virtual account, whose payment details are issued in your customer’s name. See Virtual accounts.
You receive a webhook for every deposit. Reconcile or return it from there. USD deposits arrive over ACH or Fedwire, international USD wires over SWIFT; the deposit’s 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 linked wallet on a supported chain; see Blockchain.
Verify the address, chain, and amount before sending. Transfers from non-linked addresses or unsupported chains may be lost.

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.

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 the deposit.settled webhook payload or by listing deposits.
GET /v1/deposits/{id} in the API Reference →

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: initiated, then submitted, then sent; failed when it could not be completed. A sent return that comes back from the sender’s bank moves to returned, which is final: to send the money back again, create a new payout. The deposit itself stays settled throughout. Returns reference the parent deposit and emit return.* webhook events as they progress.

Create a return

POST /v1/returns in the API Reference →

Retrieve a return

GET /v1/returns/{id} in the API Reference →

FAQ

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.
Each successful deposit immediately increases the account’s available balance. See Balances.
No. Only full returns are supported. To send back a partial amount, use a payout.