A practical guide to market fit, local payment rails, recurring authorization, and the cross-border infrastructure behind a successful checkout

India has one of the world’s largest digital audiences - and a payment environment that can punish assumptions imported from the United States or Europe. A checkout that supports international cards may technically accept a payment from India, but that does not mean it fits how a typical Indian customer prefers to pay. The opportunity is not simply to display prices in rupees. It is to choose the right rail, authorization experience, commercial partner, and renewal architecture.

UPI deserves to be treated as a first-class option, not because cards are irrelevant, but because a card-only strategy can unnecessarily limit reach. Equally important: accepting a one-time UPI payment is not the same as making recurring UPI billing work for a foreign merchant. The distinction is where a large part of the engineering effort begins.

1. The scale of the market and what the numbers actually say

India’s Unified Payments Interface (UPI) handled 241.62 billion transactions worth approximately ₹314.23 lakh crore in FY2025-26, according to a government release drawing on NPCI data. The number of transactions was around five times the FY2021-22 level. By June 2026, roughly 554.9 million users had been onboarded to UPI.

Figure 1. UPI annual transaction volume, FY2021–22 to FY2025–26. Source: Ministry of Finance / NPCI data [source].

These figures tell us that UPI has achieved extraordinary breadth; they do not, by themselves, prove its conversion rate for an online subscription checkout. UPI transaction totals span different use cases, including transfers between individuals and payments to merchants. Comparing every UPI transaction with only credit-card purchase transactions would be an apples-to-oranges comparison. The relevant question for a seller is narrower: how much of its own target audience can pay successfully, and how readily, with each method?

That distinction matters. A foreign business does not need to replace cards completely. It should test whether adding UPI to a well-designed checkout increases payment completion among its intended Indian customers, without compromising subscription operations or compliance.

2. Why card-first checkouts create avoidable friction

A credit card is a convenient default for many American subscription products. In India, it is a less universal starting point. Credit cards depend on issuer underwriting and access to a line of credit. RBI directions require issuers to assess an applicant's credit risk with reference to their independent financial means. Cards in circulation are also not the same as distinct people who hold an active, usable card.

The problem is both availability and checkout readiness. RBI card-security rules require cards to be issued with domestic ATM and point-of-sale use enabled as the baseline, while cardholders can control online and international transaction settings. An Indian customer may have a card yet be unable to complete a cross-border, card-not-present transaction until they change issuer settings. That failure can look like an ordinary declined payment to the merchant.

Preference also matters, but it deserves more careful language than a national stereotype. UPI’s familiarity, immediate account-based payment experience, wide merchant acceptance, and lack of a revolving credit requirement can make it appealing to customers who have access to both methods. Rather than assume all Indian consumers dislike credit, businesses should measure customer preferences, available instruments, authorization success and payment-method selection in their own funnel.

Finally, payment behavior depends on context. An enterprise software buyer, a consumer news subscriber and a mobile-first video viewer may have very different card access, order values and tolerance for friction. The correct payment mix is a product decision informed by the segment, not a slogan that cards never work.

3. Pricing locally is a product decision, not an exchange-rate exercise

The market is connected, but willingness to pay varies widely. TRAI reports approximately 1.09 billion internet subscriptions as of March 2026. The FICCI-EY analysis estimates that Indian digital-subscription revenue grew 60% to ₹163 billion in calendar 2025, including video, audio and news. Within video, its estimates show 216 million paid subscriptions across 143 million households, many accessed through bundled offers.

Figure 2. Digital subscription revenues, calendar years 2022–25, across video, audio and news; not an average video subscription price. Source: FICCI–EY.

These numbers demonstrate growth and market diversity; they should not be used to infer that the average paid video subscription costs ₹63 a month. The ₹163 billion revenue total covers more than video, the 216 million count refers to video subscriptions, and bundles complicate the relationship between subscriptions and what end users pay directly. A headline blended “price” created by dividing those incompatible figures would be misleading.

For a foreign merchant, pricing solely in dollars may mean a foreign-currency card purchase, possible issuer conversion fees, and a price on the statement that differs from the amount shown at checkout. The exact cost depends on the card, issuer and transaction arrangement. Card restrictions can also affect payment success. INR pricing paired with a viable local collection flow can reduce those sources of customer friction, but the business still needs to account for local taxes, foreign exchange and settlement costs within its own economics.

The practical takeaway: build the Indian price from customer value, competition, tax treatment, and payment economics. Do not calculate it solely by multiplying a US list price by the spot exchange rate.

4. What UPI changes technically

