Basic Fiat Operations
Every request listed on this page requires authorization to be successfully completed.
Withdrawal fee
GET
https://public.api.0xpay.app/merchants/withdrawals/fiat/fee
This method is used to get a fee for sending a desired amount of assets (ticker
) on a chosen blockchain. Learn how fees work here
Request Body
Name | Type | Description |
---|---|---|
ticker* | string | KZT only |
amount* | string | amount in decimal format |
Supported fiat assets
GET
https://public.api.0xpay.app/merchants/assets/fiat
This method is used to fetch all available fiat assets of your merchant.
Send fiat (single tx)
POST
https://public.api.0xpay.app/merchants/withdrawals/fiat
Creates an outgoing fiat transaction (for example, UAH or KZT payment to a banking card)
Amount limits: For KZT: 20000 KZT.
After creation, 0xpay API will produce notifications according to status updates on your withdrawal.
Request Body
Name | Type | Description |
---|---|---|
ticker* | string |
|
to* | string | Destination card address |
amount* | string | amount in decimal format |
fee | string | you can specify withdrawal fees that have to be greater than the actual fee, which can be useful for better fee calculation options on your side. If not the specified – fee will be set automatically |
localId | string | if was specified error will be thrown if not unique, can be useful on your side to avoid the double-spend issue |
meta | string | your metadata that will be passed along to you later with a notification |
Send fiat assets as batch (no amount limits)
POST
https://public.api.0xpay.app/merchants/withdrawals/fiat/batch
Splits large fiat transactions into several smaller payments and sends them to destination. You can also send KZT transactions as a batch withdrawal, with amount limits ranging from KZT 20000-299000.
After creation, 0xpay API will produce notifications according to status updates on your withdrawal.
Example: You want to send KZT 100,000 to a banking card. Normally, that'd require creating 7 different requests of ~KZT 14,500. With batched payments, your transaction amount will be automatically split into smaller portions (13800 + 13611 + 14120 + 13900 + 13831 + 13822 + 8447 + 8469 = 100 000), then sent as a batch of payments.
Request Body
Name | Type | Description |
---|---|---|
ticker* | string |
|
to* | string | Receiving card number |
amount* | string | amount in decimal format |
fee | string | you can specify withdrawal fees that have to be greater than the actual fee, which can be useful for better fee calculation options on your side. If not the specified – fee will be set automatically |
localId | string | if was specified error will be thrown if not unique, can be useful on your side to avoid the double-spend issue |
meta | string | your metadata that will be passed along to you later with a notification |
Check details of fiat batch withdrawal and tx's status
GET
https://public.api.0xpay.app/merchants/withdrawals/fiat/batch/:id
Send this request to receive info about all payments in a selected fiat batch withdrawals.
Path Parameters
Name | Type | Description |
---|---|---|
* | String |
In response, you'll receive this information regarding each transaction from a selected batch withdrawal.
Example of such request:
Check details of fiat withdrawal and tx's status
GET
https://public.api.0xpay.app/merchants/withdrawals/fiat/:id
Send this request to receive info about withdrawal. Statuses (strings): 1. "CREATED" – withdraw was just created 2. "QUEUED" – withdraw is in the queue and will be processed soon 3. "DONE" – final status, withdrawal happened 4. "FAILED" – final status, withdrawal not happened: something goes wrong, refunded to merchant's balance
Path Parameters
Name | Type | Description |
---|---|---|
* | String |
In response, you'll receive this information regarding each transaction from a selected batch withdrawal.
Example of such request:
Last updated