Ask issuer to notify the shopper
Sends a request to the issuer so they can inform the shopper about the upcoming recurring payment. This endpoint is used only for local acquiring in India. For more information, refer to Recurring card payments in India.
The amount of the upcoming payment.
Date on which the subscription amount will be debited from the shopper. In YYYY-MM-DD format
Sequence of the debit. Depends on Frequency and Billing Attempts Rule.
Reference of Pre-debit notification that is displayed to the shopper. Optional field. Maps to reference if missing
The merchant account identifier with which you want to process the transaction.
This is the recurringDetailReference returned in the response when you created the token.
Pre-debit notification reference sent by the merchant. This is a mandatory field
The ID that uniquely identifies the shopper.
This shopperReference must be the same as the shopperReference used in the initial payment.
This is the recurringDetailReference returned in the response when you created the token.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
200 - OK
The request has succeeded.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.
500 - Internal Server Error
The server could not process the request.