We inform the client of asynchronous event using webhooks. Whenever a new event occurs a HTTP call to your registered webhook URL will be perform. This payload will content all the information that you need to register this event. In this way the client receives in real time the information related of every event.
Every time a user try to verify his identity, a webhook is activated with these possible events:
|identification_pending||Triggered when a user finish finish the identity process and is is pending of approval.|
|identification_verified||Triggered when the user's identity has been approved.|
|identification_rejected||Triggered when the user's identity has been rejected. The user is not permitted to use the platform and you should contact Depasify for a manual review.|
|identification_retry||When a file is altered or the selfies are not clear, the user is invited to submit the process again.|
We inform the client after every transactions is registered in our platform. Here we can have these events:
|fiat_payment_received||Triggered when a fiat payment for a |
|fiat_payment_sent||Triggered when a fiat payment for a |
|fiat_payment_failed||Triggered when the fiat payment failed and it needs a retry.|
We inform the client after every transactions is registered in our platform. The next events can be occur:
|blockchain_payment_received||Triggered when funds are received in an account inside our platform.|
|blockchain_payment_sent||Triggered when funds are sent from an account inside our platform|
|blockchain_payment_failed||Triggered if any of the above transactions have failed for any reason|
All the JSON payloads contents of each possible event is detailed in the Webhook events and payloads section.
Our webhooks work with a retry policy so we make sure the information is received. Whenever a webhook is sent, we keep track of the status of the response we get to our HTTP call. If it is an error response, the webhook will automatically retry. It will retry up to 3 times until the response is successful. If it keeps failing, we store the information so we ensure that no information gets lost.
To ensure idempotency in our API, we utilize the
Idempotency-Key header. This header allows clients to assign a unique identifier to each request, ensuring that the same operation is not performed multiple times.