E-commerce Development
Catalogue, cart, checkout.
Read moreE-commerce · Delhi NCR & remote
A payment that works is not the hard part.
Anyone can make a test transaction succeed. The work is in what happens when it does not: the timeout, the double charge, the refund, and the order that was paid for but never created.
Short answer
Payment gateway integration connects your site to a provider such as Razorpay, PayU, CCAvenue or Stripe so customers can pay. Doing it safely means verifying every payment server-side through webhooks rather than trusting the browser, handling failures and duplicates, and making refunds and reconciliation possible without manual repair.
Server-side verification
Razorpay, PayU, CCAvenue, Stripe
Refunds and reconciliation
UPI, cards, net banking
Free integration review
Get a free quote
Four details. A real reply the same day, from me.
Orders paid but not recorded?
Get a Free Quote
WhatsApp
01 The premise
The mistake that costs real money.
The commonest payment bug I am called in to fix is the same one every time: the site marks an order as paid because the customer’s browser returned to a success page. That is trusting the least trustworthy participant in the transaction. A customer can reach that URL directly. A network can drop between the payment and the redirect. A browser can be closed at exactly the wrong moment.
The correct pattern is that the gateway tells your server, directly, through a signed webhook, and your server verifies the signature and the amount before recording anything. The browser redirect is a courtesy to the customer, not a source of truth. This is not exotic — every gateway documents it — and it is skipped constantly because the happy path works without it.
The other half is failure. Payments time out. Webhooks arrive twice. A customer pays, the confirmation is lost, and they pay again. Each of those has a correct handling, and a store without it accumulates a slow trickle of disputes and unhappy calls that nobody traces back to the integration.
02 Comparison
The Indian gateways, compared honestly.
They are more alike than their marketing suggests. These are the differences that actually affect you.
| Gateway | What it is genuinely good for |
|---|---|
| Razorpay | The common default for Indian startups and SMEs. Good documentation, quick onboarding, strong UPI support, and a dashboard your accounts person can use. |
| PayU | Long established with wide bank coverage. Often competitive on rates at volume, and worth quoting against Razorpay rather than assuming. |
| CCAvenue | Very widely used by older Indian businesses and a lot of enterprise integrations. More payment methods than most; a dated developer experience. |
| Stripe | The right choice when you sell internationally or need sophisticated subscription billing. Less natural for purely domestic Indian retail. |
| PhonePe / Paytm | Strong where UPI dominates your customer base, especially for lower-value consumer transactions. |
03 Scope
What a correct integration includes.
Ask any developer quoting for this whether all six are in scope. The answer is informative.
Non-negotiable
- Server-side verification. Every payment confirmed by a signed webhook and an amount check. The browser is never the source of truth.
- Idempotent handling. The same webhook arriving twice must not create two orders or refund twice. Gateways retry by design.
- Failure states designed. Timeout, decline and abandonment each land the customer somewhere sensible with their cart intact.
- Refunds in the system. Initiated from your admin, recorded against the order, reconciled — not done in the gateway dashboard and remembered separately.
- Reconciliation. A way to match settlements against orders, because gateways settle net of fees on their own schedule.
- Logging. Every payment event recorded. When a customer says they paid, you need to be able to check rather than believe.
Free integration review
Is your payment flow actually safe?
One question tells me most of it: does your server confirm the payment with the gateway, or does it trust the page the customer landed on? Send me the flow and I will check.
- Webhook verification checked specifically
- You keep the findings either way
- Tested with real transactions and refunds
- Same-day reply, all 7 days
Free review
Get a free quote
Four details, and a real reply today.
04 Due diligence
Questions worth asking your provider.
These affect your cash flow and margin more than the headline percentage does.
- What is the settlement cycle?
- T+2 and T+7 are very different for a small business. This is often negotiable and rarely negotiated.
- What is the rate, really?
- Published rates are frequently a starting point. Volume, sector and a competing quote all move them.
- How are chargebacks handled?
- Who bears them, what evidence is needed, and how long you have. Worth knowing before the first one.
- Is UPI included at the same rate?
- UPI economics differ from cards. If most of your customers use UPI, this materially changes the true cost.
- What happens to failed settlements?
- How you are told, and how long resolution takes. The answer varies a lot between providers.
— Questions
payment integration — your questions.
Straight answers, including the ones that cost me work. If yours is not here, ask it — I reply the same day.
For most domestic SMEs, Razorpay or PayU — and it is worth getting a quote from both, because rates move with volume. CCAvenue suits businesses needing wide payment-method coverage. Stripe is the choice when you sell internationally or need serious subscription billing.
Yes, as long as card details never touch your server. The gateway’s hosted page or embedded widget collects them, and your site only receives a confirmation it verifies server-side. That keeps you out of the heavier PCI obligations, and it is how it should be built regardless.
With webhook verification it does not stay broken: the gateway notifies your server independently of the customer’s browser, and the order is created from that notification. Without it, this is precisely the scenario that produces a paid customer with no order — and it happens more often than people expect.
Yes. In India this uses e-mandate or UPI AutoPay, which has its own registration and notification rules. It is more involved than a one-off charge and needs the retry and dunning logic designed, not improvised.
A standard one-off checkout with proper webhook verification is usually a few days. Subscriptions, split payments or marketplace payouts take longer, mostly because the failure and reconciliation cases need designing rather than because the code is hard.
Yes, and the first thing I check is whether payments are verified server-side. That single question separates integrations that are quietly fine from those that are quietly losing orders. The fix is usually smaller than people fear.
Free consultation · No obligation
Take payments in a way you can audit later.
Tell me which gateway you use or are considering. You will get a straight answer on whether the flow is safe, what is missing, and what it costs to put right.
- Server-side verification, always
- Refunds and reconciliation in scope
- Tested with real transactions
- Fixed price agreed before work starts
Start here
Send your enquiry
Name, number, email, what you need.