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

# Fiat to Crypto (On-Ramp)

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

## **Create Order**

* **Request Header**: `Content-Type: application/json`
* **Request Header**: `X-BH-TOKEN: ******`
* **Request Method**: `POST`
* **Request Path:** `/v2/order/fiat_to_crypto`
* **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")                                          |
| fiatAmount                                | decimal | Yes      | Amount of fiat currency to convert (e.g., 1000.00)                               |
| [paymentId](/guides/payment-method-id.md) | number  | Yes      | ID of the payment method                                                         |
| remark                                    | string  | No       | Additional remarks for the order                                                 |

**Request Example**

```json
{
    "country": "Mexico",
    "clientId": "xxxx",
    "merchantId": 3,
    "crypto": "USDT",
    "fiat": "MXN",
    "fiatAmount": 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
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.velafi.com/guides/fiat-to-crypto-on-ramp.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.