Every business taking card payments online watches one number: how many actually go through. For a lot of Indian merchants that number is lower than it should be, and each failed card payment is a ready buyer lost on the final screen. A few points of success rate is the difference between a good month and a leaky one.
The usual advice is to fix your checkout: add Native OTP, CVV-less payments, biometric authentication like passkeys. All of it helps. But it all sits on your side of the payment, and it quietly assumes the infrastructure underneath is fixed. That assumption is the costly part. What actually caps your success rate is the infrastructure underneath, the part you never see.
First, how a card payment actually works
Say a customer taps Pay on a ₹4,000 order. In the couple of seconds before they see “success” their payment goes through four stages, and it has to clear each one.
First the bank checks if it’s really them, usually with an OTP or a biometric. That’s authentication. Then the bank confirms the money is actually there. That’s authorization. Carrying the request between these steps and routing it to the right bank is the network’s job. And once the bank says yes, the money makes its way to your account. That’s settlement.
Four stages, two seconds, and any one of them can drop the payment.
Most failures happen in the first two. The authentication step stalls or times out because it’s routed through a slow third-party layer, or the issuing bank is hard to reach at authorization. Every one of these stages runs on infrastructure, and the more of it your provider controls directly, the more of these failures it can actually prevent.
The in-house switch: owning authentication and authorization
~3% higher card success rate · 10,000+ TPS · 99.99% uptime
The switch is the spine of a card payment, carrying the request out to the network and back for both authentication and authorization. Most providers route this through a third party, which adds a hop and a dependency at the exact stages where payments fail most.
Cashfree built its own. Authentication runs on Cashfree’s 3D Secure server, and authorization runs over a switch wired directly to Visa, Mastercard and Rupay, with no third-party layer in between. Removing that layer takes out failure points an outside switch would otherwise pass on to you, and that’s where most of the success-rate gain comes from. The capacity keeps checkouts steady through a festive spike, and owning the switch means new network features ship without waiting on a processor’s roadmap.
Dynamic routing: choosing the best path for every payment
~2% higher success rate · near-zero downtime
Instead of sending every transaction down the same road, Cashfree picks the best path for each one at the moment it happens. Connected to multiple processors and bank gateways, an AI model chooses the one performing best right then, and if that path weakens, it moves to the next best performing one. One underperforming processor no longer drags your payments down with it.
Smart retries: a second chance the customer never sees
Failed attempts retried silently, with no repeat OTP
When a payment fails at the initiation stage on one gateway, Cashfree quietly retries it through another in the background. The customer isn’t asked to re-enter an OTP and never sees the failure. As far as they know, it simply went through. It works hand in hand with routing: the retry isn’t a blind second attempt, it’s sent down a path chosen because it’s more likely to succeed.
And the real edge: tokenization
This is where owning the stack pays off most. Since the RBI mandate, saved cards must be stored as secure tokens rather than raw card numbers. The token is a stand-in for the real card, and what matters is who creates it and how directly, because that decides how the saved card behaves later.
Cashfree brings this together as Token Vault, its tokenization offering across all five schemes your customers carry: Visa, Mastercard, RuPay, Diners and Amex. Within it are two types, network tokenization and issuer tokenization.
Network tokens: Token Vault
~85% saved-card success rate · 5 schemes: Visa, Mastercard, RuPay, Diners, Amex · Interoperable
Tokens are created with the card networks, so a returning customer is recognised and checks out fast, with CVV-less and Native OTP built in. The edge is interoperability, and it works both ways. A card tokenized with Cashfree can be processed through any payment aggregator, not just Cashfree, and a card tokenized elsewhere can be processed through Cashfree too. Either way, your saved cards aren’t tied to one provider for processing.
Issuer tokens: Issuer Tokenization
~2% higher success rate · on-us processing
This goes one step closer to the source. Instead of the network, Cashfree works directly with the issuing bank to create the token and process the payment. When the same bank issues the card and holds the token, the transaction runs within that bank’s own rails instead of taking the long way through the network. That shorter path means faster processing and higher success, and it’s live across leading banks that cover the majority of the market.
Decoupled flow: each half of the payment on its best path
On by default, for every merchant
Authentication and authorization don’t have to run on the same processor. Cashfree runs each on whichever performs best for that step, instead of accepting one provider’s average across both. This happens automatically on every transaction, with nothing for you to set up, and it lifts success rates by optimizing each half of the payment on its own.
Standalone authorization: for merchants who want to run their own authentication
Some merchants prefer to handle authentication themselves and hand off only the authorization leg. Standalone authorization supports exactly that: you keep authentication in-house and rely on Cashfree purely for authorization. It’s an option rather than a default, giving you more control over the flow where you want it.
How it adds up
The switch removes structural failure points before they happen. Dynamic routing and smart retries rescue payments that would have hit a bad path. Token Vault lifts the repeat-customer and on-us cases that other setups leave on the table. Together, moving to a stack where more of the flow is handled directly rather than passed around produces a real, compounding jump in card success rate.
Whether your card success rate has plateaued or you just want to push it to its full potential, the question isn’t what else to tweak on your side. It’s how much of the stack your provider actually runs.
Sign up on cashfree to improve your success rate today!
Sign Up →Frequently asked questions
What is card payment infrastructure, and why does it affect card success rates?
Card payment infrastructure is the chain of systems a card transaction passes through from the moment a customer pays to the moment you receive the money. It includes acquiring layer, the card network, the issuing bank, tokenization, and settlement. Whether your provider owns these components has a direct effect on your success rate, your uptime, and how quickly you can ship new features.
Why do card payments fail in India?
Card payments fail at several points. At authentication, a customer might mistype or let an OTP expire, which accounts for a meaningful share of failures on its own. At authorization, the issuing bank might be slow or briefly down. In between, a processor or switch your provider depends on can have an outage.
How can I improve my card payment success rate?
The biggest lever is your provider’s infrastructure. Look for an in-house authorization switch connected directly to the card networks, AI-led dynamic routing across multiple processors, automatic background retries, and tokenization that supports on-us processing. These remove or recover the failures that cap your success rate. Checkout improvements like Card Link, Passkey, CVV-less saved cards and clean error handling help on top of that, but they cannot raise a ceiling beyond a point.
What is a payment switch and why does it matter?
A payment switch is the component that carries an authorization request between the payment platform and the card network. It matters because every hop is a potential point of failure and delay. A provider that owns its switch and connects directly to the networks can cut out a middle layer, which both reduces failures and lets it build new card features without waiting on a third party.
What is the difference between network tokenization and issuer tokenization?
Network tokenization creates the token through the card network, while issuer tokenization creates it directly with the issuing bank. The practical difference is on-us processing. With issuer tokenization, when the same bank issues the card and holds the token, the transaction can be processed within that bank’s own rails instead of routing out through the network, which is faster and lifts success rates by around two percent.
