Overview

This callback 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 any of the flows below.

The platform can share the endpoint for configuring the endpoint for this callback before going live at [email protected].

Points to Note

Key points to note.

This callback isn't triggered in case of a static QR code-based transaction or a push transaction.
This callback is triggered 3 times per transaction
This callback only propagates the transaction status
This callback is triggered when a transaction status moves to one of SUCCESS, FAILURE, EXPIRED.
If the client responds with a 200 HTTP code, we will consider the callback acknowledged. We will disregard any content in the body and solely depend on the HTTP status code.

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 Generate payment link API, Generate Dynamic QR, or Issue Collect Request or the reference_id passed by the platform in these APIs.
In this callback, Decentro relays the transaction status via the transaction_status field and the transaction details. The default status will always be 'PENDING' unless the payer authorizes a payment.
The platform can map the transaction type at its end using the collection_type parameter triggered as part of the callback payload.
The platform acknowledges the callback by responding to it with 'CB_S00000' from its end. If any other value is passed, Decentro shall retrigger the callback.
If the platform cannot acknowledge the callback or handle the same at its end, the transaction status can also be fetched using Get Transaction Status.
If the platform wants to know the updated balance of the ledger account, the same can be received using the Account Balance Callback/Webhook.
The platform can handle the reason for failure of a transaction using the 'error_key' field in the callback.

Simulation Data

Overview

Decentro's simulation data helps developers simulate all the real-world scenarios when using the Payment Link API.

This requires the platform to use standard request payloads to handle scenarios for each API and scenario, as mentioned below.

The platform will need to whitelist their IP and configure callback endpoints with Decentro if they wish to handle the flow. Please reach out to us at [email protected] for the same.

Flow

Decentro triggers the transaction status callback to the endpoints configured by Decentro as per platform's requests. The callback for the testbed will mirror the fields in the documentation but will have the data as passed by the platform in any of the below APIs.