Payment Gateway Fees in India: Every Charge Explained

Payment gateway fees in India are rarely a single number. They are a schedule of chargeable events — per transaction, per payout, per refund, per dispute and per conversion — and the difference between providers usually lies in the events nobody mentions in the first meeting. This guide names every fee type, explains how each behaves as your business grows, and sets out the contract clauses that keep pricing honest over time.

What this guide covers

1. Every fee type a Indian merchant can be charged
2. Why fixed fees decide small-ticket economics
3. Method-by-method cost behaviour
4. Refund, chargeback and reversal fees
5. Payout, settlement and conversion fees
6. Tax treatment and gross-versus-net accounting
7. How to calculate your blended effective rate
8. Benchmarking without misleading yourself
9. Practical fee optimisation levers
10. Contract clauses that protect your pricing
11. Failure rate is a cost line, not a technical metric
12. How to negotiate effectively
13. Settlement, payouts and working capital
14. Regulatory and compliance context
15. Reconciliation: the cost nobody quotes
16. Common mistakes merchants make
17. Provider evaluation checklist
18. The metrics to run permanently
19. How PayEurasia approaches this

Every fee type a Indian merchant can be charged

Fees are easier to control once they are named. This is the complete taxonomy you should expect to see across providers operating in India.

• Transaction percentage. A share of the transaction value, varying by method.
• Fixed per-transaction fee. A flat ₹ amount. Decisive on small tickets, trivial on large ones.
• Method premium. An uplift applied to specific rails, commonly cards or premium wallet flows.
• Payout fee. Charged per settlement batch or per payout instruction.
• Cross-border settlement fee. Applied when funds leave India to an offshore account.
• Currency conversion spread. A margin over the reference rate, presented as a rate rather than a fee.
• Refund fee. Either a separate charge, retention of the original fee, or both.
• Chargeback or dispute fee. Per case, sometimes irrespective of outcome.
• Monthly platform or maintenance fee. Fixed, independent of volume.
• Monthly minimum. A top-up charge when variable fees fall below a floor.
• Setup or integration fee. Increasingly rare with API-first providers.
• Reporting, statement or extra-API-call fees. Uncommon but still present with some legacy integrations.

Request this list from every provider as a written schedule. A provider that discusses only the first item is describing a fraction of your cost.

Why fixed fees decide small-ticket economics

The fixed component dominates when tickets are small. A ₹10 flat fee on a ₹200 purchase is five percent before any percentage rate is applied. The same fee on a ₹20,000 purchase is 0.05 percent.

Three consequences follow.

Choose the pricing shape that matches your ticket. Small-ticket merchants should push for percentage-only or reduced-fixed pricing, even at a higher percentage. Large-ticket merchants should push for capped percentages with a flat component.

Encourage basket consolidation. If customers can combine purchases, a small nudge toward larger baskets improves payment economics measurably.

Model your mix, not your average. An average ticket of ₹3,000 formed from many small purchases and a few large ones behaves very differently from a uniform distribution. Calculate cost on the actual distribution, in buckets, and you will often find one bucket destroying margin while the blended average looks acceptable.

Method-by-method cost behaviour

Wallet collections (UPI apps, Paytm)

Wallet rails in India are optimised for high-frequency, lower-value consumer payments. Costs tend to be expressed as a percentage with a small or zero fixed component, and authorisation is fast because the customer confirms inside an app they already trust. For most consumer-facing merchants, UPI is the first rail to integrate and the one that determines the perceived quality of checkout.

Wallets carry two hidden costs. The first is limit friction: per-transaction and daily wallet limits push large payments into failure unless you fall back to a bank rail automatically. The second is customer-side timeout, where a payment is initiated but never confirmed, producing an ambiguous state that must be resolved by status polling rather than by assuming failure.

Bank rails (IMPS, NEFT, RTGS)

Bank rails typically price with a smaller percentage or a flat fee, which makes them far cheaper for large tickets. They are slower to confirm, more sensitive to bank downtime and much more dependent on accurate reference matching. Merchants that sell high-value products or serve business customers should treat bank rails as a primary rail rather than a fallback, and should budget for reconciliation tooling rather than manual matching.

