> 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/transactions/crypto-deposit-status-flow.md).

# Crypto deposit status flow

A crypto deposit is a payment received on one of your [account addresses](https://docs.txn.io/accounts/creating-account-address.md). Its status is the `simplifiedState` attribute returned by [Listing crypto deposits](https://docs.txn.io/transactions/listing-crypto-deposits.md), [Reading crypto deposit](https://docs.txn.io/transactions/reading-crypto-deposit.md) and [Listing transactions](https://docs.txn.io/transactions/listing-transactions.md).

Payments to invoice and channel addresses follow their own flows — see [Invoice status flow](https://docs.txn.io/invoices/invoice-status-flow.md) and [Channels deposit flow](https://docs.txn.io/channels/channels-deposit-flow.md).

| status                | Final state? | Description                                                                                                                                                                                       |
| --------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `pending`             | no           | Deposit detected on-chain and waiting for the required number of confirmations. See [Supported currencies](https://docs.txn.io/api-basics/supported-currencies.md) for confirmations per network. |
| `on_hold`             | no           | Deposit confirmed but flagged by compliance screening of the sending address. Txn's compliance team either releases it or rejects it.                                                             |
| `travel_rule_waiting` | no           | Deposit confirmed and waiting for Travel Rule information about the sender before it is credited. Only occurs when Travel Rule checks are enabled for your account.                               |
| `completed`           | yes          | Deposit credited to the account balance.                                                                                                                                                          |
| `rejected`            | yes          | Deposit rejected by compliance after a hold. The funds are not credited.                                                                                                                          |
| `cancelled`           | yes          | Deposit was never confirmed on-chain, for example because the transaction was dropped or replaced. No balance change.                                                                             |

```mermaid
stateDiagram-v2
    [*] --> pending : deposit detected
    pending --> cancelled : never confirmed
    pending --> completed : confirmed
    pending --> on_hold : confirmed, flagged by screening
    pending --> travel_rule_waiting : confirmed, Travel Rule applies
    travel_rule_waiting --> completed : sender information received
    on_hold --> completed : released
    on_hold --> rejected : rejected
```

A deposit released from `on_hold` follows the same path as any other confirmed deposit, including the Travel Rule step when it applies.

{% hint style="info" %}
Only `completed` deposits change the account balance. Treat `completed`, `rejected` and `cancelled` as final; every other status can still change.
{% endhint %}


---

# 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/transactions/crypto-deposit-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.
