Mandate Update API
AIM: Adding a new feature for allowing merchants to update valid fields which are supported for that gateway and payment method type combination.
Add new command ‘update’ in the existing /mandate/:mandateId api, which will take a new parameter ‘updated_fields’
Example:- Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
Example:- application/json
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
Example:- update
Example:- 100
Example:- 1717670006
Example:- ASPRESENTED
Example:- 2061-10-10T00:00:00Z
Example:- bd_1726477951
Example:- ASPRESENTED
Example:- 2832969600
Example:- UPDATE_PENDING
Example:- 2024-09-16T14:58:08Z
Example:- 2024-09-17T13:08:13Z
Example:- VARIABLE
Example:- 2024-09-17T13:08:13Z
Example:- 1726477958
Example:- tkn_4d0dc686b85d46b69b5aea078c09c540
Example:- cst_t1bbcrzxzofcxkjs
Example:- hTdCX9eFC6EyjttVDJagq2
Example:- false
Example:- INR
Example:- 1000
Example:- 8f076e2e12004b8bb2478b188ac3202f
Example:- 1
Example:- true
Example:- billdesk@vpa
Example:- COLLECT
Example:- UPI
Example:- billuat
Example:- EMANDATE
Example:- AFTER
Example:- true
Have questions?
- Need help? Contact support
- LLM? Read llms.txt

