Async notification
Where this sits
When the payout finishes, the system POSTs JSON to notifyUrl. Verify, update payout status, and acknowledge the callback.POST
Merchant notifyUrlNotification fields
| Field | Type | Required | Sign | Example | Description |
|---|---|---|---|---|---|
appId | string | Yes | Yes | — | APP ID |
orderNo | string | Yes | Yes | — | Platform payout no |
merchantOrderNo | string | Yes | Yes | — | Merchant order no |
network | string | Yes | Yes | — | Network, see Parameter lookup |
asset | string | Yes | Yes | USDC | Payout asset; see Parameter lookup |
cryptoAmount | string | Yes | Yes | — | Payout amount |
toAddress | string | Yes | Yes | — | Destination |
status | string | Yes | Yes | — | Status; see Parameter lookup |
createdAt | string | Yes | Yes | — | Created at |
completedAt | string | Yes | Yes | — | Completed at |
attach | string | No | No | — | Attach |
signature | string | Yes | No | — | Signature |
Acknowledgement
After receiving a notification, the merchant MUST acknowledge the callback. Otherwise the notification is retried.
Retry schedule
If the first notify fails, retries follow 10, 60, 600 seconds — up to 3 additional attempts.