Callback Enumeration Types Explanation
Callback Event Enumeration Values and Their Business Meanings
Enumeration Type | Enum Value | Description |
|---|---|---|
| NOTIFY_UNKNOWN | 0 | Merchants do not need to handle this notification type and should not respond. |
| NOTIFY_DEPOSITED | 1 | WaaS notifies merchant of a successful deposit order. Merchant needs to parse parameters and respond. Merchant is responsible for secondary verification on blockchain and returning response results to WaaS. |
| NOTIFY_REQUEST_WITHDRAW | 2 | Merchant needs to parse withdrawal order and respond with detailed information to WaaS. Used only for merchant’s withdrawal secondary confirmation interface. Although this interface shares the same request/response parameter template as the Webhook callback, it uses a separate URL. |
| NOTIFY_WITHDRAW | 3 | WaaS notifies merchant of successful withdrawal order. Merchant needs to parse parameters and respond. Merchant is responsible for secondary verification on blockchain and returning response results to WaaS. |
| NOTIFY_ADDRESS | 4 | Notification of user address change. Merchant needs to parse the new address in parameters and update user address information in system. |
| NOTIFY_INVALID_ADDRESS | 5 | Withdrawal failed (invalid address). In this case, the withdrawal order is terminated as failed. Merchant can safely unfreeze funds and return to customer. Other situations requiring termination of withdrawal order and fund return also use this callback enum, not necessarily address error. |
| NOTIFY_NOT_ENOUGH_MONEY | 6 | Withdrawal temporarily failed (insufficient balance). Merchant needs to parse withdrawal order parameters and respond. Withdrawal can still succeed after balance is replenished. |
| NOTIFY_NOT_ENOUGH_HOT_MONEY | 7 | Withdrawal temporarily failed (insufficient gas). Merchant needs to parse withdrawal order parameters and respond. Withdrawal can still succeed after hot wallet balance is replenished. |