Payment Gateway in India: A Merchant Guide to UPI Acceptance

Choose an India payment gateway by confirming merchant eligibility, customer checkout flows, payment verification and the currencies reaching your bank.

This guide is for payment, product and finance leads at global gaming, content, subscription and digital-goods businesses. It focuses on accepting payments from Indian customers. Start with the legal entity and business model, then evaluate Unified Payments Interface (UPI) acceptance, device behaviour and the complete money flow.

Commercial disclosure: HaiPay publishes this guide. It combines public documentation with an original evaluation framework. The test matrix is a proposed acceptance protocol; it does not report completed payment tests. This is general information, not legal, tax or investment advice.

Start with merchant eligibility and the direction of trade

An Indian business selling abroad and an overseas business selling to Indian customers need different assessments. Describe your transaction before asking which gateway to use.

Prepare a one-page merchant profile:

• The legal entity selling the product and the country where it is incorporated.
• The website or app, what customers buy, and when you deliver it.
• Whether payments are individual purchases, renewals initiated by customers, or automatic recurring charges.
• Expected order amounts in Indian rupees (INR), volumes and refund patterns.
• The intended bank account and its currency.

The Reserve Bank of India (RBI) issued its payment aggregator directions in September 2025. These cover payment aggregator categories, including cross-border aggregation, authorisation and merchant due diligence. A reference to this framework does not establish a particular provider's authorisation.

Source: RBI, “Master Direction on Regulation of Payment Aggregator”, published 15 September 2025, accessed 7 September 2026; regulatory scope and merchant due diligence.

Ask the provider to identify the contracting entity and explain the permitted transaction flow in writing. For games or digital content, describe the actual product rather than relying on an industry label. A subscription business should confirm automatic charging separately from one-off UPI collection.

Use the international payment gateway guide for wider provider selection, then apply the India-specific checks below.

UPI, PhonePe and Paytm occupy different layers

UPI is the payment system. PhonePe and Paytm provide applications through which customers can use it. Their official UPI terms describe participation as third-party application providers (TPAPs), working through payment service provider (PSP) banks.

For merchant evaluation, separate the customer's app from the gateway's enabled payment route. A familiar app logo does not establish a separate wallet integration or prove compatibility with your checkout.

Source: PhonePe, “Terms of Use of PhonePe UPI”, and Paytm, “UPI Terms and Conditions”, accessed 7 September 2026; application and PSP roles.

India Payment Acceptance Layer Map

Read this map as a set of questions, not as a transaction sequence. The funding source belongs on the payer side of the payment.

Source: Original editorial evaluation map informed by the PhonePe and Paytm UPI terms above, merchant configuration documentation, and RBI's 2025 directions; accessed 7 September 2026. Requested evidence is not a claim that any merchant account has these capabilities.

UPI funding is not limited universally to money held in a bank deposit account. For example, Google Pay documents eligible RuPay credit card payments to merchants, with restrictions. That example establishes a funding possibility, not acceptance through every gateway.

Source: Google Pay Help, “Use your RuPay credit card on Google Pay”, accessed 7 September 2026; Google Pay's card-linked UPI use and restrictions.

Evaluate mobile handoff and desktop QR separately

In an intent flow, checkout hands the customer into a payment application. In a QR flow, the customer scans a quick response (QR) code. Treat mobile app, mobile browser and desktop journeys as separate test cases.

PayU's current integration guidance directs new merchants towards UPI Intent and QR. Its Collect notice gives 28 February 2026 as the deprecation date for manual UPI identifier entry, while listing specific exemptions. Those include certain iOS and cross-border use cases.

That notice is provider guidance. Obtain your provider's current written interpretation before relying on an exemption or choosing a Collect integration.

Source: PayU, “UPI Collect Disablement Information”, accessed 7 September 2026; migration guidance and scoped exemptions, not proof of another provider's support.

Mobile Intent vs Desktop QR Test Matrix

Use the following protocol with an approved test account. Record the device, operating system, browser, payer-app version and environment for every run.

