API integration
USDT / USDC collection API: create and query orders
Use exclusive bindings for member deposits and pay-in orders for fixed amounts. Inspect signatures, requests and responses with the official tools.
Step-by-step guide
Follow these steps in your own dashboard. Select an image to enlarge it.
In the developer center, open API Debugger. For member deposits, choose Create Exclusive Wallet and follow its guide. The following steps describe fixed-amount pay-ins. LIVE · Production means creation writes real data; start by querying an existing order if you only need to inspect the setup.
Step 1 · Click to enlarge Enter your six-digit merchant UID and API Key beginning with mch_ in the official tool. They stay in that page's memory and must be entered again after a refresh. Do not share screenshots or headers containing the key with AI or support.
Select Create Pay-in Order and check the asset, merchant order number, amount and notifyUrl. Pass the amount as a string. The merchant order number links to your own order, and notifyUrl must use HTTPS. Use debug URL to inspect platform callbacks in Receive Callbacks; use your own deployed callback URL for business traffic.
Select Create Production Pay-in Order only when you intend to create a real order. The tool generates the timestamp, nonce and signature and displays Request and Response. Check the HTTP status, orderNo, merchantOrderNo, cashierUrl and status. A checkout URL confirms creation, not payment.
Switch to Query Order Status and enter the platform's orderNo: PI for pay-ins, PO for payouts. Do not enter your merchantOrderNo. Pay-ins succeed at completed; payouts succeed at confirmed or fail at failed. If a response is unclear, query the original order before creating another.
Compare headers, signing payload, body and raw response. For 20005, check the key; 20011, check path, ordering and canonical body; 20012, correct the clock; 20016, generate a fresh nonce; 40105, check unexpired pay-ins for the same amount; 51004, check fee balance. Record requestId and share redacted errors with a developer or AI. Use the Node.js or PHP example as a reference and read credentials from environment variables.
These tools use production. Creating orders or wallets saves real data, and creating a payout attempts to send funds. Verify business parameters and query the original order after a timeout or unknown result instead of submitting again.