Cards

Cards remain useful for international customers and for merchants selling to affluent urban segments, but in India UPI now carries the majority of online consumer volume, so a UPI-first checkout is the single biggest conversion lever. Card acceptance also brings chargeback exposure, which is an economic cost as much as an operational one, and card issuers apply stricter rules to several verticals.

Refund, chargeback and reversal fees

Refunds and disputes have three separate cost components, and providers treat them inconsistently.

The original processing fee. Some providers return it with the refund, most retain it. On a business with a ten percent refund rate, retention is a meaningful permanent cost.

A refund processing fee. A separate charge for executing the return.

A dispute or chargeback fee. Charged per case in card flows, and sometimes on wallet complaint escalations, often regardless of whether you win.

Ask three specific questions in writing: is the original fee returned on a full refund, is a partial refund charged proportionately or as a full event, and is the dispute fee refunded when you win the case.

Then reduce the volume. Fast, easy refunds prevent disputes; disputes cost more than refunds in every fee structure. In India, where wallet complaints are often resolved directly with the customer, responsiveness has an immediate and measurable fee impact.

Payout, settlement and conversion fees

Collecting money is only half the flow. Getting it into the account you actually spend from carries its own charges.

Payout fees per batch. Multiply by your settlement frequency. Daily settlement with a per-batch fee costs roughly thirty times a monthly settlement with the same fee.

Cross-border transfer fees. Charged by the sending institution, sometimes the receiving one, and occasionally both. Ask who bears intermediary bank charges.

Conversion spread. Where INR collections settle in another currency, the spread over the reference rate is a fee with a friendlier name. Ask for the reference rate source, the spread in basis points and the timestamp used.

Minimum payout amounts. Balances below the minimum roll forward, which delays cash rather than costing it, but should be modelled.

A practical control: reconcile a monthly sample of conversions against the published mid-market rate for the relevant timestamp. Merchants who do this occasionally discover that the effective spread differs from the quoted one, and that conversation is worth having with evidence rather than suspicion.

Tax treatment and gross-versus-net accounting

Two accounting decisions affect how fees appear in your books and how comparable your numbers are over time.

Gross versus net revenue recognition. Record gross transaction value as revenue and processing fees as an expense. Recording net revenue hides fee growth, makes provider comparison impossible and distorts margin analysis.

Indirect tax on payment services. Depending on the structure of your contract and the location of the contracting entities, processing fees may attract indirect tax in India. Confirm with your tax adviser whether the fee is inclusive or exclusive of applicable tax, and whether any withholding applies to cross-border payments to a provider. Get the answer in writing before signing, because the treatment can change your effective cost by a noticeable margin.

Whatever treatment applies, ensure your settlement statements itemise tax separately. A statement that shows only a net deduction is unusable for tax reporting and gives you no basis to verify the charge.

How to calculate your blended effective rate

The only number that should drive a provider decision is the blended effective rate: total cost of acceptance divided by total successfully settled value over a full month. It absorbs method mix, fixed fees, failures and payout costs into a single comparable figure.

1. Export a full month of transactions, including failed and refunded attempts.
2. Group settled value by method: UPI apps, Paytm, IMPS, cards and any other rail you run.
3. Apply the contractual percentage and fixed fee per method to each group.
4. Add payout fees, currency conversion spread and any monthly platform or maintenance charges.
5. Divide the total cost by total settled value and express it as a percentage.

Run this calculation for three scenarios: your current mix, a mix where the leading wallet grows by twenty percent, and a mix where large-ticket bank transfers grow by twenty percent. Providers that look competitive in one scenario often look expensive in another, and the scenario you should optimise for is the one your growth plan actually implies.

Two practical warnings. First, exclude test and sandbox traffic before you calculate, or your effective rate will be distorted. Second, treat currency conversion as a cost even when it is presented as a rate: a spread applied to the mid-market rate is a fee with a different label. Merchants settling outside INR routinely find that conversion is their second largest line item after processing itself.

Benchmarking without misleading yourself

