Indian government regulations affecting card payments require the use of network tokenisation to save the card information of India-issued cards. You'll need to update your existing Stripe integration following the steps outlined in this guide. You could see more payment failures if your Stripe integration doesn't comply with local regulations.
If you're a Stripe user based in India, to ensure that existing saved cards continue to work with network tokenisation and before saving a new card with Stripe, you must:
- collect cardholder consent, and
- perform 3D Secure (3DS) authentication.
Collect cardholder consent to save a new card
- Ensure that your checkout flow allows users to opt in or out of saving their card details. This allows Stripe to securely save the card information as a unique token in line with regulations.
- Be transparent with your customers about how you intend to use the saved card information as well as how they can delete their saved card details.
Perform 3D Secure authentication before saving the card
Cards must be authenticated via 3DS before they can be saved for future use. 3DS authentication completed during a payment is sufficient to save the card information.
Integration changes for Stripe API users
Review the table below to see if any changes need to be made to your Stripe integration.
If you're currently using: |
Changes required for cardholder consent |
Changes required for 3DS authentication |
Stripe-hosted Checkout, Payment Links or Invoices |
No changes required |
No changes required |
Payment Intents API with setup_future_usage enabled to save payment details from a purchase |
No changes required |
No changes required |
Setup Intents API to save a customer's card without an initial payment. |
No changes required |
No changes required |
Attaching a PaymentMethod object to a customer directly or Creating a customer with a payment method |
Not supported |
Saving a card directly to a customer doesn't trigger authentication via 3DS. This doesn't meet the regulatory requirement and the API is likely to see failures in the future. |
Saving a card created via the Sources or Tokens APIs |
Not supported. To get the latest Stripe features and seamlessly stay compliant with ongoing regulations, migrate to the Payment Intents, Setup Intents and Payment Methods APIs. |
Same steps as above |
For further details, refer to our FAQs or contact Support.