How to evaluate a payment gateway in India without reading only the pricing page
Every gateway advertises a percentage. That number is the least distinguishing thing about them. What actually affects your business is when the money arrives, how many attempted payments succeed, and how much of your week disappears into reconciliation and refunds.
Start with how you get paid
The right gateway depends on your collection pattern, and these are genuinely different products:
| Pattern | What you need |
|---|---|
| One-off invoices to businesses | Payment links or pages. You may not need a checkout integration at all |
| Online store | Hosted checkout, strong UPI and card support, order-level reconciliation |
| Subscriptions or retainers | Recurring mandates, dunning on failure, and clear customer notification handling |
| Marketplace paying out to others | Split settlements and vendor onboarding, which few gateways do well |
| International clients | Multi-currency acceptance and the export documentation your bank will ask for |
If you send twenty invoices a month, a payment link plus your invoicing software may be the entire answer. Integrating a full checkout for that is a week you did not need to spend.
Settlement is a cash-flow decision
Ask, in writing, three things: the standard settlement cycle for your merchant category, whether it changes during the first months of the account, and what triggers a hold or a rolling reserve. New or higher-risk merchants are often placed on longer cycles or reserves, and this is normal but rarely mentioned during sales.
Then check what happens around weekends, bank holidays, and month-end, because a cycle quoted in working days behaves differently in practice. For a business with payroll and vendor payments, two extra days of float matters more than a small rate difference.
Success rate beats headline pricing
A gateway charging slightly less that fails more transactions costs you more, and the failures are invisible on your invoice. Ask for success rates broken down by method — UPI, cards, net banking, wallets — for merchants similar to you, and ask what happens on retry.
You also cannot verify this claim from a pricing page, so treat provider figures as marketing and run your own test: take a small share of live traffic through a second gateway for a month and compare completed payments against attempts. That measurement is worth more than every review you will read.
The costs behind the headline rate
- Method-specific pricing. UPI, cards, international cards, EMI, and wallets are usually priced differently. Weight them by your actual mix, not the cheapest one.
- Setup and annual maintenance fees, if any.
- Refund handling. Is the original fee returned, and is there a refund charge?
- Chargeback and dispute fees, including whether the fee sticks when you win.
- Payout fees on settlements or on split transfers.
- Charges for extra products such as subscriptions, links, or smart routing, which are sometimes billed separately.
- GST on fees, which changes the effective rate you should be comparing.
Rebuild the comparison as your actual monthly cost on your actual method mix. Two gateways with identical headline percentages routinely differ once refunds and payout fees are included.
Operations questions nobody asks until it hurts
- Refunds: full and partial, how long to reach the customer, and whether you can issue one after settlement.
- Disputes: what evidence is required, who assembles it, and how long you have.
- Reconciliation: is there a settlement report that ties payouts to individual orders, and does it export cleanly for your accountant?
- Support: a real escalation path with response times, not a chatbot. Test it before signing by asking a specific pre-sales question and timing the reply.
- Onboarding: which documents are needed, and whether your business type is restricted. Some categories are prohibited or need extra approval, and finding out after building is expensive.
- Data portability: can you export customers, transactions, and — critically — migrate recurring mandates if you leave? Subscription businesses get locked in here more than anywhere else.
Compliance basics that affect the build
Do not store raw card details. Let the gateway handle card data through its hosted checkout or tokenisation, so PCI scope stays with them. Verify webhook signatures on your server and never trust a client-side success callback as proof of payment: confirm status server-side before you release goods, activate a subscription, or mark an invoice paid. That single rule prevents the most common way small e-commerce sites get defrauded.
How to run the actual evaluation
- Write down your method mix, monthly volume, average ticket size, and collection pattern.
- Shortlist two or three providers that support that pattern and accept your business category.
- Get written answers on settlement, refunds, disputes, reserves, and exports.
- Model the full monthly cost on your mix, including GST and refund behaviour.
- Run live traffic through both for a month and compare completed payments.
- Choose on completed payments and operational sanity. Use the rate only to break a tie.
Pricing pages are designed to be compared. Settlement terms, success rates, and dispute handling are the parts that decide whether the gateway is a cost or a problem.
No provider paid for inclusion. Transaction rates, settlement cycles, and product features change frequently and vary by merchant category — confirm current terms directly with each provider before signing.