Notifications
Learn about how the notifications for deposits works
Last updated
Learn about how the notifications for deposits works
Last updated
Every time a deposit changes its status, we will send you an asynchronous notification to your confirmation_url as described here.
Once received the notification, you should check its status back with the Deposit Status Endpoint and update it on your end accordingly.
Bear in mind we will only connect through ports 80 and 443. Make sure your notification_url has one of those ports open and accepting connections from us.
Every time a deposit changes its status, we will send you a notification so you can check its status back.
In case that for some reason your server was unable to receive the notification and you returned an HTTP code other than 200, we will retry the notification up to 5 more times or until you respond with HTTP 200, whatever comes first.
The time between each of the 5 notifications attempts will be exponential: 5, 25, 125 and 625 minutes accordingly.
When the notifications fails to be sent, it will be shown like this in our Merchant Panel:
If you see the errors from the screenshot above, it means the payment was successfully completed and the money was credited to your account but suddenly we couldn't notify you. Keep reading to know how to resend the notifications.
In case your system was unable to receive the notification in any of the 5 attempts, you can always check its status with the Deposit Status Endpoint.
If you need to trigger the check status by receiving our notification, once the issue preventing you from receiving our notifications was fixed, you can go to the Merchant Panel, locate the deposit and click on the three dots button under the "Status History" section and then "Resend notification" to force a new notification to be sent.
It can take up to 1 minute for the notification to be resent in PROD and 3 on STG.
