Payments are the part of an online store that customers notice once and your finance team notices every week. The gateway decides how much you keep, when the money arrives, what happens when a payment fails, and how easily you can prove an order was paid. Comparing providers on headline fees alone misses most of what matters.
What to compare beyond the fee
Fees are public and change, so read the current schedule from the provider rather than relying on a blog post, including anything per transaction, per payment method or monthly. Beyond that, compare settlement timing, whether payouts can be held and why, what onboarding documentation is required, whether the provider supports the payment methods your customers prefer, and whether international cards are relevant to you. Also check the chargeback process, since that is where time and money are lost.
Compare how providers handle failures
Ask how the store behaves on a declined card, a timed-out page and a cancelled checkout. The customer should see a clear message and be able to try again without losing their cart. Ask whether payments can be retried while they are still on the page, and whether the order is created only after the payment is confirmed. A store that creates orders on intent rather than on success will fill your support inbox with orders nobody paid for.
Settlement and reconciliation matter more than fees
A small difference in fee is irrelevant if the money arrives when you cannot pay a supplier. Ask when funds become available, whether the first payout works differently from later ones, and what triggers a hold. Then ask how you will reconcile each payment against the order and the settlement report. A regular export you can match against your own records is worth a lot, because manual matching does not scale.
Integration effort is a real cost
Some gateways connect to common store platforms with configuration. Others require code, and some need a developer to maintain the connection each time the provider changes an API. Ask what the integration needs, who holds the merchant account, and what happens if you later change gateway. Confirm that card details are handled on the provider's side rather than passing through your own server, and that your store is served over a secure connection.
Fraud, risk and account health
Providers monitor transactions and may hold orders, ask for documents or restrict an account if they see unusual patterns. Ask what triggers a review, which documents are usually requested, how quickly a hold is resolved, and who you contact when it happens. Keep your business details current with the provider, because stale information is a common reason a good seller is asked to verify repeatedly.
Test the refund and return path
A payment gateway is only half the system; the other half is giving money back. Check how a full refund, a partial refund and a return initiated by the customer each behave, and how long the customer waits for the amount to appear. Check whether shipping, taxes and discount allocations are refunded correctly. Ask whether refunds can be initiated from your own system or only from the gateway dashboard.
Understand what a customer sees at checkout
Look at the payment step as a customer, not as an administrator. Confirm that the amount shown matches the cart total, that any additional charge such as a convenience fee or shipping is disclosed before the customer confirms, and that returning to your store works without losing the cart. A confusing final step is one of the most common reasons a prepared customer abandons a purchase.
What the provider needs from you
Expect to provide business identity documents, bank details matching your business records, address proof, a website or marketplace presence, and a description of what you sell. Some categories require additional approvals before payments are enabled, and those categories are decided by the provider, not by you. Start this early and keep documents consistent, since mismatches are a frequent cause of verification delays.
Questions to put to a provider
Ask for the current fee schedule in writing rather than a summary. Ask what the integration requires and how long it takes. Ask about settlement timing, holds and chargebacks. Ask who owns the merchant account and whether it can be transferred if you change developers. And ask what support looks like when a payment fails for a real customer in the evening, because that is when it matters.
Keep the gateway and the store aligned
Agree in advance who handles a failed payment, a duplicate charge, a refund a customer disputes and a payout that has not arrived. Write those four cases into your support process so nobody has to decide during an incident. Keep the gateway configuration and your accounting categories in step, because reconciliation errors usually come from a mismatch between what the customer paid and what your books recorded. A short monthly check catches more problems than any single alert.
Our e-commerce guides cover the rest of the setup. If you want payment configuration handled as part of a build, our e-commerce development work starts at INR 35,000 per project, with hosting, platform subscription, payment gateway charges, shipping and ad spend billed separately by their own providers, and you can send us your requirements for a straightforward plan.
Common questions
Which payment gateway should a small Indian store use?
There is no single right answer, because the decision depends on your average order value, how many transactions you expect, whether you need an international card option, and how comfortable you are with the provider's onboarding. Most Indian sellers compare a well-known bank or aggregator route against a specialist provider. Ask each one for written fee details, settlement timing and what happens on a failed payment.
Why are more payment options not always better?
Each option you add has a cost, a failure rate and a reconciliation burden. Some are worth enabling, but too many checkout buttons make the page busier without improving completion, and every extra line item needs settling and checking in your accounts. Enable what your customers actually ask for at checkout, then review whether anything you enabled is rarely used.
Does the payment gateway affect how quickly I get my money?
It can, because providers differ in how often they settle and how quickly withdrawals become available. A short delay for a small seller is manageable; a long or unpredictable delay makes it harder to pay suppliers and staff on time. Ask what the standard and exceptional settlement timelines are, what causes a hold on a payout, and what documentation you must keep to release funds.