Merchants frequently compare their rate with a figure heard from another business and conclude they are overpaying. The comparison is usually invalid, because rate depends on volume, average ticket, method mix, vertical risk, refund rate, settlement speed and contract length.

To benchmark honestly, compare only against merchants matching you on at least four of those seven dimensions — or, better, run a structured process. Ask three providers to quote against the same written volume profile: monthly settled value, method split, average ticket, refund rate, dispute rate, settlement cadence required and settlement currency.

Then normalise every quote to blended effective cost per ₹100 settled, including payout and conversion. Only at that point are the numbers comparable.

Keep the profile document. Re-running the same exercise every twelve months takes an afternoon and is the single most reliable way to keep pricing honest over time.

Practical fee optimisation levers

Ranked by typical impact for a Indian merchant:

1. Shift mix toward cheaper rails. Presenting IMPS prominently for large baskets and UPI for everyday tickets often saves more than any negotiated discount.
2. Raise authorisation rate. Every recovered failure is full-margin revenue; a few points of success rate outweigh basis points of pricing.
3. Reduce refunds. Fewer refunds means fewer retained fees, fewer refund fees and fewer disputes.
4. Right-size settlement frequency. Match payout batches to your actual cash needs rather than defaulting to daily.
5. Consolidate providers commercially, diversify them technically. Volume concentrated under one commercial agreement prices better, while routing across several underlying routes preserves resilience.
6. Renegotiate on evidence. Bring measured volume, mix and performance to a quarterly review.
7. Eliminate monthly minimums once volume comfortably clears them.

Recalculate blended effective cost after every change. Optimisations that are not measured tend to be reversed by drift within two quarters.

Contract clauses that protect your pricing

• Rate review trigger. Pricing is revisited when volume exceeds an agreed threshold for three consecutive months.
• Change notice period. No unilateral fee change without a defined written notice period and a right to terminate.
• Fee schedule as an annex. Every chargeable event listed in one document, incorporated into the contract.
• Reserve terms and review. Percentage, hold period and a measurable review condition.
• Settlement service level. Cadence, cut-off and remedy if missed repeatedly.
• Data portability. Right to export full transaction and settlement history in a machine-readable format, including after termination.
• Termination assistance. A defined wind-down period covering final settlement and reserve release.

The last two matter most at the point you want to leave, which is exactly when negotiating leverage is lowest. Agree them at the start.

Failure rate is a cost line, not a technical metric

A provider quoting a lower rate with a five percentage point worse authorisation rate is more expensive in every realistic model. If one hundred customers try to pay ₹1,000 and ninety-two succeed instead of ninety-seven, you have lost ₹5,000 of revenue to save a few basis points on ₹92,000 of settled value.

Measure success rate per method, per hour of day and per provider, not as a single monthly average. Failures in India cluster in predictable ways: wallet maintenance windows, bank downtime around end-of-month batch processing, and telecom-level issues affecting one-time password delivery. A platform that routes around these events — rather than reporting them after the fact — protects revenue in a way no discount can match.

The controls that matter most are automatic failover to an alternative provider or rail, idempotent retries that cannot double-charge, per-method health scoring, and a checkout that presents a working method rather than a failing default. These are described in more detail on the payment infrastructure page.

How to negotiate effectively

Negotiation works when you bring evidence. Prepare a one-page volume profile: last six months of settled value, method split, average ticket, refund rate, chargeback rate and projected growth. Providers price risk, and risk falls when your data is clean and your business is legible.

• Ask for pricing per method rather than a single blended number, so you can optimise checkout toward cheaper rails.
• Request a written review clause: if monthly volume exceeds an agreed threshold for three consecutive months, pricing is revisited.
• Negotiate payout frequency and reserve terms as hard as you negotiate the rate; both affect cash more than a small percentage change.
• Ask what happens during an incident: what is the failover path, who is on call, and what is the notification channel.
• Confirm the settlement currency and the exact conversion mechanism in writing.

Do not negotiate on rate alone. A provider that is ten basis points cheaper but settles a day later, holds a reserve, and lacks a second route for UPI is quietly more expensive.

Settlement, payouts and working capital

