Frequently Asked Questions (FAQs)

Click the below button to download the list of banks that support cards.

This is the latest version of the list and was last updated on January 2, 2023.

Watch this video to see how a customer registers for Recurring Payments using Cards.

If a customer enters card details of banks that are not available for Recurring Payments, an error message is displayed as Card does not support recurring payments.

We will migrate existing credit card tokens of OneCard bank by September 30, 2021. Therefore, you can continue to process recurring payments on such mandates even after September 30, 2021. As and when more banks become available for Recurring Payments using Cards, we will migrate the existing mandates of such banks.

All the card tokens of the banks that are not yet available for Recurring Payments on cards are put in a paused state from October 1, 2021. You cannot debit these mandates. Please contact your customers and register new mandates using other methods such as UPI or Emandate. Know more about other

You can go to the Reports section in your Razorpay Dashboard and download the token report on October 1, 2021 to know the status of all your tokens to take appropriate action.

To download the token report:

1. Log in to the

   Razorpay Dashboard

   and click the Reports from the left menu.
2. Select Token Report from the Select Report Type drop-down list.
3. Select the relevant Period from the Select Period drop-down list.
4. Select the file format from the Select Format drop-down list. You can choose CSV, XLSX or XLS formats.
5. Click Generate Report to download or get it emailed to your registered email address by selecting the Email Report To check box.

Watch this video to see how to check the token status.

There are no changes in the existing integration flow. However, we have added a few optional token parameters to the Create Order API. If these parameters are not passed in the request, the default values are assumed. Know more about

1. Starting October 1, 2021, you will have to raise the debit request 24 hours in advance for processing debits on registered mandates.
2. A pre-debit notification will be sent to the customer’s registered mobile number or email ID.
3. If they do not pause or cancel the mandate, the recurring debit will be processed, and you will get the notification through a webhook or in the dashboard.

Following is a sample of pre-debit notification:

• You can register mandates up to a maximum of ₹15,000 without any intervention from customers and process subsequent payments.
• To register and process mandates of amounts greater than ₹15,000, an Additional Factor Authentication (AFA) is required from customers for every subsequent debit.

To process subsequent debits below ₹15,000:

1. Businesses initiate the debit for an amount less than ₹15,000.
2. Bank will send a pre-debit notification SMS to the customer immediately.
3. The amount will be debited 24 hours after the notification.

To process subsequent debits above ₹15,000:

1. Businesses initiate the debit for an amount greater than ₹15,000.
2. Bank will send a notification with a link for Additional Factor Authentication (AFA) to the customer immediately. The AFA link will be active for 72 hours.
3. The amount will be debited as soon as the customer provides AFA.

Watch this video to see how the customers provide their consent through the AFA link.

No, there are no changes in processing recurring payments on international cards. The RBI guidelines apply only to domestic cards and not international cards.

For card mandates, the status is updated in real-time.

In the case of cards, the status is updated in real-time.

• For processing debits below ₹15,000, the TAT is 24 hours after raising the debit request, subject to the customer not pausing or cancelling the mandate.
• For processing debits above ₹15,000, the amount will be debited as soon as the customer provides consent through AFA, which has a validity of 72 hours.

Yes, cardholders can pause, resume and cancel card tokens from the portal provided by the bank to manage them. You will get notifications through multiple webhooks when a cardholder initiates any such changes to the card tokens. You can also see these changes on the Razorpay Dashboard.

Yes. You can use the cancel a card mandate by deleting the token. Tokens can be deleted:

• From the Dashboard

• Using APIs

Yes, you can skip the MandateHQ summary screen by enabling Skip Mandate Summary Page for Cards option from the Razorpay Dashboard.

To enable the option:

1. Log into the

   Razorpay Dashboard

   and click Account & Settings in the left menu.
2. Click Skip mandate summary page under Checkout settings.
   
3. Enable the Skip Mandate Summary Page for Cards option.
   

• Credit cards from the following networks, issued by any bank in India:
  • Mastercard
  • Visa
  • RuPay
• Debit cards on the Mastercard and Visa networks, issued by the following banks:
  • ICICI Bank
  • Kotak Mahindra Bank
  • Citibank
  • Canara Bank

We are doing a beta rollout for recurring payments via Rupay cards. This beta phase will include an on-demand enablement. You should reach out to your POCs to get this enabled.

Also, alternatively, we will choose a set of merchants to enable this feature and inform them through the POCs.

No. If you have already integrated Razorpay Subscriptions or CAW for Visa and Mastercard cards, no additional changes or integrations are required to enable RuPay cards. This applies to all cases, whether you are integrated on Standard Checkout, Custom Checkout, or S2S (server-to-server integrations).

RuPay SI requires payment processors/aggregators and banks to work with NPCI to enable the support. NPCI is continuously working with more banks to support recurring payments on RuPay cards. Refer to the

Yes. The 2021 RBI guidelines apply to all cards issued in India across network schemes, including RuPay cards.

Yes. The card needs to be tokenised during the mandate registration to process subsequent payments on the respective mandate. In all cases, Razorpay will act as an on-behalf token requestor for the business while tokenising the card with the RuPay network.