> For the complete documentation index, see [llms.txt](https://docs.finrax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finrax.com/references/crypto-withdrawals.md).

# Crypto withdrawals

In this section we'll go through the endpoints you'll need to execute crypto withdrawals.

By utilizing this functionality, you will be able to send payouts to your customers in cryptocurrencies without prior holding it, thus we remove the crypto volatility and complexity.

The Crypto withdrawals work on a Buy\&Send basis. The moment you initiate the withdrawal request, we'll purchase the given cryptocurrency on a [mid-market rate](https://blog.finrax.com/articles/why-is-your-crypto-payment-processing-not-working) and send it immediately to your customer.\
In addition we allow you to specify the amount in fiat currency to denominate the amount in a currency you are used to and only specify the cryptocurrency you wish to send.

{% hint style="warning" %}
Bear in mind that we don't cover on-chain fees for withdrawals. Please make sure to get familiarised with the on-chain fees per currency, before executing a withdrawal.\
The on-chain fees are deducted from the selected amount in the withdrawal request i.e. if you wish to withdraw 1 Litecoin,  the recipient will receive 1 Litecoin minus the associated on-chain fee. List of current on-chain fees [here](https://finrax.com/supported-currencies-withdrawal-metadata). 
{% endhint %}

### Withdrawal statuses

| Status    | Description                                                                                                                                                                                                                                                     |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| NEW       | We've received your Withdrawal request and it has passed our initial validations.                                                                                                                                                                               |
| PENDING   | The withdrawal request has passed the required steps i.e. we've bought the requested cryptocurrency and have deducted your balance. The transaction is to be broadcast on the blockchain network.                                                               |
| COMPLETED | The blockchain transaction has been validated on the blockchain, thus the recipient should have access to the funds. A [callback notification](/references/callbacks.md) will be sent to your designated endpoint.                                              |
| FAILED    | The withdrawal request has failed. We'll trigger a callback notification with a failure status and description.                                                                                                                                                 |
| BLOCKED   | The withdrawal processing is aborted due to compliance reasons. This usually happens when the recipient address is marked as illicit (e.g. Darknet, Scam, etc.).  A [callback notification](/references/callbacks.md) will be sent to your designated endpoint. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.finrax.com/references/crypto-withdrawals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.