# India recurring payments Learn how to update an integration to support RBI e-mandates for cards and UPI. > While the regulation refers to “recurring” payments, networks treat *any* off-session (that is, merchant-initiated) transaction as in scope, and so do we. The Reserve Bank of India (RBI) issued a [directive](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=11668) (amended subsequently in [December 2020](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=12002) and [March 2021](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=12051&Mode=0)) that introduces additional security measures for recurring payments on India issued cards and other payment methods such as [UPI](https://docs.stripe.com/payments/upi.md). These measures include: - Payment providers need to register customers and create an *e-mandate* (An e-mandate is a form of authorization provided by cardholders to issuing banks that grants permission for recurring payments on their card. Any recurring payment arrangements (for example, monthly subscriptions to OTT services) need an associated e-mandate to be successful. The e-mandate needs to be registered and then validated through AFA, such as 3DS) through a one-time process, using additional factor authentication (AFA) such as *3D Secure (3DS)* (3D Secure (3DS) provides an additional layer of authentication for credit card transactions that protects businesses from liability for fraudulent card payments) for cards or UPI PIN for UPI. - Customers must be alerted at least 24 hours before charges take place and given the ability to opt out of transactions. - Recurring transactions over 15,000 INR (or equivalent in other currencies) must go through AFA each time. If you’re an India-based Stripe user or an international (non-IN) Stripe user, your business is impacted if you have customers who use India cards or UPI for: - *Off-session* (A payment is described as off-session if it occurs without the direct involvement of the customer, using previously-collected payment information) payments - Subscriptions or Invoices where the `collection_method` is set to `charge_automatically` > For UPI-specific recurring payment details including mandate customization options, see [Recurring payments (UPI AutoPay)](https://docs.stripe.com/payments/upi/upi-autopay.md). ## How payments work with an e-mandate Stripe has worked with a partner platform to support registering e-mandates and issuing pre-debit notifications to customers. This applies to both card payments and UPI payments. > We don’t currently offer the use of e-mandates to Stripe users in Mexico. Depending on how you’ve integrated with Stripe, you might need to send Stripe additional information to set up a mandate. The customer must go through AFA (3DS for cards, or UPI PIN for UPI) to register the mandate. Subsequent off-session payments or auto-debits for a Subscription undergo a significant change. Customers need to receive a pre-debit notification at least 24 hours before the actual payment with the exact debit amount mentioned. The pre-debit notification contains information about the payment and an option to cancel the mandate. For card payments, if the payment amount is above 15,000 INR or the mandate’s maximum amount, the pre-debit notification contains a link to perform AFA (3DS) to authorize the payment. UPI currently doesn’t support recurring transactions of greater than 15,000 INR in value. For card payments, because Stripe is integrating with a partner platform, Stripe waits 26 hours before charging the customer after receiving a payment request (Stripe adds a buffer for possible downstream issues, which necessitates the 26-hour advance notification). This means that Stripe delays collecting card payments by 26 hours. For UPI payments, Stripe sends the pre-debit notification and charges the customer 1 day later. Without a mandate for an off-session payment, the payment will be declined. ## Integration ### Pre-debit notification When the off-session PaymentIntent is [confirmed](https://docs.stripe.com/api/payment_intents/confirm.md), the bank sends the customer the pre-debit notification. The PaymentIntent transitions to a `processing` state for the entire duration of the pre-debit notification period (26 hours) and can’t be canceled. ```json { "object": "payment_intent", ... "processing": { "card": { "customer_notification": { "approval_requested": true, "completes_at": 1677307005 } }, "type": "card" }, ... "status": "processing", ... } ``` If [processing.card.customer_notification.approval_requested](https://docs.stripe.com/api/payment_intents/object.md#payment_intent_object-processing-card-customer_notification-approval_requested) is `true`, the customer needs to authenticate the payment using the pre-debit notification sent to them by the bank. The [processing.card.customer_notification.completes_at](https://docs.stripe.com/api/payment_intents/object.md#payment_intent_object-processing-card-customer_notification-completes_at) attribute specifies the time that Stripe attempts to charge the payment method. If successfully processing the payment requires customer approval, they need to authenticate the payment by the specified time. ### Error and decline codes We return error [codes](https://docs.stripe.com/api/payment_intents/object.md#payment_intent_object-last_payment_error-decline_code) for the following scenarios: | Error code | Description | | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `payment_intent_mandate_invalid` | Attempting a recurring payment using an inactive mandate returns this code. You can prevent this by checking the mandate status before attempting to charge. | | `india_recurring_payment_mandate_canceled` | Attempting a recurring payment using a canceled mandate returns this code. This can happen when we only learn that a mandate has been canceled at this point. | | `processing_error` | Discovery of a (usually transient) processing error returns this code. | In the context of e-mandates, certain [decline codes](https://docs.stripe.com/api/payment_intents/object.md#payment_intent_object-last_payment_error-decline_code) have potentially more specific explanations than [in general scenarios](https://docs.stripe.com/declines/codes.md): | Decline code | Description | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `transaction_not_approved` | Attempting a subsequent payment when the customer has paused permissions to auto-debit, or doesn’t authenticate the payment when it’s required returns this code. | ## Testing You can use these [test card numbers](https://docs.stripe.com/testing.md#testing-interactively) to simulate different card mandate scenarios. In a *sandbox* (A sandbox is an isolated test environment that allows you to test Stripe functionality in your account without affecting your live integration. Use sandboxes to safely experiment with new features and changes), it takes approximately 15 minutes for an off-session PaymentIntent to transition out of the `processing` state. The on-session PaymentIntent for an initial payment never enters the `processing` state. #### Card numbers | Number | Scenario | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | 4000003560000123 | Simulates successful mandate setup and renewals. | | 4000003560000297 | Simulates a customer receiving a pre-debit notification for either canceling or pausing an off-session payment for a mandate of any amount. | | 4000003560000248 | Simulates the issuing bank’s failure to send a pre-debit notification to the customer during off-session payment for a mandate of any amount. | | 4000003560000263 | Simulates a customer canceling a mandate of any amount. | #### PaymentMethods | PaymentMethod | Scenario | | ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | | `pm_card_indiaRecurringMandateSetupAndRenewalsSuccess` | Simulates successful mandate setup and renewals. | | `pm_card_indiaRecurringPaymentFailureAfterPreDebitNotification` | Simulates a customer receiving a pre-debit notification either canceling or pausing an off-session payment for a mandate of any amount. | | `pm_card_indiaRecurringPaymentFailureUndeliveredDebitNotification` | Simulates the issuing bank’s failure to send a pre-debit notification to the customer during off-session payment for a mandate of any amount. | | `pm_card_indiaRecurringPaymentFailureCanceledMandate` | Simulates a customer canceling a mandate of any amount. | ## Limitations Keep in mind the following limitations: - Stripe attempts to automatically create mandates only on Subscriptions created after October 1, 2021. If you have a Subscription created before then, cancel and create a new Subscription to make sure a mandate is created. - You can’t create a mandate using the [Charges](https://docs.stripe.com/api/charges.md) and [Sources](https://docs.stripe.com/api/sources.md) APIs. - For Subscriptions with a non-INR currency, mandates are only registered if an India payment method is attached to the Customer at the time of subscription creation. If you create a non-INR subscription without a payment method and later add an India card, no mandate is created. To ensure proper mandate creation, attach an India payment method before creating the subscription. - You can’t pass an existing mandate to a Subscription. - You can’t cancel or update a mandate. - UPI currently doesn’t support recurring transactions of greater than 15,000 INR in value.