This callback is used by Decentro to trigger the status of a transaction to pre-configured endpoint of the platform.
Important Note
Please use only Staging Credentials on each API Reference page to test the APIs directly from our Documentation.
Overview
This API allows the platform to proactively receive the status of a transaction without having to check the status from their end, thus reducing the computational burden and making it more efficient to propagate the status to the payer.
This callback allows a platform to receive the status of a transaction undertaken through the Penny Pull - Intent API
The platform can share the endpoint for triggering this callback before going live at [email protected].
Points to Note
Key points to note.
- This callback only propagates the terminal transaction status.
- This callback is triggered when a transaction status moves to SUCCESS only and not in case of PENDING, FAILURE or EXPIRED.
API Endpoints
Below are the API endpoints to be used by the platform basis the environments.
| Environment | Endpoint |
|---|---|
| Staging / Sandbox | https://your.custom.endpoint.com |
| Production | https://your.custom.endpoint.com |
Flow
Below is the flow for using the callback capability as part of Decentro
- The platform consumes this callback to get the latest status of an initiated transaction using the Decentro transaction ID received from Penny Pull - Intent API or the reference_id passed by the platform in this API.
- Decentro relays the transaction status via the status field in this callback, which includes value SUCCESS.
- The platform can map the transaction type at its end using the verificationType parameter triggered as part of the callback payload.
- The platform acknowledges the callback by responding to it with 'CB_S00000' from its end.
- If the platform cannot acknowledge the callback or handle the same at its end, the transaction status can also be fetched using Penny Pull - Get Transaction Status API.