Payment gateway integration
Taking money reliably — including the awkward cases where the customer pays but the browser never comes back.
Payments
Chosen per project
Maintainable handover
Connecting a payment gateway is straightforward until the unhappy paths arrive: a customer who closes the tab mid-payment, a UPI collect request approved four minutes later, a duplicate submission, a refund issued from the gateway dashboard rather than the application.
Every one of those is normal, and each one produces a mismatch between what the bank thinks and what your system thinks. The integration work that matters is making the server-side webhook — not the browser redirect — the source of truth.
What we build with Payment gateways
E-commerce checkout with cards, UPI, netbanking and wallets
Subscription and recurring billing with mandates
Payment links and invoices for offline sales
Refunds and partial refunds initiated from your own system
Where it fits — and where it does not
Good fit when
Any transaction where a lost payment causes a support call
Businesses needing reconciliation against a settlement report
Recurring revenue needing mandate handling
Consider something else when
Handling raw card data yourself — always use the gateway’s hosted fields
Trusting a browser redirect as confirmation of payment
Why the browser is not trusted
Two independent paths. Only one of them is reliable.
Customer pays
On the gateway’s hosted page or UPI app.
Browser may return
Or may not — closed tab, dead battery, lost signal.
Webhook always arrives
Signed, server to server, retried on failure.
Order confirmed
State changes on the webhook, then reconciled.
How we work with Payment gateways
Webhook is the truth
Order state changes on the signed server-to-server callback, never on the customer returning to a success page.
Idempotent handling
Duplicate webhooks and repeated submissions produce one order, because both will happen.
Reconciliation built in
Daily settlement comparison so a mismatch is found by the system rather than by an accountant weeks later.
No card data on your servers
Hosted checkout or tokenisation, keeping PCI scope as small as possible.
Our typical Payment gateways setup
| Concern | What we use |
|---|---|
| Gateways | Razorpay, PayU, Cashfree, CCAvenue, Stripe and PayPal |
| Methods | UPI, cards, netbanking, wallets, EMI where offered |
| Confirmation | Signature-verified webhooks as the authoritative event |
| Recurring | Mandates and subscriptions with retry and dunning |
| Reconciliation | Automated settlement matching with exception reporting |
Frequently asked questions
It usually comes down to your settlement terms, the payment methods your customers use and the rate you are offered. The integration work is similar across the major Indian gateways, so pick on commercials.
Classically, an integration that confirms on the browser redirect. With webhook-driven confirmation the order is created regardless of what the browser does.
Not if you never touch card data. Hosted checkout and tokenisation keep the card details with the gateway, which is why we build it that way.
Topics people search for
Services built with Payment gateways
E-commerce Development
Online stores where the checkout works, the stock figures are real and the order data reaches your operations team intact.
Web Application Development
Applications that run in the browser, handle real workloads and hold up when several departments depend on them at once.
Custom Software Development
Software shaped around the way your business already works, instead of a packaged product you have to reorganise around.
SaaS Development
Building a software product means building a business system around it too — tenancy, billing, onboarding and support tooling.
Tell us what you are trying to build
Describe the problem in plain language and we will tell you what it would take to solve it — the approach, the moving parts and the sensible order to build them in. No obligation either way.