Source: Original test protocol informed by PayU's flow guidance and the provider's end-to-end testing guide, accessed 7 September 2026. These are acceptance criteria, not measured compatibility results.

Repeat applicable cases with PhonePe, Paytm and another app relevant to your customers. Do not mark a cell successful merely because a payment link opened.

The testing guide describes changing order status and sending notifications through a test environment. Such simulation helps exercise application logic. It does not demonstrate a real bank debit, payer-app handoff or successful UPI transaction.

Keep global cards separate from India-local acquiring

If cards are part of your checkout, assess them as a separate product scope. Card acquiring means the merchant-side arrangement for accepting and processing card transactions. Confirm the acquiring location, merchant entity and contract before calling it local.

The public pricing matrix lists UPI under India local methods and also displays Visa and Mastercard. This does not establish India-local card acquiring. The India collection documentation reviewed for this guide lists UPI routes.

Source: HaiPay, “Payment Gateway Pricing”, and “India” API documentation, accessed 7 September 2026; public listings and documentation scope.

For this evaluation, the local-payment route under discussion is UPI. Global card acceptance needs its own eligibility, currency, authentication and commercial review. A business requiring India-local card acquiring should obtain an explicit answer before shortlisting the arrangement.

Map INR checkout, USD routes and bank receipt

A route name containing US dollars (USD) is not a complete explanation of the money flow. The India documentation lists an INR UPI route and a USD-labelled route, IN_UPI_USD. Confirm what each currency means for your account.

The generic USD-wrapping guide contains conflicting descriptions of what the payer sees. Its reference region table also omits India. These public materials cannot establish the complete India currency flow.

Source: “India” and “USD Wrapping”, accessed 7 September 2026; route labels and an unresolved documentation conflict.

Have finance and engineering complete this worksheet together:

Source: Original currency-verification worksheet prompted by the documentation conflict above; no exchange rate, currency outcome or payout availability is assumed.

For example, a USD-labelled order alone cannot answer whether the shopper sees rupees, whether conversion occurs, or whether the bank receives USD. Match records from the same payment. If conversion applies, request the currency pair, direction, rate timestamp, rate source, markup and fee basis.

Do not configure transaction limits from a single public table. The India page and global collection list disagree on the INR minimum. The merchant-configuration reference describes effective limits derived from both method and application constraints.

Source: “India”, “Collection Payment Methods List”, and “Get Merchant Payment Config”, accessed 7 September 2026; conflicting public limits and the documented configuration model.

Compare the complete UPI quote

Request a written India quote before comparing cost. The public pricing page distinguishes card processing from local-method pricing and qualifies charges by commercial scope. A global starting price is not an India UPI rate.

Source: HaiPay, “Payment Gateway Pricing”, accessed 7 September 2026; pricing structure and signed-agreement qualifiers.

Use the same order profile for each provider:

This is a comparison worksheet. Its rows are questions, not a statement that every listed charge applies.

For small digital purchases, a fixed fee can materially change the economics. As an arithmetic illustration, a hypothetical ₹2 fixed fee equals 10% of a ₹20 purchase and 1% of a ₹200 purchase. This is not a provider quote.

Compare costs on the same basket of orders and in a common currency. Include conversion only when the actual flow requires it. Do not infer free merchant processing from the customer-facing UPI experience.

Confirm payments before delivering digital goods

A customer return page is insufficient evidence for delivering an item or activating an entitlement. Design fulfilment around authenticated server evidence and a verified order state.

The India reference directs merchants to query an order after asynchronous notification for the relevant non-bank-transfer flow. The Common API reference describes signed callbacks and order identifiers. These are documented controls, not proof that a particular integration implements them correctly.

Source: “India” and “Common API”, accessed 7 September 2026; query confirmation and callback verification.

Use this proposed acceptance sequence:

