Principle of operation

When creating the initial payment, the amount to be debited for future subscription charges must be specified. This amount appears in the customer’s UPI app when the mandate, which authorizes subsequent payments, is created.

To ensure clarity for merchants, the amount for the product or subscription that the merchant plans to charge in future payments should be displayed from your side to the customer. You must display the mandate message clearly in the checkout, which may require designer and front-end coordination. This allows the customer to review the payment terms at the time of mandate creation.

For example, if the merchant has sold the customer a subscription plan for up to 3000 INR, the customer sees this amount at the time of mandate creation, along with a notice that payments may be up to 3000 INR.

Any payment below the amount specified in the initial request occurs without additional confirmation from the customer. However, the customer still receives notifications the day before the subsequent payment and can cancel the subscription at any time.

Additionally, customers can easily revoke the mandate/consent agreement at any time by logging into their app and Delete AutoPay. In such cases, the merchant will receive a specific decline for any subsequent payments.

Recurring payments

❗Recurring payments up to ₹15,000 per individual transaction can be processed without customer intervention. For amounts above ₹15,000 per transaction, additional factor authentication (AFA) is required for each debit, and these are currently not supported.

Current recurring flow:

• Customer receive a pre-debit notification 24 hours before the scheduled charge.
  • If the customer opts to decline the subsequent charge, a decline response will be returned.
  • In cases where the customer does not decline the charge, a success response will be issued.

Handle UPI errors

Specific errors may occur when a UPI payment attempt fails.

• Guide
  The payment was not completed within the allocated timeframe, leading to order expiration. 0.02 Order expired
  This error occurs when the payment session expired before the customer completed the transaction. The UPI payment session remains active for 15 minutes. If the customer does not complete the payment within this time, the order is automatically declined with the 0.02 error code. Inform the customer to retry the payment and ensure they complete the transaction within the allocated time frame.
• Guide
  This error indicates an issue with the provided mobile number format. 2.01 Invalid data
  The phone number provided contains invalid characters. Validate the phone number format before submission. Only digits (0-9) and the + symbol are permitted.