Prepaid funds, credit, and low-water thresholds—three numbers determine when your services stop.
Merchant Accounts and Prepaid Funds
All Costs Are Debited from Prepaid Funds
We do not advance any funds for merchants. Before each transaction completes, the portion payable to us is frozen in the prepaid account and settled on completion.
预付余额 ──冻结──► 冻结中 ──结算──► 我方收入
▲ │
└────── 释放 ────────┘ （订单取消/失败）
Prepaid balances are per asset: USDT costs debit USDT prepaid funds, without cross-asset conversion.
Credit
Credit is the exposure we extend to you, and it counts toward available funds:
有效可用 = 预付余额 + 授信额度
Reducing credit can therefore immediately move you toward a service halt—which is why it requires dual approval on our side.
Three Low-Water Levels
Thresholds use “days of funds remaining at average daily consumption,” not absolute amounts (one fixed amount cannot suit merchants of every size):
| Level | What happens |
|---|---|
| Warning | Email is sent to your configured recipients |
| Alert | Another, more urgent email is sent |
| Halt | Affected services stop accepting new orders |
⚠ During a halt, members see “Temporarily unavailable,” not “Your platform has run out of funds.”
Financial arrangements between us and you are not disclosed to end users.
Eight Services, Each with Its Own Switch
GET /v1/merchant/lines
| Service | Meaning |
|---|---|
deposit | Deposit reporting |
withdraw | Withdrawal debits |
remit | Remittance |
qrpay | QR payments |
card | Card issuance |
earn | Wealth |
exchange | Internal exchange |
transfer | Internal transfers |
Each service has three flags:
| Field | Meaning | Who can change it |
|---|---|---|
enabled | Whether this service is enabled | Contact your account manager |
halted | Whether acceptance is halted | Manual halts require manual release; automatic low-water halts clear after you add funds |
self_pricing | Whether you may set your own retail price | Configured by us |
⚠ Missing row = unavailable (deliberately opposite to the product authorization tables).
An unconfigured service means “not enabled,” not “unrestricted.”
Insufficient Funds Fail Differently Across the Eight Services
| Service | Insufficient funds behavior |
|---|---|
remit · card | Queued (pending_merchant_funds), resumes automatically after you add funds |
qrpay · exchange · earn · withdraw | Fails immediately (service_unavailable), no queue |
deposit · transfer | Does not consume prepaid funds; unaffected |
⚠ No member funds have moved in the queued state. It occurs before freezing funds—
otherwise funds would be trapped in a bucket neither the member nor operations can advance.
Queue Depth
GET /v1/merchant/pending
Shows each service's queued order count, amount, and age of the oldest order.
⚠⚠ This is the only place in the entire flow that clearly tells you to add funds.
Members experience failed transactions despite sufficient personal balances, and the wording deliberately conceals the cause.
Merchants who ignore this endpoint will only see an unexplained fall in completion rates.
Add Funds
Two paths:
- On-chain deposit—use
POST /v1/merchant/deposit-addressesto obtain an address assigned to you, then transfer funds to it. Funds are credited automatically on receipt (we assign the address, and the amount comes from on-chain confirmation; no manual amount entry is involved). - Offline settlement—bank transfer, credited after we manually verify the receipt and obtain dual approval.