Notification API
This API is required if mandate notification is handled at merchants end. This sends a notification to the customer before the mandate transaction is exercised. A notification has to be sent to the user 24 hours before the execution of the mandate. This API is called using the mandate_id generated while creation of mandate. In case of Razorpay, Gocashfree, PhonePe the notification is taken care at PG end.
Length upto 25 and alphanumeric characters are only accepted.
Consists of two parts.
Username: API Key obtained from Juspay dashboard
Password: Empty string
Example:- Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
application/x-www-form-urlencoded
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
Mandate Id
Example:- b70vxxxxxjGyUhVrV8
“pre_debit_notify” for sending notification before execute mandate
Merchants unique Identifier for the request.
Json block to pass detailed information to gateway
Amount for which notification is to be sent to customer I.e. 100.00
Date on which debit is intended to happen in UNIX EPOCH timestamp (UTC timezone) format
If merchant wants to generate invoice display number, this needs to be passed in notification call. If not passed, Juspay will create a unique invoice number and pass it to downstream system. It should be alphanumeric and length upto 25 characters. (Applicable only for cards SI)
Reason for debit that will be sent to user - Max Length: 50
To be passed as Stringified JSON
Any key value pair can be passed and will be returned in response
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 request.
Format: UNIX EPOCH timestamp (UTC timezone).
I.e. 1634057114
Amount passed in the request.
I.e. 100.00
The display invoice number that is passed in the request.
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 request
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

