> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augustus.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat the published Augustus OpenAPI specification (https://api.augustus.com/openapi/2026-05-01.json) and the current API-reference pages as the source of truth for endpoints, request/response schemas, enum values, webhook event names, and required headers.
> Prefer the 2026-05-01 Banking API and @augustusbank/typescript-sdk for all new integrations. The 2023-01-01 API is a separate, older surface covering two products — Open Banking (instant bank transfer) checkout and refunds, and Manual Bank Transfer (MBT); use it only when one of those products is specifically required.
> Cite or link the relevant docs.augustus.com page when answering integration questions.
> Do not infer support for currencies, networks, scopes, account types, or operations that are not present in the current documentation.
> Use the sandbox base URL (https://api.sandbox.augustus.com) and placeholder credentials in examples. Never include or request a real API key.
> The Augustus docs MCP server (https://docs.augustus.com/mcp) provides documentation search and retrieval only; it does not execute authenticated Augustus API actions.

# Payments

> How money moves in and out of your Augustus accounts: deposits, payouts, counterparties, and returns, and the rails that carry them.

Four resources cover everything that moves money in or out of an account. Deposits, payouts, and returns exist in both APIs; counterparties are specific to the 2026-05-01 API; the 2023-01-01 API takes the destination inline on the payout.

<CardGroup cols={2}>
  <Card title="Deposits" icon="arrow-down" href="/docs/payments/deposits">
    Incoming transfers credited to one of your accounts. A deposit appears once the funds are final and has one status, `settled`.
  </Card>

  <Card title="Payouts" icon="arrow-up" href="/docs/payments/payouts">
    Outgoing transfers from an account to a bank account or wallet. A payout moves `initiated` → `submitted` → `sent`, or ends `failed` or `returned` *(2026-05-01 statuses)*.
  </Card>

  <Card title="Counterparties" icon="address-book" href="/docs/payments/payouts#key-fields">
    The bank account or wallet on the other side of a payment, saved once and referenced by `counterparty_id`. Every payout targets one. Deposits carry one where the rail delivers the sender's account details; ACH does not share the originator's account number, so inbound ACH deposits have none.
  </Card>

  <Card title="Returns" icon="rotate-left" href="/docs/payments/deposits#returns">
    A deposit sent back to its sender. An outbound payment with the same lifecycle as a payout, linked to the deposit it undoes; the deposit stays `settled`.
  </Card>
</CardGroup>

## Where to find them

| Resource       | 2026-05-01 API                                                            | 2023-01-01 API                                                               | Dashboard                                                                |
| -------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Deposits       | [`/v1/deposits`](/api-reference/deposits/list-deposits)                   | [`/api/service/deposit/retrieve`](/api-reference/deposit/retrieve-a-deposit) | [Payments → Deposits](https://dashboard.augustus.com/dashboard/deposits) |
| Payouts        | [`/v1/payouts`](/api-reference/payouts/list-payouts)                      | [`/api/service/payout/list`](/api-reference/payout/list-payouts)             | [Payments → Payouts](https://dashboard.augustus.com/dashboard/payouts)   |
| Counterparties | [`/v1/counterparties`](/api-reference/counterparties/list-counterparties) | Inline `destination` on the payout                                           | Shown on the payout or deposit they belong to                            |
| Returns        | [`/v1/returns`](/api-reference/returns/list-returns)                      | [`/api/service/return/create`](/api-reference/return/create-a-return)        | On the deposit: status in the list, details in the deposit view          |

Every completed movement also lands as a booked [transaction](/docs/transactions/overview) on the account, and each state change fires a [webhook](/v1/webhooks).

## Rails

The rail is how the money travels. It follows from the currency and the counterparty's financial address; for USD you choose it on the payout. Each page covers timing, limits, and return behavior.

<CardGroup cols={3}>
  <Card title="ACH" href="/docs/rails/ach">
    USD, batch-based, same-day or next-day. Returns within the network windows.
  </Card>

  <Card title="Fedwire" href="/docs/rails/fedwire">
    USD, real-time and final. No return procedure on the network.
  </Card>

  <Card title="SWIFT" href="/docs/rails/swift">
    International USD over the correspondent network. Returns can arrive net of fees.
  </Card>

  <Card title="SEPA" href="/docs/rails/sepa">
    EUR, standard and instant.
  </Card>

  <Card title="Faster Payments" href="/docs/rails/fps">
    GBP, near-instant.
  </Card>

  <Card title="Blockchain" href="/docs/rails/blockchain">
    Stablecoins to and from linked wallets on supported chains.
  </Card>
</CardGroup>

Test any of these without moving real money: see [Sandbox Mode](/docs/basics/sandbox-mode) and the [Simulations](/v1/simulations) walkthrough.