post https://your.custom.endpoint.com/transactionStatus
API Endpoints
| Environment | Endpoint |
|---|---|
| Staging / Sandbox | https://your.staging.custom.endpoint.com |
| Production | https://your.custom.endpoint.com |
Overview
This callback allows the platform to proactively receive a transaction's status without having to check it from their end, thus reducing the computational burden and making it more efficient to propagate the status to the platform.
Flow
- The platform will perform a transaction with Initiate Payout:.
- Once Decentro fetches the final status from the provider, Decentro will trigger the callback to the platform's endpoint.
- The platform must acknowledge the callback. If the callback is not acknowledged as per the given examples, Decentro will retrigger the callback.
- Decentro will retrigger a total of 3 times to the platform if the callback is not acknowledged.
- If the platform has not acknowledged any of the callbacks triggered, then the platform can use Get Transaction Status: to fetch the status of the transaction.
Key Points
Below are the key points for the Transaction Status Callback workflow.
- Platforms must ensure that to handle the retrigger of the callbacks from Decentro to avoid registering double debits/credits in their system.
- It is recommended that platforms whitelist Decentro's IP address for both staging and production.
- Decentro will trigger the callback only when the transaction status moves from pending to success/failure