Razorpay vs Stripe for International Subscriptions: Merchant Country, Card Country and Renewal Eligibility
A Bengaluru SaaS company adds a USD plan for customers in the US and Europe. Checkout works in testing. The first payments succeed. Then, month two, a batch of renewals fails, and it turns out the configuration never supported automatic renewal for one group of cards. One-time card acceptance is not the same as approval for recurring billing, and a feature that works on a global account does not automatically work on an Indian one.
This guide helps Indian subscription businesses check eligibility before they launch: which combination of merchant country, card country and currency can actually renew, how the first authorisation and later renewals work on Razorpay and Stripe, and what happens when a renewal fails. Generic pricing, merchant-of-record models and broad cross-border licensing are out of scope; see our Razorpay vs Stripe in India overview for the wider comparison.
Facts come from each provider’s public documentation, checked on 12 November 2026. Account eligibility differs between merchants, so confirm your configuration with the provider and test it in sandbox before you sell a recurring plan.
Quick answer: For an India-based business charging overseas customers on international cards, Razorpay documents international-currency subscriptions through cards with settlement in INR, using its Subscriptions product with defined retry, pending and halted states. Stripe’s India-specific documentation focuses on RBI e-mandates for India-issued cards: mandates need additional factor authentication, customers get a pre-debit notification at least 24 hours before each charge, Stripe waits 26 hours before charging cards, and payments above ₹15,000 need authentication each time. The deciding questions are where your merchant account is registered, where your customers’ cards are issued and which currency you bill in. Test every combination you plan to sell.
Key takeaways
- Eligibility depends on three things together: merchant account country, card-issuing country and billing currency. Check each row, not the provider in general.
- Razorpay Subscriptions supports international-currency plans on cards with INR settlement for Indian merchants, with three daily retries after a failed charge before a subscription is halted.
- Razorpay does not support manually charging a domestic card on a subscription invoice, and updates are limited to card-authorised subscriptions.
- Stripe requires an e-mandate for India-issued cards: AFA at setup, 24-hour pre-debit notification, a 26-hour charge delay for cards and AFA on payments above ₹15,000.
- On Stripe, a non-INR subscription registers an India card mandate only if an India payment method is attached when the subscription is created.
Which merchant, card and currency combination are you actually selling?
Most launch failures come from treating “international subscriptions” as one thing. Break it into rows:
| Configuration | Typical example | Razorpay | Stripe | Key checks |
|---|---|---|---|---|
| India-based merchant, overseas-issued cards, foreign currency | Indian SaaS billing US customers in USD | International-currency subscriptions documented on cards, settled in INR; international payments must be enabled | Depends on your Stripe account’s availability and features in India; confirm with Stripe | International card activation, supported currencies, export documentation |
| India-based merchant, India-issued cards, INR | Indian SaaS billing Indian customers | Card, UPI and eMandate subscriptions; RBI e-mandate rules apply | E-mandate flow for India cards and UPI via Subscriptions | AFA at setup, pre-debit notification, ₹15,000 threshold |
| Non-India merchant, Indian customers’ India-issued cards | US company billing customers in India | Not the Razorpay India use case | E-mandate required for India cards; mandate currency rules depend on account country | Attach India card before creating non-INR subscription |
Keep billing currency, settlement currency and the mandate path separate. An Indian merchant can bill in USD and settle in INR; an India-issued card on a USD plan still falls under RBI e-mandate rules.
How does the first authorisation work for an overseas subscriber?
On Razorpay
The customer subscribes through Razorpay Checkout and authorises their card for the plan. Razorpay links the subscription ID to each invoice and payment, and subscription payments are captured automatically. For an overseas card on a foreign-currency plan, the customer is charged in the plan currency and the Indian merchant receives INR. Your account must have international payments enabled; foreign-card payments also carry export-related compliance, covered in our PA-CB rules guide.
Before launch, confirm: the currency is supported for subscriptions on your account, the plan uses card authorisation, and your website shows the information Razorpay requires for international activation.
On Stripe
Stripe creates an invoice and PaymentIntent for the first payment. A subscription stays incomplete until the first invoice is paid, and if the customer does not pay within 23 hours it moves to incomplete_expired. Whether additional authentication is needed depends on the issuer and Stripe’s risk rules. For overseas-issued cards, Stripe’s standard Billing behaviour applies; the India-specific e-mandate requirements are triggered by India-issued cards and UPI, not by every foreign card.
Contrast: the India-issued card case
For India-issued cards, the customer registers an e-mandate through AFA (3D Secure for cards, UPI PIN for UPI). On Stripe, mandates are managed through Subscriptions, not through PaymentIntents or SetupIntents directly, and you cannot pass an existing mandate to a subscription or update a mandate. On Razorpay, the same RBI rules apply to card, UPI and eMandate subscriptions in India.
What happens at renewal?
| Step | Razorpay (cards) | Stripe (India-issued cards) |
|---|---|---|
| Notification before charge | Per RBI rules for domestic mandates | Bank sends pre-debit notification at least 24 hours before |
| Charge timing | On the subscription’s charge date | Stripe waits 26 hours after the payment request before charging cards; PaymentIntent stays processing and cannot be cancelled |
| Higher-value renewals | Per RBI ₹15,000 threshold for domestic mandates | AFA required each time above ₹15,000 or the mandate maximum, via a link in the pre-debit notification |
| Customer opt-out | Customer can cancel the mandate | Customer can cancel from the pre-debit notification |
| What links payments | Subscription ID, invoice ID, payment ID | Subscription, invoice, PaymentIntent and Mandate objects |
Stripe also exposes why a mandate is inactive, with reasons such as issuer_not_supported, currency_not_supported and card_not_supported. The currency_not_supported reason is a useful signal that a non-INR mandate on an India card will not work and an INR plan might.
How do failed renewals and plan changes compare?
Failed renewals are where configurations quietly diverge. Keep each restriction next to the card country it applies to.
Razorpay
- After a failed auto-charge on day T, Razorpay retries once a day on T+1, T+2 and T+3.
- The subscription moves to
pendingafter the first failure and tohaltedif all retries fail, withsubscription.pendingandsubscription.haltedwebhooks. - If the customer updates their card while pending, the last invoice is auto-charged; from halted, a card update returns the subscription to active, but invoices raised meanwhile must be charged manually.
- Manual charging of a domestic card is not supported, according to Razorpay’s documentation.
- Customers can change cards via an emailed link, Checkout with
subscription_card_change, or a hosted update page. - Updates (plan, quantity, start date, total count) are allowed only for card-authorised subscriptions in
authenticatedoractivestates, either immediately with proration or at the end of the cycle.
Stripe
- A failed renewal makes a subscription
past_due; your retry settings and failed-payment settings then decide whether it stays past due or becomesunpaidorcanceled. - For India-issued cards under e-mandates, Stripe’s documentation describes a single attempt regardless of retry settings, so plan your own customer outreach rather than relying on Smart Retries.
- Decline codes such as
transaction_not_approved(customer paused or did not authenticate) anddebit_notification_undeliveredexplain e-mandate failures. - Charging an inactive or cancelled mandate returns
payment_intent_mandate_invalidorindia_recurring_payment_mandate_canceled; check mandate status before charging.
Recovery comparison
| Situation | Razorpay | Stripe |
|---|---|---|
| Renewal fails on a card | Three daily retries, then halted; card update link | past_due; retries per settings (single attempt for India cards) |
| Customer changes card | Emailed link, Checkout card change or hosted page | Collect new payment method; update default payment method |
| Plan upgrade mid-cycle | Allowed for card-authorised subscriptions, with proration or at cycle end | Supported through subscription changes; India mandates cannot be updated |
| Mandate invalid | Customer re-authorises | Error codes identify inactive or cancelled mandates |
Neither column is a universal advantage. Verify the recovery path for foreign-issued cards separately from India-issued cards.
What should you test before going live?
Build a labelled test plan and keep evidence from sandbox runs:
- Eligible combination: overseas test card on your foreign-currency plan; confirm first charge, subscription ID and INR settlement record.
- Unsupported combination: a card or currency you do not plan to support; confirm the error is clear to the customer.
- India-issued card: mandate setup with AFA; pre-debit notification; renewal. On Stripe, use its test cards for mandate success, customer cancellation, undelivered notification and cancelled mandate.
- Renewal failure: force a decline; confirm webhooks, customer emails and state transitions (pending and halted on Razorpay; past_due on Stripe).
- Re-authentication: customer updates card from the link or page provided.
- Plan change: upgrade and downgrade at once and at cycle end; check proration minimums.
- Cancellation: customer cancels; confirm no further charges.
- Reconciliation: match foreign-currency invoices to INR settlements and your accounting entries.
Questions to resolve with each provider before launch: Is international recurring enabled on our account? Which currencies? What happens to foreign-issued card renewals that fail? Which documents do you need for export compliance? Supported recurring billing and a passing test do not guarantee live activation or regulatory compliance; keep subscription management, payment processing and your tax and export obligations distinct.
Common eligibility mistakes to avoid
- Assuming one-time acceptance means recurring approval. International card payments on your checkout do not prove that subscriptions in that currency will renew. Ask for recurring activation explicitly.
- Copying a global setup to an Indian account. Features and currencies available on a provider’s US or EU entity may not apply to your Indian merchant account. Check the documentation for your account country.
- Mixing card countries in one plan without testing. A USD plan bought with an India-issued card triggers e-mandate rules; the same plan bought with a US card does not. Test both.
- Creating the subscription before attaching the card (Stripe). For non-INR subscriptions, Stripe registers an India card mandate only if the India payment method is attached first.
- Relying on automatic retries for India cards. Razorpay retries cards over three days; Stripe’s India e-mandate flow may make a single attempt. Plan customer emails and in-app prompts for both.
- Forgetting the ₹15,000 threshold. Renewals above this amount on India-issued cards need authentication each time, which lowers automatic success. Consider annual plans and messaging carefully.
- Treating settlement as revenue recognition. Foreign-currency invoices settled in INR still need correct accounting, export documentation and GST treatment. Keep the finance team in the launch plan.
A quick pre-launch matrix to fill in
| Question | Razorpay answer | Stripe answer |
|---|---|---|
| Is recurring enabled for our currency? | ||
| Which card countries can renew? | ||
| What happens after a failed renewal? | ||
| Can customers update cards themselves? | ||
| How are mandates cancelled and reported? | ||
| Which export documents are provided? |
Fill this in with written answers from each provider before you announce the plan.
Why we recommend Razorpay for Indian businesses launching international subscriptions
For an India-based SaaS or content business adding foreign-currency plans, we recommend Razorpay when international payments and subscriptions are enabled on its account. Our reasons:
- India-first configuration: Razorpay documents international-currency subscriptions on cards with INR settlement for Indian merchants, which matches the most common exporter setup.
- Predictable failure handling: three documented daily retries, clear pending and halted states and webhooks make dunning straightforward to build.
- One stack for domestic and international: the same Subscriptions product covers Indian customers on cards, UPI and eMandate, so you do not run two billing systems.
- Export compliance alongside: Razorpay’s international payments run under its PA-CB framework, which keeps payment processing and export documentation in one place.
These are fit-based reasons. They do not mean Razorpay supports every currency or card on every account, or that renewals cannot fail.
When Stripe may fit better
Stripe may suit businesses with a non-India Stripe entity, global Billing requirements or deep usage of Stripe’s subscription tooling across countries. Its India documentation is explicit about e-mandate mechanics, mandate inactive reasons and test cards, which helps engineering teams simulate failures precisely. Confirm your account’s eligibility for the configuration you plan to sell, especially the rule that non-INR subscriptions register India card mandates only when an India payment method is attached at creation.
FAQs
1. Can an Indian company charge overseas customers a USD subscription?
Yes, with the right setup. Razorpay documents international-currency subscriptions on cards with settlement in INR, provided international payments are enabled on your account. Confirm supported currencies with your provider and keep export documentation in order.
2. Does RBI’s e-mandate rule apply to foreign-issued cards?
The RBI e-mandate framework applies to India-issued cards and other Indian payment methods such as UPI. Foreign-issued cards follow their own network and issuer rules. Stripe’s India recurring documentation applies to customers using India cards or UPI, whether the merchant is in India or abroad.
3. How many times does Razorpay retry a failed subscription payment?
For cards, Razorpay retries once a day on the three days after the failed charge (T+1, T+2, T+3). The subscription is pending during retries and moves to halted if they all fail. Customers can update their card to resume.
4. Why do Stripe renewals on Indian cards take more than a day?
Customers must receive a pre-debit notification at least 24 hours before the charge. Stripe waits 26 hours after a payment request before charging India cards, adding a buffer for downstream issues. The PaymentIntent stays processing during that time.
5. Can I manually charge a failed subscription invoice on a domestic card with Razorpay?
No. Razorpay’s documentation states that manual charging of a domestic card is not supported. Ask the customer to update their card through the provided link or Checkout instead.
6. Why was no mandate created for my Stripe USD subscription with an Indian card?
For non-INR subscriptions, Stripe registers a mandate only if an India payment method is attached to the customer when the subscription is created. Attach the India card first, then create the subscription.
7. Does a successful sandbox test guarantee live renewals will work?
No. Sandbox tests confirm your integration handles each case, but live activation depends on account approval, issuer support and currency eligibility. Monitor the first live renewal cycle closely.
8. Should I offer annual or monthly international plans?
It depends on your customers and card mix. Annual plans reduce the number of renewals that can fail, but larger amounts on India-issued cards above ₹15,000 need authentication each time. Monthly plans renew more often but usually stay below that threshold. Test both with your actual card mix.