Withdrawal Events
When the system performs a withdrawal that belongs to one of the customers' users, it will inform the customer through the customer's withdrawal callback URL.
Every callback request will originate from the following IP addresses: 18.132.254.104,18.170.187.186.
Our system signs the withdrawal event object with the customer's HMAC secret and sends the signature with the x-payload-hash header. So the customers can check the integrity of these requests by comparing the x-payload-hash with the one they calculated upon receiving the withdrawal information. The customer can also assume that the callbacks originate from our system if they arrive at their end from these IP addresses.
Once the system performs a withdrawal that belongs to one of the customers' users, the payment gateway calls their registered callback with the following event object.
Withdrawal Event Object Structure
objectType
STRING Customers can use this field to create their object hierarchy. All objects sent by the system will have this field. For Withdrawal Event Object, this field can consist of a single value: withdrawEventObject.
amount
NUMBER This field represents the amount of the withdrawal.
userId
STRING This field represents the user ID associated with the customer's withdrawal request.
operationNo
STRING This is the operation id of the withdrawal. The customer is responsible for sending a unique operation id in UUID format for each withdrawal request. When the system performs this request, the callback object consists of this UUID.
withdrawTime
NUMBER This field represents the epoch time of the withdrawal.
currency
STRING This field represents the blockchain currency of the withdrawal.
withdrawalState
Last updated
Was this helpful?