Get Mandate Order Status
This is the same API used to check order status of one time debit transactions. The status of the mandate and other mandate related details are included in the response of the same API.
|
Transaction Status
|
ID
|
Meaning
|
|---|---|---|
NEW
| 10
| Newly created order.
|
PENDING_VBV
| 23
| Authentication is in progress. The customer has to approve the mandate through the PSP App of their choice.
|
CHARGED
| 21
| Successful transaction. The subscription cost of the period has been charged.
|
AUTHENTICATION_FAILED
| 26
| User did not complete authentication.
|
AUTHORIZATION_FAILED
| 27
| User completed authentication, but the bank refused the transaction.
|
JUSPAY_DECLINED
| 22
| User input is not accepted by the underlying PG.
|
AUTHORIZING
| 28
| Transaction status is pending from bank.
|
|
Mandate Status
|
Description
|
|---|---|
CREATED
| Mandate has been created, but awaiting status from PG.
|
ACTIVE
| When PG accepts the chosen mode of payment, the mandate is set to the active state. This is a terminal state until mandate expires or customer/merchant wants to revoke the mandate.
|
FAILURE
| Mandate creation was unsuccessful. This is a terminal state, the merchant has to create a new mandate if failed.
|
Consists of two parts.
Username: API Key obtained from Juspay dashboard
Password: Empty string
Example:- Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
Merchant ID which would have been issues while registering with Juspay
Pass the date in YYYY-MM-DD format.
Note: If a version is provided, the response will include data corresponding to that specific version date.
It is recommended not to enforce strict validation on the entire response on the merchant's side to allow for future key additions.
Example:- Eg: Sample Value: 2025-01-10
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
Order Id for which you want check mandate order status
Example:- ord_234823498237423894273498
Transaction UUID
Transaction ID
Transaction UUID
Unique Identifier for the order.
ISO string of the currency.
Status ID is a numeric id corresponding to the status value.
Status of the order. If you receive “NEW”, then the order is successfully created.
A fully qualified URL such as http://shop.merchant.com/
to which the customer will be redirected after payment completion.
An identifier for the product on the Lender side for which the payment is being done. This field is just echoed back in the response so that Lender can differentiate on their side.
Payment method type used at the time of creating a mandate
Payment method used at the time of creating a mandate
Contains 3 strings that link to a Desktop optimized, Mobile optimized as well as iFrame checkout screen for the given order.
Payer VPA used during setting up mandate
Unique Identifier for the order.
Mandate start date. The value that is passed during order creation
Rule value
Rule Type
Mandate revocable by customer
Mandate max amount
Type of Mandate. Example: EMANDATE
Mandate token sent by Juspay after mandate creation
Status of the Mandate. Will be ACTIVE if the mandate is successfully setup
Mandate id sent by Juspay after mandate creation
Mandate frequency
Mandate end data.The value that is passed during order creation
Mandate block fund
Amount rule
Unique ID generated by Juspay for the given order.
Mobile number or fixed line number of the customer.
Customer Identifier against which a mandate should be created. This has to be unique for a customer
Email address of the customer.
ISO string of the currency.
Bank Error Message
Bank Error Code
Type of authentication used
The amount that was refunded
This is the amount that a customer will be charged in this transaction.
Transaction UUID
Transaction ID
Transaction UUID
Unique Identifier for the order.
ISO string of the currency.
Status ID is a numeric id corresponding to the status value.
Status of the order. If you receive “NEW”, then the order is successfully created.
A fully qualified URL such as http://shop.merchant.com/ to which the customer will be redirected after payment completion.
An identifier for the product on the Lender side for which the payment is being done. This field is just echoed back in the response so that Lender can differentiate on their side.
Payment method type used at the time of creating a mandate
Payment method used at the time of creating a mandate
Contains 3 strings that link to a Desktop optimized, Mobile optimized as well as iFrame checkout screen for the given order.
Payer VPA used during setting up mandate
Unique Identifier for the order.
Mandate start date. The value that is passed during order creation
Mandate revocable by customer
Mandate max amount
Type of Mandate. Example: EMANDATE
Mandate token sent by Juspay after mandate creation
Status of the Mandate. Will be ACTIVE if the mandate is successfully setup
Mandate id sent by Juspay after mandate creation
Mandate frequency
Mandate end data.The value that is passed during order creation
Mandate block fund
Amount rule
Unique ID generated by Juspay for the given order.
Mobile number or fixed line number of the customer.
Customer Identifier against which a mandate should be created. This has to be unique for a customer
Email address of the customer.
ISO string of the currency.
Type of authentication used
The amount that was refunded
This is the amount that a customer will be charged in this transaction.
Bank Error Message
Bank Error Code
Transaction UUID
Transaction ID
Transaction UUID
Unique Identifier for the order.
ISO string of the currency.
Status ID is a numeric id corresponding to the status value.
Status of the order. If you receive “NEW”, then the order is successfully created.
A fully qualified URL such as http://shop.merchant.com/ to which the customer will be redirected after payment completion.
An identifier for the product on the Lender side for which the payment is being done. This field is just echoed back in the response so that Lender can differentiate on their side.
Payment method type used at the time of creating a mandate
Payment method used at the time of creating a mandate
Contains 3 strings that link to a Desktop optimized, Mobile optimized as well as iFrame checkout screen for the given order.
Unique Identifier for the order.
Mandate revocable by customer
Mandate max amount
Type of Mandate. Example: EMANDATE
Mandate token sent by Juspay after mandate creation
Status of the Mandate. Will be ACTIVE if the mandate is successfully setup
Mandate id sent by Juspay after mandate creation
Mandate frequency
IFSC Code of the bank
Account holder name
Bank name
Bank account number
Mandate block fund
Amount rule
Unique ID generated by Juspay for the given order.
Mobile number or fixed line number of the customer.
Customer Identifier against which a mandate should be created. This has to be unique for a customer
Email address of the customer.
ISO string of the currency.
Bank Error Message
Bank Error Code
Type of authentication used
The amount that was refunded
This is the amount that a customer will be charged in this transaction.
Have questions?
- Need help? Contact support
- LLM? Read llms.txt