Skip to main content
A transaction is the ledger record of money that moved on one of your accounts: the line item on your bank statement. Every deposit, payout, and return produces one when it books. Transactions are immutable and always booked; money still in flight is visible on the payout or return it belongs to, never as a transaction. Use transactions for reconciliation, custom reporting, and balance time series. For the current balance, use Balances. For CSV exports and PDF statements, see Reports.

What a transaction carries

  • Direction and amount: credit or debit relative to your account, the absolute amount, and the account’s currency.
  • The account it was booked on.
  • The cause: the deposit, payout, or return that moved the money, so you can open it on its own endpoint.
  • The other party: the bank account or wallet on the far side, and the saved counterparty it resolved to where there is one.
  • References: the remittance text that travelled with the transfer and the network reference where the rail has one (for example the UETR on SWIFT).
  • Booking time: when the movement was recorded on the Augustus ledger. A credit books when the funds settled on your account. A debit books when the payout or return was initiated, which is when the amount leaves your available balance.

List transactions

Both versions list transactions per account, narrowed by a booking-time window, and paginate with a cursor.
GET /v1/transactions in the API Reference →

Retrieve a transaction

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

Reconcile against your records

  • Find the cause. Open the deposit, payout, or return the transaction points to and match it to your own record by its ID or by the remittance text you set.
  • Match returns by reference, not by amount. A return that references the original payment moves the payout to returned; one that does not arrives as a new deposit. International returns can come back net of correspondent fees, so correlate on the payment reference, never on the amount. See Returned payouts.
  • Point-in-time balance.
The transaction object carries no running balance. Take the current balance from GET /v1/accounts/{id}/balance and walk backwards over the transactions returned by GET /v1/transactions, subtracting each credit and adding back each debit by booked_at.

In the Dashboard

Transactions lists the same movements across all your accounts, with filters by date, status, payment method, and account. Open a row to see the related deposit, payout, or return. The Dashboard is an activity view: outgoing movements also appear while in flight and when they have failed. The API returns booked transactions only.