> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/fiat-settlements/bank-withdrawal-status-flow.md).

# Bank withdrawal status flow

A bank withdrawal sends fiat from one of your accounts to a [bank account](/fiat-settlements/listing-bank-accounts.md) registered with Txn. Its status is the `simplifiedState` attribute returned by [Listing bank withdrawals](/fiat-settlements/listing-bank-withdrawals.md), [Reading bank withdrawal](/fiat-settlements/reading-bank-withdrawal.md) and [Listing transactions](/transactions/listing-transactions.md).

| status        | Final state? | Description                                                                                                   |
| ------------- | ------------ | ------------------------------------------------------------------------------------------------------------- |
| `pending`     | no           | Withdrawal accepted. The amount is reserved from the account balance while the transfer is prepared and sent. |
| `send_failed` | no           | The transfer to the bank failed. Txn retries it or cancels the withdrawal.                                    |
| `completed`   | yes          | Transfer sent and settled. The amount is debited from the account.                                            |
| `cancelled`   | yes          | Withdrawal cancelled before completion. The reserved amount is released back to the account balance.          |

```mermaid
stateDiagram-v2
    [*] --> pending : withdrawal created
    pending --> completed : transfer sent
    pending --> send_failed : transfer failed
    pending --> cancelled : cancelled
    send_failed --> completed : retried successfully
    send_failed --> cancelled : cancelled
```

{% hint style="info" %}
A `pending` withdrawal already lowers the account balance. Treat `completed` and `cancelled` as final; `pending` and `send_failed` can still change.
{% endhint %}

## Bank-side processing status

The `bankWithdrawalTransactions` object in `included[]` carries two further fields:

* **`paymentStatus`** tracks the transfer on the bank side. The usual sequence is `draft`, `created`, `validated`, `approved`, `processed`, `completed`; `on_hold` (compliance review) and `failed` (rejected by the bank, then retried or cancelled) are detours, and `cancelled` is final. `paymentStatus` can lag behind `simplifiedState`, so use `simplifiedState` to drive your logic.
* **`approvalStatus`** is the approval-workflow status for dashboard-initiated withdrawals subject to an approval rule. It is `null` for withdrawals created through the API. See the [Approvals feature guide](/getting-setup/approvals-feature-guide.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.txn.io/fiat-settlements/bank-withdrawal-status-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.