CNIXPay is a stablecoin payment gateway for merchants. Create an order with one API call, let customers pay on any supported network, and we confirm, settle and notify your server automatically.
One order can offer several networks and tokens at once
Available combinations are returned by the API
From address allocation to confirmation, from ledger entries to callbacks — every step is built to the standard that money must never be wrong.
Attach up to 10 network × token payment options to a single order. A payment on any of them counts toward the order, with your own checkout or ours.
Every order gets its own HD-derived address. Address pools are isolated per merchant and only reused within the same merchant after a cooldown, so attribution stays auditable.
On-chain webhooks deliver deposits in real time while scheduled chain scans act as a fallback. A flaky channel never means a missed order.
Quote orders in USD and let customers pay in USDT or USDC at 1:1 — the same address accepts both. Native-coin orders in TRX, BNB and more are supported too.
If a customer underpays or sends several transfers, payments keep adding up and each one sends order.partially_paid. The order completes once paid in full; if it is still short when the grace period ends, the amount received is credited and order.underpaid is sent.
Webhooks carry an HMAC-SHA256 signature and a timestamp. All four order events are retried for about 22 hours on failure, delivery logs are visible in the dashboard, and you can resend any event.
You create orders and handle callbacks. We take care of everything on-chain.
Call POST /orders from your server with an amount and optional network / token payment options. You get deposit addresses or a hosted checkout link.
On your own page or our hosted checkout, the customer sends USDT / USDC to one of the addresses — on whichever network they prefer.
Deposits are detected in real time and checked against the amount due. Paid in full means paid; short means we keep accumulating.
Funds are credited to your merchant balance with a ledger entry, and a signed event is sent to your callbackUrl.
Five REST endpoints cover every payment scenario: create, get, list, add payment options and close. One JSON envelope with clear error codes, every amount is a string, and an OpenAPI file is included.
Authorization: Bearer <API Key>, with optional IP allowlists.
Merchant order numbers are unique per app and a duplicate returns the existing order; re-adding options or re-closing simply returns the current state.
Per-endpoint limits are documented and return 429 with Retry-After, so backing off is straightforward.
curl -X POST https://api.cnixpay.com/api/v2/orders \
-H "Authorization: Bearer $CNIXPAY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"merchantOrderNo": "ORDER_10086",
"amount": "100.00",
"paymentOptions": [
{ "chain": "tron", "token": "USDT" },
{ "chain": "bsc", "token": "USDC" }
],
"callbackUrl": "https://shop.example.com/notify"
}'{
"code": 0,
"message": "success",
"data": {
"orderNo": "20261017105142a1b2c3d4e5f6",
"status": "pending",
"amount": "100.00",
"currency": "USD",
"paymentOptions": [
{ "chain": "tron", "token": "USDT", "address": "TR7NHq...", "amount": "100.00" },
{ "chain": "bsc", "token": "USDC", "address": "0x55d3...", "amount": "100.00" }
],
"cashierUrl": "https://pay.cnixpay.com/pay/20261017105142a1b2c3d4e5f6",
"expireTime": 1760670400
},
"requestId": "req_1c9e..."
}POST /notify HTTP/1.1
Content-Type: application/json
X-Webhook-Id: evt_7f3c9a...
X-Webhook-Timestamp: 1760670205
X-Webhook-Signature: v2=5b1f0e...
{
"id": "evt_7f3c9a...",
"event": "order.paid",
"createTime": 1760670200,
"data": { "orderNo": "20261017105142a1b2c3d4e5f6", "status": "paid", "version": 3, "...": "..." }
}import crypto from 'node:crypto'
// rawBody must be the raw request body (Buffer); do not re-serialize parsed JSON
export function verifyWebhook(rawBody, headers, apiSecret) {
const timestamp = headers['x-webhook-timestamp']
const signature = headers['x-webhook-signature'] ?? ''
if (!/^\d+$/.test(timestamp ?? '') || Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false
const expected =
'v2=' + crypto.createHmac('sha256', apiSecret).update(`${timestamp}.`).update(rawBody).digest('hex')
const a = Buffer.from(expected)
const b = Buffer.from(signature)
return a.length === b.length && crypto.timingSafeEqual(a, b)
}
// Express: app.post('/notify', express.raw({ type: 'application/json' }), handler)Pass paymentOptions when creating the order, receive every deposit address and amount due, and render network + token + address + QR code inside your own UI.
createOrder({ options: [...] }) → paymentOptions[]Create the order without paymentOptions and redirect the customer to the returned cashierUrl. Network selection, address, QR code, countdown and result pages are handled for you.
createOrder({ }) → cashierUrlThe dashboard is designed around status and next actions, so finance and engineering both find what they need.
Settlements land in real time. Withdraw to your saved addresses and track every status along the way.
Filter by order number, address, status or time, and inspect transaction hashes and callback logs per order.
Export daily reports, fund details and ledger entries to CSV, with Chinese or English headers.
Manage multiple apps, each with its own API key / secret, callback URL and IP allowlist.
Withdrawals require TOTP. Adding a withdrawal address requires an email code plus TOTP. After a password or email change, withdrawals pause for 24 hours.
API key authentication, IP allowlists and per-endpoint rate limits. Webhooks carry an HMAC-SHA256 signature and a timestamp to prevent forgery and replay.
Deposit addresses are allocated per merchant and never shared with others, so on-chain ownership is always clear.
Amounts are computed and compared as integer micro-units. Every balance change is recorded for reconciliation and audit.
USDT and USDC on TRON, BNB Smart Chain, Ethereum, Polygon and Solana (USDT only on TRON). Available combinations are configured by the platform and returned by the API.
No. Deposit addresses are derived and monitored by the platform. Once an order completes, funds are credited to your merchant balance and you can withdraw to your own on-chain address any time.
The order stays pending and keeps adding up, sending order.partially_paid for each transfer; once the total reaches the amount due it becomes paid and order.paid is sent. If it is still short when the grace period after expiry ends, the amount received is credited, the order becomes underpaid and order.underpaid is sent for you to handle.
Rely on status == "paid" in the webhook order, always verify the signature, dedupe by X-Webhook-Id and keep the highest version. You can also get the order before shipping to double-check.
Orders are quoted in USD and paid in USDT or USDC at 1:1. You can also quote in a native coin (TRX, BNB, ETH, POL, SOL), in which case only that coin is accepted. Fiat quotes such as CNY are not supported.
There is no simulated sandbox. We recommend integrating with small real orders on a live network.
Fees and the minimum withdrawal amount are shown in the merchant dashboard. The exact fee and net amount are displayed before you confirm each withdrawal.
Create a merchant account, then create an app in the dashboard and submit it to go live. The app page shows your API key and API secret. Send the key as Authorization: Bearer; the secret is only used to verify webhook signatures — never put it in requests or front-end code.
30 minutes by default; set expireMinutes (5–1440) when creating the order, and it is returned as expireTime. A grace period follows expiry during which deposits and top-ups still count; funds arriving after that are handled manually by the platform.
Once the total received meets the amount due, the order is paid. The actual amount received is returned as paidAmount, and any overpayment is credited to your merchant balance as well.
Yes. A pending order that has not received any payment can be closed, after which deposits are no longer credited automatically. Orders that received a payment, or have one still confirming on-chain, cannot be closed.
Yes. Pass callbackUrl when creating the order to override the app default; both must use https. Any HTTP 2xx from your endpoint counts as delivered.
Just four: pending — no outcome yet, wait; paid — paid in full, fulfil; underpaid — only part paid when the grace period ended, handle manually; closed — nothing received, the order is closed.
Yes. A merchant account can have multiple apps, each with its own API key / secret, callback URL and IP allowlist. Orders and statistics are kept separate per app.
The merchant payment API does not currently include a refund endpoint. If you need to refund, send the funds from your own wallet to the customer address.
Create a merchant account, set up an app, grab your API key — and run your first order today.