Available in🇮🇳 India
Cards Recurring lets you charge a customer’s credit or debit card automatically after they authorise it once. It works on Visa, Mastercard and RuPay cards issued in India. The customer authenticates the first payment with an OTP. After that, you debit the card on your schedule, and Razorpay sends the customer the pre-debit notification that RBI requires before each debit.
How Cards Recurring Works
When a customer registers their card for recurring payments, Razorpay creates two linked records:- Recurring token: Razorpay’s record of the mandate on the customer’s card, identified by a
token_id. You use thetoken_idfor every future debit. - Mandate: the customer’s standing instruction that lets you debit their card. It is registered with a mandate hub, such as Razorpay’s MandateHQ or BillDesk’s SiHub. The mandate hub stores the mandate, sends the customer pre-debit notifications and AFA requests, and lets the customer pause or cancel the mandate.
Lifecycle
- Registration: The customer completes the first payment and authenticates with an OTP. The recurring token moves from
initiatedtoconfirmedin real time. - Debit: You create an order and a payment on the recurring token. The mandate hub sends the customer a pre-debit notification, and the card is debited 36 hours later. If the amount is above the AFA limit, the customer instead gets an approval link that is valid for 72 hours.
- Changes: The customer can pause, resume or cancel the mandate from their bank’s or mandate hub’s portal, and you get a webhook for each change.
AFA Limits
AFA (Additional Factor of Authentication) is the customer’s approval that RBI requires for high-value recurring card debits. Whether a debit needs AFA depends on the amount and your business category.AFA Limit by Business Category
- ₹15,000: most businesses.
- ₹1,00,000: mutual fund subscriptions, insurance premiums and credit card bill payments. The merchant category codes (MCCs) eligible for this limit are listed below.
Your business category is set during onboarding. If you are not sure which limit applies to you, check with your Razorpay account manager.
AFA rules apply only to cards issued in India.
Integration Steps
Integrate Cards Recurring using Razorpay APIs in these steps:- Create the Authorisation Transaction: register the card mandate. The recurring token is created when this payment succeeds.
- Fetch and Manage Tokens: check that the mandate is registered and track the token status.
- Create Subsequent Payments: charge the customer on the confirmed token whenever a payment is due.
- Webhooks: subscribe to webhooks to track token and payment status changes.
Token Statuses
As the authorisation transaction moves through its different states, the recurring token that is generated also undergoes state changes. Following is the life cycle of a recurring token:Before You Charge
- Pre-debit notification: When you create a payment, the mandate hub notifies the customer, and the card is debited 36 hours later. Debits above the AFA limit need the customer’s approval through a link that is valid for 72 hours.
- Amount: A debit cannot exceed the recurring token’s
max_amount. Setmax_amounthigh enough to cover the largest debit you expect to make on this recurring token. Debits above the AFA limit need the customer’s approval before the card is debited. - Frequency: On a fixed-frequency token, such as one backing a subscription, only one debit is allowed per frequency cycle. Because the debit happens 36 hours after you create the payment, do not create it at the very end of a cycle. On a charge-at-will token there is no such restriction, so you can debit whenever you need to, within the token’s
max_amountand expiry.