Fluxx Tech
Most Indian businesses shortlist the same few payment gateways. They look broadly similar: UPI, cards, net banking, wallets, a dashboard and APIs. The differences show up in settlement speed, support quality, developer experience and extra features you may need later.
Rather than declaring a winner, here is how to compare them for your business.
1. Transaction charges
Published rates change and are often negotiable at volume. Ask each provider for written rates for:
• UPI transactions
• Debit cards, by amount slab
• Credit cards
• Net banking
• Wallets
• International cards, if needed
• EMI
Then apply them to your actual mix. A gateway that is cheapest on cards may cost more overall if most of your payments come through UPI.
2. Settlement cycle
How many working days until money reaches your bank? Standard cycles are commonly T+1 to T+3. Faster settlement, same-day or instant, is usually available at extra cost. For businesses with tight cash flow, this matters more than a small rate difference.
3. Payment methods and checkout experience
• Does checkout work smoothly on mobile?
• Is UPI intent supported, so the customer’s app opens directly?
• Are saved cards and tokenisation handled?
• Can you customise the checkout with your branding?
• How many clicks from cart to confirmation?
Test each gateway’s demo checkout on a phone before deciding.
4. Developer experience
For your development team:
• Quality of documentation
• Official SDKs for your stack: PHP, Node, Python, Flutter, React Native
• Test environment that behaves like production
• Webhook reliability and retry behaviour
• Clear error codes
Poor documentation and flaky test environments add days to a project.
5. Features beyond checkout
Feature | Why you might need it |
Payment links | Collect money without a website |
Subscriptions and e-mandates | Recurring billing |
Payment pages | Simple hosted pages for small sellers |
Split payments | Marketplaces paying multiple vendors |
Smart routing | Automatic fallback between banks |
Invoicing | Billing without separate software |
Settlement reports | Easier reconciliation |
Marketplaces in particular should check split settlement support early; retrofitting it is painful.
6. Support
When payments fail, you need answers quickly. Ask:
• Is there a dedicated account manager at your volume?
• What are support hours and channels?
• How are disputes and chargebacks handled?
• What is the typical response time?
Ask other businesses in your industry about their real support experience.
7. Onboarding and KYC
Some categories face extra scrutiny: education, healthcare, financial services, travel and anything regulated. If you are in one of these, confirm your category is accepted before you build.
A practical way to decide
1. List your must-have payment methods and features
2. Get written rates from two or three providers
3. Calculate monthly cost using your actual transaction mix
4. Test each checkout on mobile
5. Have your developer review the documentation
6. Check support reputation
7. Choose, and keep a second provider in mind as backup
Frequently asked questions
Which gateway is cheapest? It depends on your payment mix and volume. Calculate with your own numbers rather than comparing headline rates.
Can I switch gateways later? Yes, though it means integration work and re-testing. Keeping payment logic separate in your code makes switching easier.
Should a small shop use payment links instead? If you have no website yet, payment links or hosted pages are a quick way to start collecting payments.
