v1
latestOpenAPI 3.0.02026-07-24270120.1 KBExecute Mandate
API to debit on existing mandates with Cards or UPI
Request body
Merchant account ID
Unique ref no to identify the request. Should have only alphanumeric characters. No other characters allowed.
Transaction amount, 9 significant and 2 decimal/precision. As sent in PDN request.
Transaction Currency
Remarks.
Merchant Aggregator ID
Mandate id as returned in create mandate flow
Possible value RECURRING or OT
txnId as received in successful PDN call for execute
billNumber as used during create api
Hash value
Response
Successful response
Response code indicating success/failure. R1000 – Request Initiated successfully Any other value indicates failure
Description of failure. Ignore for success response.
Merchant account ID
Merchant aggregator ID
Merchant Txn ref Number
Redirection URL. Will be available in case merchant is required to redirect to complete payment authorization. Either this field or showOTPCaptureP age field will be available in response.
generateOTP . Will be available when showOTPCaptureP age is ’Y’
verifyOTPURI, Will be available when showOTPCaptureP age is ’Y’
authorizeURL, Will be available when showOTPCaptureP age is ’Y’
Show OTP Page indicator, Y / N. Y – Merchant should display a page to ask for OTP. Please do contact integration team for OTP capture page requirements
The transaction context generated by the PG, Needs to be sent as is to the redirectURI / authorizeURI endpoint
Hash value