​
Callback Event Enumeration Values and Their Business Meanings

Enumeration TypeEnum ValueDescription
NOTIFY_UNKNOWN0Merchants do not need to handle this notification type and should not respond.
NOTIFY_DEPOSITED1WaaS 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_WITHDRAW2Merchant 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_WITHDRAW3WaaS notifies the merchant of completed business operations through the NOTIFY_WITHDRAW (type=3) callback. The merchant needs to parse the symbol field in the callback parameters to distinguish the business type: when the symbol is a digital currency symbol (such as USDT), it indicates a withdrawal operation completion; when symbol=“ENERGY”, it indicates an energy lease operation completion. The merchant must perform secondary verification of the corresponding operation on the blockchain and return a response to WaaS based on the verification results.
NOTIFY_ADDRESS4Notification of user address change. Merchant needs to parse the new address in parameters and update user address information in system.
NOTIFY_INVALID_ADDRESS5Withdrawal 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_MONEY6Withdrawal 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_MONEY7Withdrawal temporarily failed (insufficient gas). Merchant needs to parse withdrawal order parameters and respond. Withdrawal can still succeed after hot wallet balance is replenished.