UPI is an interoperable, real-time payment system operated by the National Payments Corporation of India (NPCI). A customer typically initiates or approves a payment in a UPI-enabled app linked to their bank account. The merchant and its payment partners receive a transaction result, while bank-account identifiers need not be entered on the merchant’s checkout page. It is more accurate to say the account credential is not exposed to the merchant than to say no credential or identifying information ever travels through the payment network.

A merchant can present an app-intent link on mobile or a QR-based flow on desktop; a collect flow may also be supported depending on the provider and use case. Availability, customer prompts, and conversion vary by product and UPI app. The only reliable way to pick the checkout UX is to test the actual payment paths, including app switches, slow callbacks, user cancellations and return-to-merchant behavior.

4.1  Merchant fees are changing

Historically, bank-account-funded UPI merchant transactions operated largely under a zero-MDR framework. A September 2026 announcement set out a 0.4% merchant discount rate (MDR) for eligible person-to-merchant (P2M) transactions above ₹2,000, capped at ₹300 for transactions of ₹75,000 or more. Person-to-person transfers, payments of ₹2,000 or less, and qualifying small-merchant transactions remain exempt; some sectors have lower or flat rates.

For subscription businesses, one-time checkout and recurring collection need to be distinguished. NPCI’s policy FAQ expressly states that automated recurring standing instructions (UPI AutoPay mandates), including OTT subscriptions, do not attract the prescribed MDR. This exemption concerns the network MDR; it should not be mistaken for a guarantee that gateways, aggregators, or cross-border providers will charge no processing, settlement, or foreign-exchange fees.

The announced rates were initially scheduled for October 15, 2026, but NPCI deferred the rollout until after Diwali. As of November 13, 2026, no replacement effective date had been confirmed. MDR is a merchant-acceptance cost, not an extra UPI checkout surcharge to the customer. Merchants should confirm the effective date, applicable transaction classifications including mandate renewals and their actual provider fee schedule and net settlement with the acquiring or aggregation partner. Broad claims that UPI is always free for merchants, or that the new 0.4% MDR already applies to all UPI payments, are misleading.

4.2  Recurring payments are an authorization lifecycle

For subscriptions, UPI AutoPay adds an electronic mandate. The customer authorizes its setup, and later debit attempts are made against that mandate subject to network, bank, regulatory and mandate-specific rules. The payment provider - not the merchant alone implements the network interactions; the merchant must still maintain the correct business state.

Figure 3. Conceptual recurring-billing lifecycle. Simplified for engineering discussion; actual provider and network states vary.

Under RBI’s Digital Payments – E-mandate Framework, 2026, recurring transactions up to ₹15,000 generally may proceed without additional authentication after mandate setup; higher authentication-free thresholds apply to specified categories such as insurance, mutual funds and credit-card bills. Issuers generally must send a pre-debit notification at least 24 hours before charging, subject to stated exceptions. This requires advance scheduling and coordination; it does not mean that every same-day debit is prohibited or that a merchant should blindly charge a day early.

The critical architecture distinction is that subscription state and mandate state are independent. A subscription may remain active in the product database after a customer pauses or revokes the payment mandate in their UPI app. A mandate may be valid when the renewal request is created but fail during execution. Every renewal needs its own attempt, result, retries and reconciliation against the authoritative provider events.

5. What foreign businesses must establish before launch

5.1  Define the seller and the collection chain

A foreign business has several possible entry models: an Indian entity collecting locally, an arrangement with an Indian payment aggregator and a compliant cross-border settlement path, or a merchant-of-record (MoR) service that contracts with the end customer as seller. These models differ materially in who sells the product, who owns tax and refunds, whose name appears on the customer’s statement, where funds settle, and who handles disputes.

Do not assume that registering a foreign merchant with a globally known processor automatically enables Indian UPI collection. Nor is a locally incorporated subsidiary the only theoretical route. RBI’s Payment Aggregator–Cross Border (PA-CB) framework regulates entities facilitating import and export payments. The actual permissible configuration depends on the authorized entities and their arrangements.

5.2  Verify the actual entity, direction and payment method

A processor’s brand name is less important than the regulated entity providing the service. Ask the provider for the legal entity name, its relevant RBI authorization, the cross-border direction in which the payment is classified, the bank/settlement chain and the specific supported merchant category. The “inward” and “outward” labels can be confusing if read from the foreign seller’s point of view: check the RBI definitions and the exact transaction flow rather than guessing from a label.

Licensing does not itself establish product availability. A provider may be authorized for cross-border collection yet offer UPI only to certain industries, currencies, checkout integrations or one-time transactions. Ask explicitly whether one-time UPI, mandate registration and renewal debits are enabled for a foreign-registered business in your category. Examples of published provider documentation for cross-border UPI mandates now exist, including PayU’s cross-border UPI consent flow and Paddle’s UPI AutoPay offering; eligibility and contracting still need confirmation.

