LRS Transaction Status Callback/Webhook

post

https://stagingglobal.decentro.tech/clientcustomendpoint

This callback is used by Decentro to trigger the status updates against a transaction to pre-configured endpoint of the platform.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

📘
This service is currently in internal beta and subject to change. The request and response payloads, API endpoint, and validation logic may be updated.

Overview

This callback allows the platform to proactively receive a transaction's status, initiated using the Generate LRS Payment Link API, without having to check it from their end, thus reducing the computational burden and making it more efficient to propagate the status to the payer.

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

Key points to note:

This callback is triggered 3 times per transaction
This callback only propagates the transaction status
This callback is triggered each time a transaction status is updated.

Body Params

callback_attempt

string

required

Number of times the callback has been attempted.

callback_txn_id

string

required

Unique identifier assigned by Decentro to the callback attempt.

callback_timestamp

string

required

Timestamp of the callback in UTC. Please Note: this value is not the transaction authentication timestamp.

original_callback_txn_id

string

required

Unique identifier mapped to the first callback attempt.

request_decentro_txn_id

string

required

The unique ID assigned by Decentro when generating the payment link.

request_reference_id

string

required

The unique ID assigned by the platform when generating the payment link.

lrs_customer_id

string

required

The customer/payer ID against which the payment request was initiated.

consumer_urn

string

required

The consumer (merchant) who initiated the payment request.

transaction_status

string

required

The current status of the transaction.

transaction_status_description

string

required

Human readable description of the transaction status.

error_key

string

Machine readable keys documenting the various errors which can contribute to the payment failure. Will be propagated when the transaction reaches a FAILED state.

error_key_description

string

Human and Machine readable descriptions documenting the various errors which can contribute to the payment failure. Will be propagated when the transaction reaches a FAILED state.

payment_details

object

required

Please Note: Will be represented in the main currency unit. Example: Dollars instead of cents.

payer_details

object

required

lrs_details

object

required

Responses

This service is currently in internal beta and subject to change. The request and response payloads, API endpoint, and validation logic may be updated.

Overview

Key points to note:

200

400Bad Request