You have picked a payment gateway, or narrowed it down to two, and now need it working on your website or app. One developer says it is a plugin and an afternoon's work. Another sends a quote with webhooks, refunds and reconciliation as separate line items. Both can be right, because they are describing different integrations.
This guide separates the two costs that get mixed up: what you pay the gateway on every transaction, and what you pay a developer once to build the integration. It explains what makes an integration simple or complex, and the shortcuts that later turn into lost orders and month-end mismatches.
Quick answer: Payment gateway integration cost in India has two parts. The gateway charges a fee on each successful transaction, plus GST, and sometimes setup or annual fees, so check each gateway's current pricing page. The developer charges once to build checkout, payment verification, webhooks, refunds and reconciliation. A plugin on Shopify or WooCommerce costs least; a custom app with subscriptions or split payments costs most.
Two different bills: the gateway and the developer
| Cost | Paid to | When | What to check |
|---|---|---|---|
| Transaction fee | Gateway | On every successful payment | The rate for each method: UPI, debit and credit cards, net banking, wallets, EMI and international cards |
| GST on fees | Gateway, through its invoice | On every fee charged | Whether it is deducted from settlements, and your input tax credit |
| Setup or annual fee | Gateway | Once, or yearly, on some plans | Whether your plan waives it, and for how long |
| Optional services | Gateway | When used | Instant settlement, payouts, split settlements, premium support |
| Refunds and disputes | Gateway | When they happen | Whether the original fee comes back on a refund, and any charge for handling disputes |
| Integration build | Developer | Once | Checkout, verification, webhooks, refunds, reconciliation, testing and go-live |
| Maintenance | Developer | Ongoing | API version changes, new payment methods, monitoring of failed webhooks |
What the gateway charges, and why rates are not quoted here
Gateway pricing changes often and differs by payment method, business category, volume and the plan you negotiate. Some charges are also shaped by government policy, for example on UPI and RuPay debit card payments, so a rate printed in an article can be out of date by the time you read it.
- Read the official pricing page of each gateway you are considering, on the day you decide.
- Get your rate in the merchant agreement, not only in a sales email.
- Ask about every method you will accept, especially international cards, EMI and corporate cards, which are often priced higher than domestic UPI or debit cards.
- Check settlement terms: how many days the money takes to reach your bank account, and what faster settlement costs.
- Check GST treatment: GST is charged on the gateway's fee and is usually deducted from settlements. A GST-registered business can usually claim it as input tax credit.
If you are still choosing a gateway, read how to choose a payment gateway in India and the Razorpay vs Cashfree vs Stripe comparison.
What the developer builds
- Checkout: a hosted payment page, an embedded checkout on your site, or a plugin for platforms such as Shopify or WooCommerce.
- Server-side order creation: the amount and order ID are created on your server and never taken from the browser, so nobody can change the price before paying.
- Payment verification: checking the gateway's signature on every payment response before an order is marked as paid.
- Webhooks: a server endpoint that receives payment events directly from the gateway, verifies their signature and handles repeated events without double-crediting, so orders complete even if the customer closes the browser.
- Failed and pending payments: clear messages, retry options and a way to resolve payments that stay pending.
- Refunds: full and partial refunds from your admin panel through the gateway's API, recorded against the order.
- Reconciliation: matching settlements, fees and GST against orders and your accounting system, such as Tally.
- Invoices and notifications: GST invoices, receipts and alerts once payment is confirmed.
- Testing and go-live: sandbox testing of every flow, switching to live keys, and watching the first live transactions.
What makes an integration simple or complex
| Factor | Simpler | More complex |
|---|---|---|
| Platform | Shopify or WooCommerce with an official plugin | Custom web app, mobile app, or both |
| Payment type | One-time payments | Subscriptions, UPI AutoPay or e-mandates |
| Gateways | One gateway | Two or more, with failover or routing |
| Money flow | All money settles to you | Marketplace split settlements or vendor payouts |
| Fulfilment | Orders confirmed by hand | Automatic fulfilment on webhook, with stock or access updates |
| Reconciliation | Dashboard export each month | Automated matching to orders and accounts |
| Currency | Rupees only | International cards and multiple currencies |
Recurring payments add their own steps. They follow RBI's framework for e-mandates, and UPI AutoPay and e-NACH also follow rules published by NPCI, which cover customer consent, debit notifications and limits that your integration has to handle.
As a market reference, the development firm Abbacus Technologies publishes indicative integration bands, with no date shown on the page: ₹15,000 to ₹40,000 for a basic plugin-style integration with one gateway, and ₹40,000 to ₹1 lakh for a custom checkout with webhooks, refunds and reporting, with multi-gateway, subscription and marketplace work priced above that. Treat any band as a starting point, and get quotes against a written list of the flows above.
Hidden costs and red flags
- Trusting the browser redirect: if orders are confirmed only when the customer returns to your success page, closed tabs and weak mobile networks leave paid orders unfulfilled.
- Amounts taken from the browser: a price passed from a form field can be changed before payment.
- No webhook signature check: anyone who finds the endpoint could send fake payment events.
- No refund flow: refunds done by hand in the gateway dashboard drift away from your order records.
- No reconciliation: fees, GST and short settlements only surface at month-end, when they are hardest to trace.
- The developer's account or keys: the merchant account, API keys and webhook secrets must be in your company's name and stored securely, not in code or with the developer.
- No source code handover: without it, every change or gateway switch depends on the original developer.
How EthicsComputer can help
EthicsComputer builds payment gateway integrations for Razorpay, Cashfree, Stripe, PayU and UPI AutoPay, with server-side order creation, HMAC-verified webhooks, refunds and automatic reconciliation. Every project starts with a mutual NDA and a written specification, moves through milestone sign-off, and ends with full source code and IP handover. For gateway-specific work, see Razorpay integration and payment reconciliation software.
Need a quote for your payment integration?
List your platform, the gateway you have chosen and the payment flows you need, and we will send a written scope.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.