# Crypto to Fiat (Off-Ramp)

This section provides information about the crypto to fiat off-ramp process, allowing users to convert cryptocurrency into fiat currency through the API. 

## **Create Order**

* **Request Header**: `Content-Type: application/json`
* **Request Header**: `X-BH-TOKEN: ******`
* **Request Method**: `POST`
* **Request Path:** `/v2/order/crypto_to_fiat`
* **Authorization Required**: Yes

**Request Parameters**

The request body should include the following parameters:

| Parameter                                                            | Type    | Required | Description                                                                      |
| -------------------------------------------------------------------- | ------- | -------- | -------------------------------------------------------------------------------- |
| country                                                              | string  | Yes      | Name of the country (e.g., "Mexico")                                             |
| clientId                                                             | string  | No       | An order ID that you may define and will be returned to you in a Get Order call. |
| merchantId                                                           | number  | No       | ID of the merchant                                                               |
| crypto                                                               | string  | Yes      | Name of the cryptocurrency (e.g., "USDT")                                        |
| fiat                                                                 | string  | Yes      | Name of the fiat currency (e.g., "MXN")                                          |
| cryptoAmount                                                         | decimal | Yes      | Amount of fiat currency to convert (e.g., 1000.00)                               |
| [userPaymentId](/api-reference/payment-method/get-payment-method.md) | number  | Yes      | ID of the user payment method                                                    |
| remark                                                               | string  | No       | Additional remarks for the order                                                 |

**Request Example**

```json
{
    "country": "Mexico",
    "clientId": "xxxx",
    "merchantId": 3,
    "crypto": "USDT",
    "fiat": "MXN",
    "cryptoAmount": 1000.00,
    "paymentId": 91,
    "remark": ""
}
```

**Response Parameters**

The response will contain the following parameters:

| Parameter    | Type   | Description                        |
| ------------ | ------ | ---------------------------------- |
| code         | number | Response status code (e.g., 200)   |
| msg          | string | Response message (e.g., "SUCCESS") |
| data         | object | Contains order details             |
| data.orderId | number | ID of the created order            |

**Response Example**

```json
{
    "code": 200,
    "msg": "SUCCESS",
    "data": {
        "orderId": 1123123123
    }
}
```

### Notes

* Ensure that valid parameters are provided for successful order creation.
* The `merchantId` and `paymentId` must correspond to existing merchant and payment method configurations.
* The response will confirm the successful creation of the order, along with the order ID for tracking.


---

# Agent Instructions: 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:

```
GET https://docs.velafi.com/guides/crypto-to-fiat-off-ramp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.