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

# Atum payment lifecycle

> A payment goes through five stages: request, accept, select, deliver, confirm.

You sign a payment request and submit it to Atum's Payment Gateway. Independent settlement operators deliver it, and Atum verifies the delivery. You don't have to manage any of it.

## The five stages

```mermaid theme={"theme":"github-dark"}
flowchart LR
    A([Request]) --> B([Accept]) --> C([Select]) --> D([Deliver]) --> E([Confirm])
```

## Stage by stage

**1. Submit a payment request**

Your app builds the payment request (source account, destination account, amount) and signs it on your machine. On EVM, Tempo and Tron, the signature is a [Permit2](https://docs.atum.xyz/get-started/concepts/permit2-and-approvals.md) authorization for up to `max_source_amount`. Atum never sees your private key. See [Prepare a payment](https://docs.atum.xyz/get-started/prepare-a-payment.md).

**2. Atum accepts it**

The Payment Gateway checks the request and the signature, and returns a `payment_id`.

**3. Settlement operators send price quotes**

During the [quote window](https://docs.atum.xyz/get-started/concepts/deadlines.md#quote-window), independent settlement operators send price quotes for the route you asked for. When the window closes, the gateway selects one that has not expired. With [auto accept](https://docs.atum.xyz/get-started/concepts/deadlines.md#auto-accept), it selects the first valid quote as soon as it arrives. If none is usable, the payment fails; see [Deadline errors](https://docs.atum.xyz/get-started/concepts/deadlines.md#deadline-errors). You never contact settlement operators directly.

**4. The settlement operator delivers**

The selected operator deposits your funds in the [settlement vault](https://docs.atum.xyz/get-started/concepts/settlement-vault.md) on the source chain. Your balance drops here, before the recipient is paid. The operator then pays the recipient on the destination chain, before the [delivery deadline](https://docs.atum.xyz/get-started/concepts/deadlines.md#delivery-deadline).

**5. Atum confirms the delivery**

Atum verifies the payout on the destination chain and waits until it is [final](https://docs.atum.xyz/get-started/concepts/finality.md). The payment is then `completed`. The settlement operator is paid from the vault after that. If the payment is not delivered, your funds are refunded instead. See [Refunds](https://docs.atum.xyz/get-started/support/refunds.md).

## What `/status` shows at each stage

| Stage | `status` |
| - | - |
| Request, accept, select | `pending` |
| Deliver | `pending`, then `finalizing` once the payout is on the destination chain |
| Confirm | `completed` |
| Not delivered | a refund status; see [Refunds](https://docs.atum.xyz/get-started/support/refunds.md) |

What each status means: [Payment status](https://docs.atum.xyz/get-started/after-submission.md#payment-status).

## Who does what

You integrate only with the Payment Gateway. The roles in a payment are on [Network participants](https://docs.atum.xyz/get-started/concepts/participants.md), and who is responsible for what is on [Who owns what](https://docs.atum.xyz/get-started/support/who-owns-what.md).

## Next steps

* [After submission](https://docs.atum.xyz/get-started/after-submission.md) — follow a payment to the end and retry safely
* [Quickstart (using CLI)](https://docs.atum.xyz/get-started/start-building/using-the-cli.md) — send a real payment on testnet
* [SDK quickstart](https://docs.atum.xyz/get-started/start-building/build-with-the-sdk.md) — integrate payments into your app


## Related topics

- [What is Atum?](https://docs.atum.xyz/get-started/overview/what-is-atum.md)
- [Atum infrastructure](https://docs.atum.xyz/get-started/architecture/payment-rails-primer.md)
- [Payment request](https://docs.atum.xyz/get-started/concepts/payment-intent.md)
- [What is Atum ID?](https://docs.atum.xyz/get-started/identity/overview.md)
- [Glossary](https://docs.atum.xyz/get-started/reference/glossary.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.