Callback Implementation

• Polling cycle: The system polls for 1 minute to check whether there are incoming and outgoing transaction messages. If the code value received by the system after pushing is not 0, it will always try to push (message is ignored, message processing complete code returns 0).

• Push principle: Push messages in the dimension of business lines, with the granularity of in and out of accounts, and push messages in and out of accounts separately, and push a batch of messages at a time. In order to ensure the orderliness of the message, if the system does not receive the code value of 0 synchronously after the message is pushed, the push will be suspended and the next polling cycle will try again.

• Security assurance: The system only pushes brief information, and you need to query the API document through detail_id query API Doc 5.2 for the wallet transaction record details to confirm the deposit and withdrawal.If the order has multiple transactions, the ids are separated by commas. It is recommended to filter the transaction details directly according to the order number. And confirm the currency according to "coin_name"

• Deposit confirmation: deposit transaction will push the confirmation message from 0 block to the safe block height (BTC safe height 6, ETH safe height 30), the status of the transaction that has not reached the safety confirmation is unconfirmed, and the transaction is confirmed status when the deposit is confirmed on chain.

• Withdrawal confirmation: Withdrawal pushes the message according to the order status, the payment block height is 1 block if the order FINISHED, and the withdrawal can be checked for transaction details according to the FINISHED order status to confirm the order.