Settlement in India typically runs T+1 business day into an INR current account, subject to the underwriting profile of the merchant. The cadence you agree determines how much cash is permanently parked inside the payment system. A merchant processing ₹30 million a month on T+2 has roughly two days of revenue in transit at all times; moving to T+1 releases a day of working capital permanently.

Three questions decide the real cash profile:

• Cut-off times. A T+1 promise with a 14:00 cut-off means afternoon volume settles on day two.
• Weekend and holiday behaviour. Domestic rails in India do not clear on bank holidays; confirm how the calendar is handled.
• Reserves. A rolling reserve of five percent held for ninety days is a meaningful financing cost that never appears on a rate card.

For merchants collecting in several markets, the settlement design question widens: do you want four local accounts and four reconciliation processes, or one consolidated treasury view with per-market sub-ledgers? The second is materially easier to operate, and it is what cross-border payment solutions is built for.

Regulatory and compliance context

Payment acceptance in India is supervised by the Reserve Bank of India, and both local acquiring relationships and cross-border settlement are shaped by that supervision. Merchants do not need to become regulatory experts, but they do need to understand three practical consequences.

First, the entity that receives settlement matters. Locally registered entities generally access domestic rails and INR settlement directly; offshore entities usually work through a licensed local partner and settle cross-border. This affects timelines, documentation and cost, and it should be decided before integration rather than after.

Second, know-your-customer and anti-money-laundering obligations flow down to merchants. Expect to provide incorporation documents, beneficial ownership information, a description of the business model and evidence of the goods or services sold. Our approach is documented on the KYC and AML pages.

Third, restricted and prohibited categories are enforced at the acquiring level, not only in contracts. Merchants operating in sensitive verticals should disclose the model early — underwriting that starts with accurate information almost always ends better than underwriting that discovers the truth in transaction data. See compliance for how we structure that review.

Reconciliation: the cost nobody quotes

Reconciliation is where payment costs hide. Every unmatched transaction consumes finance time, and unmatched transactions accumulate quietly until a month-end close takes four days instead of four hours.

Good reconciliation depends on three properties. Identifiers must be consistent across the API response, the webhook payload and the settlement file. Settlement files must show gross value, fees, refunds and net value line by line rather than as monthly aggregates. And timing must be explicit, so a transaction authorised on the last day of the month and settled on the first day of the next can be matched without judgement calls.

A practical monthly close for a India merchant looks like this:

1. Pull settled transactions from the API for the period.
2. Pull the provider settlement statements for the same period.
3. Match on transaction identifier first, then on amount plus timestamp for the remainder.
4. Investigate anything unmatched after two passes, categorising it as timing, fee, refund or genuine break.
5. Post the net figures to the ledger with fees recorded separately from gross revenue.

Merchants who do this monthly find pricing errors. Merchants who do not, do not.

Common mistakes merchants make

Choosing on headline rate. The blended effective rate, including failures and payout costs, routinely differs from the quoted rate by fifty basis points or more.

Running a single provider. One provider means one outage equals zero revenue. Redundancy is cheaper than the downtime it prevents, especially in markets where a single wallet carries a large share of volume.

Treating webhooks as reliable. Networks fail. Without a status endpoint and a reconciliation job, lost webhooks become stuck orders and support tickets.

Ignoring refund and dispute mechanics until the first case. The first chargeback is the wrong time to discover the evidence requirements.

Underestimating onboarding. Documentation gaps are the most common cause of a delayed launch, not technical work.

Optimising checkout for the head office rather than the customer. In India, defaulting to cards when UPI carries most consumer volume is a direct conversion loss.

Skipping monthly reconciliation. Pricing errors and fee drift are invisible without it.

Provider evaluation checklist

Use this as a scorecard rather than a reading list. Score each item from zero to three and compare totals rather than impressions.

• Coverage of UPI apps, Paytm, PhonePe and IMPS, NEFT under one contract.
• Published authorisation rate per method, with historical data rather than a claim.
• Automatic failover between providers or rails, demonstrated in the sandbox.
• Settlement cadence, cut-off times and holiday behaviour in writing.
• Reserve policy stated explicitly, including release schedule.
• Full chargeable-event list, including payout, refund and dispute fees.
• Signed webhooks, idempotency and an authoritative status endpoint.
• Settlement statements at transaction level with fees itemised.
• Named support contact and a documented incident escalation path.
• Onboarding requirements and realistic go-live timeline.
• Clear statement of which entity contracts and which entity settles.
• Sandbox that simulates failure and timeout, not only success.

