Notification Status API
Merchants can call notification status API to check whether a notification has been sent to a customer or not.
We recommend passing the customer_id as the x-routing-id. If the customer is checking out as a guest, you can pass an alternative ID that helps track the payment session lifecycle. For example, this could be an Order ID or Cart ID.
This ID is associated with the customer. It plays a key role in ensuring consistency and maintaining connections across different systems. If you fail to pass the same x-routing-id for the same customer in all related API calls, it could lead to issues with API functionality. Therefore, it’s crucial that you use the same x-routing-id for all requests tied to the same customer.
Example:- customer_1122
Object reference Id
Status of Notification :
CREATED/PENDING/SUCCESS/FAILURE
CREATED- Created and not yet initiated to gateway
PENDING- Initiated to gateway
SUCCESS- Success from gateway
FAILURE- Failed from gateway
Source object for notification. i.e. “Mandate”
Json block of source info provided in the request
txn_date passed in the notification request.
Format: UNIX EPOCH timestamp (UTC timezone).
I.e. 1634057114
The invoice display number passed during notification API
Amount passed in the request
I.e. 100.00
Json block of response from gateway
Reference Number provided by downstream gateway
Date on which notification has been sent by downstream gateway.
Format: UNIX EPOCH timestamp (UTC timezone).
I.e. 1634057114
Specific to PAYTM_V2
Name of the provider. Gateway name in this case
I.e. PAYTM_V2
Unique Identifier passed in the request.
I.e. 1234578
notification
Type of notification.
I.e. “SMS”
Json block for Mandate ID provided in the request:
Mandate id provided in the Notification API
Date-time of notification updated in UNIX EPOCH timestamp (UTC timezone) format
Unique identifier provided by Juspay
Reason for debit passed in the request
Date-time of notification created in UNIX EPOCH timestamp (UTC timezone) format
Notification not found
INVALID_REQUST_ERROR
a054b2b1-1a79-4225-bebf-d2b9ba130a58
Notification not found
INVALID_REQUEST