5.3  Design for mandate events, not “charge customer” calls

For recurring billing, obtain the answers before integration: Does the provider offer mandate registration, cancellation, pause, and status queries? Who sends the pre-debit notice? What time windows and retry limits apply? Which transaction results are final, and which are pending? How do asynchronous provider webhooks map to subscription, invoice, and entitlement states? What recovery experience is available after mandate revocation?

Store mandates as separate records linked to subscriptions; make debit and webhook processing idempotent; reconcile transaction IDs with the provider; handle delayed and reversed results; and provide a card or alternative-method recovery path when AutoPay is unavailable. Do not mark an invoice paid merely because the mandate exists or the debit request was accepted.

5.4  Price in INR, settle taxes, then model net proceeds

Digital supplies to Indian consumers may create Indian GST obligations, including under rules for online information and database access or retrieval (OIDAR) services. The responsible party depends on the transaction and seller-of-record structure. Tax obligations do not vanish because the payment uses UPI or because a third party processes funds. Have an India-qualified tax adviser validate the specific service, customer types and contractual arrangements.

Your margin model should separately account for INR list price, applicable tax, provider and settlement fees, currency conversion, chargebacks or disputes where relevant, refunds and payment-recovery expenses. Even with a simple consumer-facing checkout, the underlying economics are not automatically simple.

6. A practical example: a US digital publisher enters India

Consider a digital publisher offering a US subscription at $12 per month. The first launch uses an international-card checkout with dollar pricing. A later, localized experiment offers ₹999 per month, displays the applicable tax treatment clearly, supports eligible local payment methods, and routes UPI through a provider that has confirmed this merchant’s contract and product eligibility.

The ₹999 figure is intentionally illustrative - not a foreign-exchange conversion, market benchmark, or actual business result. The real decision would require price research and controlled testing. The operational differences are more important than the numbers:

Decision

Card-first launch

Localized experiment

Pricing

USD price; issuer FX may affect statement amount

INR price; taxes and merchant FX/settlement modeled

First payment

International card and issuer controls

Cards plus approved UPI flow; app/QR UX tested

Recurring billing

Card credential/network token and card rules

UPI AutoPay only where contractually supported; mandate state tracked

Recovery

Card declines and payment-method updates

Revoked or failed mandates, fallback payments and explicit reauthorization

Success metric

Checkout starts and accepted card charges

Net paid conversion, first renewal, recovered revenue and support burden

What would prove the strategy works? Not UPI’s national market share. Measure paid checkout conversion by payment method, first-cycle authorization success, the proportion of customers able to register recurring mandates, renewal collection rate after 30 and 60 days, net realized revenue, refund/support cost, and payment-method fallback. Segment those metrics by app, device, acquisition channel, and price cohort.

7. A launch checklist for engineering and product leaders

  • Commercial eligibility: Confirm merchant-of-record, cross-border direction, regulated entity, merchant category, currency, fees, and settlement timeline in writing.
  • Checkout experience: Test one-time UPI intent/QR, customer navigation, bank/app failures, cancellations, timeout handling, and webhooks on actual devices.
  • Recurring eligibility: Verify AutoPay mandate creation and renewal for the exact merchant entity; do not extrapolate from a provider’s one-time UPI support.
  • Billing state: Model subscription, mandate, attempt, and invoice separately; add idempotency, reconciliation, backoff, and payment recovery.
  • Consumer protection: Ensure the provider handles required advance notices and mandate controls; present clear renewal terms and cancellation paths.
  • Measurement: Compare net paid conversion and renewals against a card-first control; never use total UPI volume as a proxy for your own checkout performance.

8. The short version

UPI is not a logo to add next to Visa and Mastercard. It changes the customer’s payment behavior, the merchant’s collection choices and, for recurring revenue, the authorization model itself. But the case for UPI should not be overstated: national transaction totals are not a merchant conversion study, not every foreign seller can activate every UPI product, and fee policy is evolving.

The right approach is to combine local pricing research, a compliant collection chain, carefully tested UPI and card experiences, and an architecture that treats mandates as live customer-controlled permissions. Real localization means adapting the payment architecture to the market - not merely translating the price into its currency.


Author’s note: Sources for the original article were checked on 19 October 2026. Inline source links and the merchant-fee section were reviewed and updated on 13 November 2026. Provider capabilities, fees, and regulations can change; confirm them again before launching. This article is business and engineering analysis, not legal or tax advice.