The metrics to run permanently

• Authorisation rate by method and hour. The earliest indicator of a degrading route.
• Blended effective cost. Recalculated monthly, not annually.
• Time to settle. Actual, measured, versus contractual.
• Reconciliation break rate. Unmatched transactions as a share of volume.
• Refund rate and refund latency. Both affect customer trust and support load.
• Dispute rate and win rate. Trend matters more than absolute level.
• Webhook delivery success and retry depth.
• Support contacts per thousand transactions. A direct proxy for checkout quality.

Put these on one dashboard reviewed weekly by someone who owns the number. Payment performance degrades gradually and is rarely announced; the merchants who notice first are the ones who measure continuously.

How PayEurasia approaches this

PayEurasia operates as a single integration across India and the wider South Asia region, with multiple underlying provider relationships per market rather than one. That structure produces three concrete benefits for the questions in this guide.

Routing and redundancy. Payments are scored and routed across available providers by health, success rate and limit headroom, with automatic failover when a route degrades. A single wallet outage does not stop collections.

One reconciliation surface. Every transaction, fee, refund and settlement line is exposed through the same API and the same reporting model, whether the money moved over UPI, IMPS or IMPS.

Transparent economics. Pricing is quoted per method, settlement cadence and cut-offs are documented, and merchants can see fees at transaction level rather than as a monthly deduction.

Merchants operating in more than one South Asian market get the additional benefit of consolidated treasury: local collections in INR and neighbouring currencies, reconciled centrally, settled on an agreed schedule. Start with merchant onboarding or review coverage on the country hub.

Frequently asked questions

What fees do payment gateways charge in India?

Expect a transaction percentage, often a fixed per-transaction fee, payout fees, currency conversion spread where you settle outside INR, refund and dispute charges, and sometimes a monthly platform fee or minimum. Ask for the full schedule of chargeable events in writing rather than a single rate.

Is the original processing fee returned when I refund a customer?

It depends on the provider and it is worth asking explicitly. Many retain the original fee and some add a separate refund charge. For a business with a meaningful refund rate this single clause can be worth more than a negotiated rate reduction.

How much does currency conversion cost?

Conversion is charged as a spread over a reference rate rather than as a line-item fee, which makes it easy to overlook. Ask for the reference rate source and the spread in basis points, then reconcile a monthly sample against published mid-market rates for the relevant timestamp.

Should I choose subscription pricing or pay-as-you-go?

Compare them against your worst month, not your best. Subscription plus a lower variable rate wins at consistent high volume; pay-as-you-go is safer for seasonal or early-stage businesses because there is no floor charge in a slow month.

How do I reduce payment fees in India?

In order of impact: shift mix toward cheaper rails such as IMPS for large baskets, raise authorisation rate, reduce refunds, right-size settlement frequency, consolidate volume commercially while keeping several routes technically, and renegotiate quarterly with measured data.

Are payment fees subject to tax?

Treatment depends on your contract structure and the jurisdictions of the contracting entities. Confirm with your tax adviser whether quoted fees are inclusive or exclusive of applicable indirect tax and whether withholding applies to cross-border payments, and insist that settlement statements itemise tax separately.

Related guides

• Payment gateway charges india
• Best payment gateway small business india
• Best payment gateway india
• Upi merchant payment guide
• Imps payment guide for merchants

Where to go next

• India payment coverage — Local methods, settlement and supported flows.
• Country hub — Coverage, local methods and settlement timelines per market.
• Solutions — Collections, payouts, wallet rails and bank rails in one platform.
• API overview — REST endpoints for payments, payouts, refunds and reporting.
• Developer docs — Authentication, idempotency, webhook signatures and the sandbox.
• Merchant onboarding — Documents, timelines and what underwriting reviews.
• Cross-border payments — Collect locally, reconcile centrally, settle once.