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

# Transfer Statuses

> Map Pagou payout statuses into operator workflows, customer messaging, and reconciliation jobs.

Use one shared status map for product, operations, and support.

## API resource statuses

| Status        | Meaning                       | Typical action                       |
| ------------- | ----------------------------- | ------------------------------------ |
| `pending`     | accepted but not final        | monitor                              |
| `scheduled`   | queued for future execution   | keep scheduled                       |
| `in_analysis` | additional review is required | keep queued and visible to operators |
| `processing`  | settlement in progress        | wait for webhook or reconcile        |
| `paid`        | settled successfully          | mark payout completed                |
| `rejected`    | blocked before settlement     | route to operator review             |
| `cancelled`   | intentionally stopped         | close the request                    |
| `error`       | failed during processing      | investigate retry policy             |
| `unknown`     | not yet normalized            | reconcile immediately                |

## Webhook event mapping

Resource status and webhook event names are not identical.

* `payout.transferred` maps to resource status `paid`
* `payout.failed` maps to resource status `error`
* `payout.canceled` maps to resource status `cancelled`

## Why this matters

If your product displays event names as resource statuses, operator tooling becomes ambiguous. Keep one canonical mapping and reuse it across webhook handlers, dashboards, and reconciliation jobs.

## Read next

* [Transfer Events](/webhooks/transfer-events)
* [Transfer Reconciliation](/payouts/pix-out/reconciliation)