API Reference
Get StartedExport API CollectionSupport

Netbanking Terminal Transaction Status Callback/Webhook

post
https://your.custom.endpoint.com/CALLBACK_NETBANKING_TRANSACTION_STATUS/clientcustomendpoint

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

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 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 this callback before going live at [email protected].

Points to Note

Key points to note.

  • 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.

Flow

Below is the flow for using the callback capability as part of Decentro

  1. The platform consumes this callback to get the latest status of an initiated transaction from Generate Netbanking intent link API, Generate Netbanking QR or Generate Netbanking Redirection Link API
  2. 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.
  3. The platform can map the transaction type at its end using the initiation_type parameter triggered as part of the callback payload.
  4. 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.
  5. 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 in case of a UPI transaction.

Simulation Data

Overview

Decentro's simulation data helps developers simulate all the real-world scenarios 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 must whitelist its IP and configure callback endpoints with Decentro if it wishes 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 the 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.

Body Params
int32
required

Number of times the callback has been attempted.

float
required

The transaction amount. In case of UPI collection, the amount requested against a payment request.

string
required

Timestamp of the callback. Not the timestamp of the transaction.

string
required

Unique identifier mapped to the callback attempt.

string

The method of netbanking transaction. Describes whether the funds were received via an intent link, QR, or redirection. Possible values: INTENT, QR, REDIRECTION.

string
required

Unique urn assigned to client that they pass in request payload

string
required

The unique transaction identifier, passed against the payment request, by Decentro at the time of transaction initiation.

string

Unique identifier mapped to the first callback attempt.

string

Name of the payer if propagated by the partner bank

string

Account number of the payer/remitter. Passed only for virtual account based collections if provided by the bank partner.

float

The amount collected against a Transaction Attempt.

string

The purpose message value, shared during transaction initiation.

string

The unique transaction identifier, created by Decentro, for the payment.

string

The description of the status associated with the transaction attempt.

string

Status of the transaction attempt. Values passed: SUCCESS, FAILED, DEEMED, HOLD, REFUND_FAILED, REFUNDED

string

The timestamp at which user entered the MPIN and authenticated the payment.

string
required

The status of the transaction. Values passed: PENDING, SUCCESS, FAILED, EXPIRED, DEEMED, REFUND_FAILED, REFUNDED, DISPUTED_AMOUNT

string

The unique transaction reference number from the bank partner. Will not be propagated in "EXPIRED" and certain "FAILED" scenarios.

Headers
string
required

The header token shared by you should not contain any unsanitized values like @ # $ % ^ & * ! ; : ' " ~ ` ? = + ) (

string
required

The header token shared by you should not contain any unsanitized values like @ # $ % ^ & * ! ; : ' " ~ ` ? = + ) (

Responses

Updated about 2 hours ago

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated about 2 hours ago