<!-- tempo-docs-context -->
> Source: [/docs/routes/delivery](https://tempo.com/developers/docs/routes/delivery.md)
> Section: [Routes](https://tempo.com/developers/docs/routes.md). Move stablecoins between Tempo and other networks: try a route, set up API access, choose a supported route, quote it, accept deposits or make a transfer, and track delivery. Routes is in beta; see the introduction for access.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

# Track delivery

A successful source-chain transaction starts a route. The route completes when the destination receives funds or the refund lands. Keep the Routes object ID with your payment record and follow its status.

<span id="read-the-transfer-or-deposit" />

<span id="check-status" />

## Read the status

Read status with a key that has `routes:read`:

| Flow | Read | Request builder |
| --- | --- | --- |
| Deposit address | `GET /v1/routes/deposits?depositAddress=…`, then `GET /v1/routes/deposits/{id}` for each deposit | [Track deposits](https://tempo.com/developers/docs/routes/deposits#track-deposits) |
| Transfer | `GET /v1/routes/transfers/{id}`, after you register the source transaction hashes | [Confirm the transfer](https://tempo.com/developers/docs/routes/transfers#confirm-the-transfer) |

An `active` deposit address can receive deposits. Each deposit has its own status.

<span id="keep-delivery-and-refund-states-distinct" />

<span id="handle-failures" />

## Delivery states

| State | Applies to | Application behavior |
| --- | --- | --- |
| `awaiting-source` | Transfers | Source funding has not been registered. |
| `detected`, `bridging`, `settling` | Deposits | Funds are moving through delivery. Keep the deposit pending. |
| `processing` | Transfers | Keep the payment pending. |
| `completed` | Both | Reconcile the delivered amount and destination transaction references. |
| `action-required` | Both | Inspect `statusReason` and the endpoint's instructions. |
| `expired` | Transfers | Inspect source funding before starting a replacement. |
| `refunding` | Both | Keep the refund pending. |
| `refunded` | Both | Reconcile the refund amount and transaction references. |

Use the full [transfer](https://tempo.com/developers/docs/api/routes/transfers) or [deposit](https://tempo.com/developers/docs/api/routes/deposit-addresses) reference for the lifecycle and response fields. Do not automatically send the payment again when it is pending or being refunded.

## Track refunds

Keep `refunding` separate from `refunded`. Reconcile the returned refund amount and transaction references before updating the customer's balance.

<span id="retry-a-create-request-safely" />

<span id="retry-a-create-request" />

## Retry without duplicates

If a create request gets no response, the object may still exist. Retry with the same [idempotency key](https://tempo.com/developers/docs/routes/api-setup#set-idempotency-keys) and unchanged inputs to receive the original result before creating a replacement.

## Use funds after delivery

After the destination account receives stablecoins, it can [send a payment](https://tempo.com/developers/docs/guide/payments/send-a-payment), [deposit into Earn](https://tempo.com/developers/docs/earn/integrate), or [deposit into a Zone](https://tempo.com/developers/docs/zones/deposit). Each is a separate operation. Direct Routes transfers into a vault or Zone are not implemented; their endpoints return HTTP `501`.