1. Create an order with a unique merchant reference.
2. Associate the provider reference with that order.
3. Validate server notifications using the current approved signature procedure.
4. Query and reconcile the order when the integration contract requires it.
5. Match the successful payment to the intended order, amount and currency before fulfilment.
6. Make fulfilment idempotent: processing the same payment again must not deliver the item twice.
7. Keep unresolved cases in a reviewable state with a defined customer-support path.

For a game-item purchase, test a notification arriving after the player closes checkout. Then replay the test event. The acceptance criterion is one entitlement, with an audit record explaining the payment state. This is a proposed scenario, not a reported customer result.

Finance should be able to connect the order, payment, deductions and bank receipt. Reconciliation means matching those records. Ask for a redacted sample using stable identifiers, including an unsuccessful or delayed case as well as a successful one.

Distinguish customer confirmation from settlement

Use a separate timeline for the customer payment and the merchant's access to funds.

The table is a recordkeeping model. Your contract determines which stages apply and their timing.

Ask whether the quoted period uses calendar days or working days, what event starts it, and what happens around holidays. Request payout frequency and receiving-bank transit assumptions separately. Avoid turning a successful consumer payment into a promise about merchant bank receipt.

RBI's payment aggregator directions distinguish aggregation from subsequent settlement to merchants. The public pricing page also makes commercial terms subject to the signed agreement.

Source: RBI's 2025 payment aggregator directions and current pricing, accessed 7 September 2026; settlement role and commercial qualification. No India settlement duration is asserted here.

Where HaiPay may fit, and what would rule it out

The public India UPI listing provides a starting point for a scoped conversation. Review the local-payment product and APAC coverage, then request account-specific confirmation.

A potential fit is a business seeking individual UPI collections that can obtain written eligibility, a clear currency map and verified operating evidence. Treat these as prerequisites to establish, not capabilities already proved for your business.

Pause the evaluation if your requirement is:

• India-local card acquiring without a separately confirmed arrangement.
• Automatic subscription charging inferred solely from UPI collection.
• Guaranteed support for every payer app or funding source.
• A particular INR limit or USD bank payout inferred from a route label.
• A launch date before payment confirmation and reconciliation have been tested.

Send the merchant profile, device priorities and currency worksheet with your India capability and quote request. Ask for a response covering eligibility, enabled collection route, effective limits, fees, currencies, supported flows and the evidence needed for launch.

Assign one owner from product, engineering and finance to review that response. Proceed only when each can connect the commercial answer to the configuration and observed payment records.

Sources

1. Reserve Bank of India. Master Direction on Regulation of Payment Aggregator. Published 15 September 2025; accessed 7 September 2026. Supports aggregation categories, merchant due diligence and settlement roles.
2. PhonePe. Terms of Use of PhonePe UPI. Accessed 7 September 2026. Supports UPI application and PSP roles.
3. Paytm. UPI Terms and Conditions. Accessed 7 September 2026. Supports TPAP participation and application scope.
4. Google Pay Help. Use your RuPay credit card on Google Pay. Accessed 7 September 2026. Supports a restricted credit-card funding example.
5. PayU. UPI Collect Disablement Information. Accessed 7 September 2026. Supports provider migration guidance and specific exemptions.
6. HaiPay Docs. India. Accessed 7 September 2026. Supports documented UPI route labels and query guidance, subject to unresolved documentation conflicts.
7. HaiPay Docs. Collection Payment Methods List. Accessed 7 September 2026. Supports the public INR minimum conflict.
8. HaiPay Docs. Get Merchant Payment Config. Accessed 7 September 2026. Supports the application-specific configuration and limit model.
9. HaiPay Docs. USD Wrapping. Accessed 7 September 2026. Supports the identified currency-description conflict; does not establish India bank payout.
10. HaiPay Docs. Common API. Accessed 7 September 2026. Supports signed callback and order-reference concepts.
11. HaiPay Docs. End-to-End Testing Guide. Accessed 7 September 2026. Supports test-environment status and notification simulation.
12. HaiPay. Payment Gateway Pricing. Accessed 7 September 2026. Supports public market listings and commercial qualifiers, not an India UPI quote.