JavaScript is disabled. Some features may not work. You can also read the static version: View text version

Order + Txns being called together for Mandate Registration

In this flow, merchant will have to call only one API, we’ll internally call the Order API and create order. Merchant can expect response, similar to Txns reponse itself.

This is just a snippet of how the flow can work, for all possible cases and parameters

1. Regarding Order, please check here
2. Regarding Transaction , please check here.

Request

Response

API Endpoints

Sandbox Link

POST

https://sandbox.juspay.in/txns

Production Link

POST

https://api.juspay.in/txns

                      Basic Auth
                      *
                      

required

                      x-routing-id
                      *
                      

String

Required

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

Have questions?
Need help? Contact support
LLM? Read llms.txt