Create crypto deposit
The customer pays in USDT or USDC on-chain, and the funds are credited to your USDT balance. Each order gets its own deposit address. The response contains a hosted checkout URL (the page offers crypto payment only) as well as the deposit address and amount due, so you can also build your own payment page. When the funds arrive, the platform sends you a callback.
/api/open/order/createCryptoDepositFull URL = your API base URL + this path. The base URL is shown in the merchant console under Developers → API & callbacks.
Requires: IP whitelist, OpenAPI enabled, crypto deposits enabled for your merchant account (ask the platform), and a pay-in callback URL (or callbackUrl on this order).
You can also keep using Create pay-in order with paymentType = 101 / 102 / 103; the result is the same as this endpoint.
Supported networks and coins
| network | Coin | paymentType (for the pay-in endpoint) |
|---|---|---|
TRC20 (TRON) | USDT | 101 |
BEP20 (BNB Smart Chain) | USDT | 102 |
BEP20 (BNB Smart Chain) | USDC | 103 |
USDC is credited as USDT at 1:1. Each payment must be worth at least 100 USDT (the current value is minAmount in List payout methods).
Request parameters
JSON before encryption:
| Parameter | Type | Required | Description |
|---|---|---|---|
merchantNo | string | Yes | Merchant number, same as the outer request |
merchantOrderNo | string | Strongly recommended | Your order number, up to 50 characters, unique per merchant (checked together with pay-in orders, 40007). Generated randomly if omitted |
amount | number | Yes | Amount, greater than 0, at most 6 decimals |
currencyType | string | Yes | USDT / USDC: amount is the number of coins to receive. A fiat code (e.g. CNY): converted to coins at the rate at order time, and the rate is locked on the order |
payCoin | string | No | Coin to receive: USDT / USDC. If omitted: the coin in currencyType, or USDT when currencyType is a fiat code |
network | string | Yes | TRC20 or BEP20 |
redirectUrl | string | No | Where the checkout's "Back to merchant" button goes after payment |
callbackUrl | string | No | Callback URL for this order; defaults to the pay-in callback URL in the merchant console |
{
"merchantNo": "your merchant number",
"merchantOrderNo": "C20261021001",
"amount": 200,
"currencyType": "USDT",
"network": "TRC20",
"redirectUrl": "https://shop.example.com/pay/done"
}Response
| Field | Type | Description |
|---|---|---|
url | string | Hosted checkout URL (crypto only); send the customer there |
orderNo | string | Platform order number (starts with CD) |
merchantOrderNo | string | Your order number |
payAddress | string | Deposit address for this order only |
payNetwork | string | TRC20 / BEP20 |
payCoin | string | USDT / USDC |
payAmount | number | Amount of coins the customer should pay. For fiat orders it is the converted amount rounded up to 2 decimals |
expireAt | string | Payment deadline, UTC+8, yyyy-MM-dd HH:mm:ss |
{
"code": 0,
"message": "success",
"data": {
"url": "https://checkout-domain/crypto/?orderId=…&checkoutToken=…",
"orderNo": "CD20261021120000123456",
"merchantOrderNo": "C20261021001",
"payAddress": "T… (this order's address)",
"payNetwork": "TRC20",
"payCoin": "USDT",
"payAmount": 200,
"expireAt": "2026-10-21 13:00:00"
}
}The checkout URL contains this order's access token. Give it only to this customer and don't publish it.
If you build your own payment page
Tell the customer:
- send only the stated coin on the stated network; funds sent on another network or in another coin cannot be recovered automatically;
- send
payAmount; network fees are paid separately by their wallet, and the amount received must not be less than the amount due; - the address is for this order only; don't save it for future payments.
How payments are credited
| Case | Result |
|---|---|
| Received ≥ amount due | Credited at the amount actually received; overpayments are credited too (overpaid = true in Get order) |
| Received < amount due, but this payment is worth ≥ the minimum | Credited at the amount actually received (underpaid = true) |
| This payment is worth < the minimum | Not credited automatically; handled manually by the platform |
| Paid in several transfers | Each transfer is checked, credited and called back separately |
| Arrives within 24 hours after the deadline | Still credited automatically, with a callback |
| Arrives more than 24 hours late, or held by risk review | The order shows "pending release"; handled manually by the platform |
Crediting waits for block confirmations: 19 blocks on TRC20 (about 1 minute), 15 blocks on BEP20 (about 15 seconds); orders of 10,000 USDT or more need twice as many.
Common errors
| code | Reason |
|---|---|
| 40016 | Crypto deposits are not enabled for you; network is not TRC20 / BEP20; payCoin is not USDT / USDC; or the coin is not supported on that network (e.g. TRC20 + USDC) |
| 40019 | amount is not greater than 0, has more than 6 decimals, or is worth less than the minimum |
| 40010 | currencyType is a fiat currency that is unavailable or has no rate |
| 40017 | That fiat currency is not enabled for you |
| 40007 | Duplicate merchant order number |
| 40000 | Merchant order number longer than 50 characters |
Other common errors (signature, IP whitelist, …) are listed in Error codes.
Order states
| orderState | Meaning |
|---|---|
| 1 | Awaiting payment |
| 2 | Pending release (a transfer was seen on-chain and is waiting for confirmations, or is under manual review) |
| 6 | Released (credited to your balance; you will get a callback) |
| 3 | Success (you replied success to the callback of every transfer on this order) |
| 4 | Cancelled |
| 5 | Expired (nothing arrived before the deadline) |
Use Get order to check the current state and on-chain details at any time.