UPI for International Merchants: Collection, AutoPay, and Settlement

India's digital payment ecosystem is dominated by the Unified Payments Interface (UPI), developed by the National Payments Corporation of India (NPCI). For global e-commerce merchants, SaaS platforms, and digital service providers targeting Indian consumers, supporting UPI is no longer optional—it accounts for over 80% of consumer-to-merchant digital transactions in the country.

However, accepting UPI payments as an offshore entity presents distinct operational, technical, and regulatory challenges. International businesses must navigate cross-border payment aggregation regulations, foreign exchange conversion, and strict compliance frameworks established by the Reserve Bank of India (RBI). This guide breaks down the technical mechanisms of UPI collection, recurring AutoPay mandates, and cross-border settlement rails for global merchants.

UPI Collection Mechanics: Intent vs. Collect Flow

To accept one-time UPI payments, merchants typically implement one of two primary integration models: the Collect Request (collect flow) or the UPI Intent flow. In a collect flow, the user inputs their Virtual Payment Address (VPA, e.g., user@upi) on the merchant checkout page. The payment gateway triggers a push notification to the user's UPI app (such as Google Pay, PhonePe, or Paytm), where the user approves the payment by entering their 4- or 6-digit UPI PIN.

While collect flows were historically common, the UPI Intent flow has become the industry standard for mobile web and in-app checkout due to significantly higher conversion rates. With Intent, the merchant checkout automatically detects installed UPI apps on the user's mobile device and opens the chosen app directly via deep-linking, bypassing manual VPA entry. For desktop environments, dynamic QR codes serve a similar function, allowing users to scan and pay seamlessly. Gateways like Coingopay streamline these intent and dynamic QR integrations into unified SDKs for international merchants.

UPI AutoPay: Managing Recurring Subscriptions

For SaaS providers, streaming platforms, and subscription-based marketplaces, NPCI introduced UPI AutoPay to enable recurring debit mandates. UPI AutoPay allows customers to authorize recurring payments—such as weekly, monthly, or quarterly subscriptions—using their UPI app without requiring manual authentication for every billing cycle.

Under current RBI and NPCI guidelines, recurring payments up to INR 100,000 (~USD 1,200) per transaction can be executed automatically after the initial mandate setup, which requires a one-time UPI PIN authentication. Crucially, merchants must comply with mandatory pre-debit notifications: an automated SMS or push notification must be sent to the subscriber at least 24 hours prior to pulling funds. Managing these mandate state transitions—including registration, active status, pause, unpause, and revoke events—requires robust webhook infrastructure to prevent service disruption and involuntary churn.

Cross-Border Settlement Rails and Regulatory Compliance

International merchants selling to Indian consumers without a local Indian legal entity cannot receive direct local Indian Rupee (INR) settlements into domestic bank accounts. Instead, payments must flow through regulated Payment Aggregator - Cross Border (PA-CB) entities or authorized dealer (AD Category-I) banks operating under RBI guidelines.

In a typical cross-border UPI workflow, the local INR collected from the customer is converted into the merchant's settlement currency (such as USD, EUR, or SGD) at the prevailing FX rate. The funds are then repatriated via international wire transfers (SWIFT or local clearing systems) to the merchant's global bank account. Cross-border settlement cycles typically range from T+1 to T+3 business days. Merchants must ensure that their payment processing pipeline complies with RBI regulations regarding gross-to-net settlement reporting, purpose code tagging, and foreign exchange compliance.

Reconciliation, Refunds, and Dispute Management

Operational efficiency in high-volume UPI processing depends on automated reconciliation and robust status management. UPI transactions rely on asynchronous settlement architectures where payment confirmations occur via webhooks. Payment infrastructure must handle transient state conditions, such as pending or delayed responses from issuing banks, through automated polling mechanisms (Server-to-Server status checks) to ensure accurate order fulfillment.

Because UPI transactions are authenticated via a two-factor security model requiring the user's secret UPI PIN, standard chargebacks due to fraud claims are exceedingly rare compared to traditional credit card processing. However, refund management remains a critical operational workflow. International merchants must support programmatic partial and full refunds. Cross-border refunds involve reverse FX conversions, where the gateway deducts the equivalent foreign currency from the merchant's balance and credits INR back to the customer's original UPI account.

Strategic Implementation for Global Platforms

Expanding into the Indian market requires a payments infrastructure designed for local regulatory complexity and high-throughput processing. While direct integration with local Indian banks is technically impossible for non-resident entities, working with international payment infrastructure providers offers a streamlined pathway to enter the market.

By leveraging cross-border payment gateways like Coingopay, platforms can integrate UPI, UPI AutoPay, and local card schemes through a single API. This infrastructure abstracts away the complexities of local banking relationships, foreign currency repatriation, pre-debit mandate notifications, and tax compliance. Choosing an optimized UPI processing rail enables global merchants to capture India's rapid digital growth while maintaining unified global treasury operations.