Asynchronous events with real-time notifications

Identification events list

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.

User identification events list

Every time a user try to verify his identity, a webhook is activated with these possible events:

identification_pendingTriggered when a user finish finish the identity process and is is pending of approval.
identification_verifiedTriggered when the user's identity has been approved.
identification_rejectedTriggered 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_retryWhen a file is altered or the selfies are not clear, the user is invited to submit the process again.

Fiat Payments

We inform the client after every transactions is registered in our platform. Here we can have these events:

fiat_payment_receivedTriggered when a fiat payment for a bank_account is received in our platform
fiat_payment_sentTriggered when a fiat payment for a bank_account is sent from our platform
fiat_payment_failedTriggered when the fiat payment failed and it needs a retry.

Blockchain payments

We inform the client after every transactions is registered in our platform. The next events can be occur:

blockchain_payment_receivedTriggered when a payment or token has been received in any of your wallets
blockchain_payment_enqueuedTriggered when an outgoing payment has been accepted by Depasify, and it's enqueued for its further execution. This event doesn't yet contain a trx. id
blockchain_payment_sentTriggered when an outgoing payment has been processed succesfully, and it contains its trx. id
blockchain_payment_failedTriggered if the outgoing payment cannot be processed properly. These cases will need to review your Idempotent implementation and decided if re-try or create a new instance of the payment.

All the JSON payloads contents of each possible event is detailed in the Webhook events and payloads section.

Retry policy

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.

Ensuring Idempotency with the Idempotency-Key Header

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.