Why Your International Payment Gateway Is Declining Indian Cards

Here’s What’s Actually Happening

You’re watching the dashboard. Traffic from India looks healthy. The cart is full, the customer is clearly trying to pay, and the payment fails. You check the card details. They are fine. You assume it is a fluke. Then you notice it is happening to a large share of your Indian card transactions.

The problem almost certainly isn’t your customers, and it isn’t a bug in your checkout. Indian card payments run on rules and rails that a standard international payment gateway setup was never built to satisfy. 

Here is what is actually happening under the hood, and what to do about it.

India doesn’t process cards the way the rest of the world does

Most countries clear a card payment with little more than a number, an expiry, and a CVV. India does not. The Reserve Bank of India (RBI) requires an Additional Factor of Authentication, usually an OTP or an in-app 3-D Secure step, on all online card transactions. If your checkout doesn’t trigger and complete that step cleanly, the bank declines the payment. There is no useful error message. The customer just sees a failure and blames you.

Tokenisation adds another layer. Since October 2022, RBI rules mean merchants and gateways cannot store raw card numbers. Cards have to be saved as network tokens issued through the card networks. A setup that isn’t fully tokenised for India loses saved-card and repeat payments at a much higher rate than it should.

Where your payment gets routed matters more than the card

Here is the part most people miss. 

When an Indian customer pays on an international payment gateway, the transaction is usually processed through a foreign acquiring bank. The customer’s Indian issuing bank then sees a cross-border charge from an overseas acquirer. Indian banks decline those far more often than they decline domestic ones. Some of that is risk policy. Some are regulatory caution. Some is just how the rails are wired. The result is the same. A payment that would have gone through on a local Indian acquirer gets bounced.

That single fact, the distance between the acquirer and the issuer, is the most common reason “my Indian cards keep failing” shows up on founder forums. It is rarely the card itself.

The Recurring-payments Trap

Subscriptions make it harder, and this is where a global setup quietly breaks.

Recurring card charges in India run under the RBI’s Digital Payments E-mandate Framework, 2026, which pulled eight earlier circulars into one set of rules covering domestic and cross-border recurring transactions on cards, UPI, and prepaid instruments. A recurring charge needs a registered mandate, set up with initial authentication. The customer must get a pre-debit notification at least 24 hours before each debit. Charges run without fresh authentication up to ₹15,000 for standard services and up to ₹1,00,000 for select utilities like insurance, above which each transaction must be authenticated again.

Here is the part most global processors have not solved. Many of them bill Indian subscribers with a plain non-3DS charge, an un-authenticated transaction repeated each cycle, which worked as a grey-area workaround for years. That door is closing. Under the RBI’s digital payment authentication directions, Indian issuers will block all static, non-authenticated card-not-present transactions starting 1 October 2026, cross-border charges included. From then, the only compliant way to raise a subscription charge on a card is a registered mandate routed through the card networks’ Standing Instruction (SI) Hub. A gateway still running plain non-3DS recurring charges simply stops getting paid.

Even with a compliant mandate, the mechanics bite. Because the framework mandates a strict 24-hour pre-debit notification window, gateways must trigger processing schedules a day in advance. If any step in that verification chain is missed, the renewal fails. 

So a SaaS company billing monthly on Indian cards can lose a slice of renewals every cycle, purely to mandate mechanics, before anyone mentions expired cards or low balances. What happens after a charge fails is where providers separate, and it is revenue most leave on the table. A foreign gateway typically marks the renewal failed and moves on, and nothing reaches the customer. Cashfree Payments instead tries to recover it, automatically sending the customer a payment link to complete the charge on time. Many “failed” renewals are only a temporary glitch, so recovering them lifts conversion with no change to your pricing or your product.

The Onboarding Wall

One more thing piles on. 

Onboarding a global processor in India can be narrow for new businesses, and often expects an Indian entity or a GST registration. Many merchants end up pushing India traffic through a setup that was never fully localised in the first place.

How to actually fix it

Each of these is fixable. In rough order of impact.

Process through a local Indian acquirer. This is the big one. Routing Indian card payments through a domestic acquiring partner instead of a foreign one is what moves your authorisation rate from poor to good. It is not a tweak. It decides whether the rest even matters.

Add the methods Indians actually use. Cards are a minority of Indian payments. By transaction volume, UPI made up about 83% of India’s digital payments in 2024, while cards and the other legacy rails together accounted for roughly 17%, according to RBI’s payment system report. UPI is how the country pays. RuPay is a card network that a Visa-and-Mastercard-only checkout ignores. Offering UPI, RuPay, netbanking, EMI & affordability options next to cards wins back customers who were never going to finish a card payment.

Get tokenisation and authentication right. Store saved cards as RBI-compliant network tokens. Make sure the OTP or 3-D Secure step renders properly on mobile, where most Indian payments happen.

Use smart routing and retries. A good Indian gateway retries a failed transaction down a different route and times the retry based on why it failed. A bank outage and a low-balance decline are different problems and should not be retried the same way.

You can build some of this yourself. The cleaner path is to run Indian payments on local rails from the start, and this is where a domestic provider like Cashfree Payments has a structural edge over a global processor. Domestic acquiring, UPI, RuPay, netbanking, EMI, RBI-compliant tokenisation, and e-mandate handling are the default, not an add-on. 

Cashfree routes intelligently across these methods and reports checkout success rates of 80% and above once payments run on local rails, well beyond what cross-border card routing usually returns. Card data is stored as network tokens, and India’s mandatory identity verification is built into the checkout flow rather than bolted on.

Cashfree Payments is India’s first licensed cross-border payment aggregator (PA-CB, Export and Import). For a business based outside India, that is the other half of the same problem. You can accept payments from Indian customers using every local method above, with no Indian entity or local bank account, and settle to your overseas account in your preferred currency. Funds are settled by SWIFT or wire transfer on a T+2* business-day basis, across 100+ settlement currencies, at zero-cost FX in the overseas bank account, with settlements, refunds, and disputes tracked from a single dashboard and API.

If your international payment gateway is declining your Indian cards, it is not bad luck. It is a localisation gap. Close it with local acquiring and the methods Indians actually use, and the declines mostly disappear.

FAQs

1. Why are Indian cards declined on international payment gateways?

Indian card payments can fail because of cross-border routing, authentication requirements, tokenisation, issuer risk checks, or recurring-payment rules. A gateway without India-specific payment infrastructure may not handle these requirements correctly.

2. How can I improve Indian card payment success rates?

Use domestic acquiring where possible, support RBI-compliant authentication and card tokenisation, and offer local payment methods such as UPI, RuPay, netbanking and EMI. Smart routing and appropriate retries can also help recover failed transactions.

3. Can international businesses accept payments from Indian customers without an Indian entity?

Yes, depending on the payment provider and its regulatory setup. Cashfree Payments’ PA-CB infrastructure enables eligible international businesses to accept payments from Indian customers using local payment methods without requiring a separate Indian entity or local bank account.

4. Why do recurring payments on Indian cards fail?

Recurring card payments in India have additional requirements around mandates, authentication and pre-debit notifications. If a gateway does not correctly support these requirements, subscription renewals can fail even when the customer’s card is valid.