UPI is a payment system, not a single app
The Unified Payments Interface is an instant payment system developed by the National Payments Corporation of India. Customers encounter it through participating banking and payment applications; BHIM is one such app, not another name for the entire network. For merchants, choosing a familiar app logo is therefore different from obtaining an acquiring relationship, a merchant identifier and a production checkout integration.
The operating question is how the customer’s authorised payment becomes a confirmed merchant receipt. Separate the payment system, customer application, acquiring bank and any gateway or service provider. Keep the approved seller identity visible throughout the journey. A consumer’s ability to use UPI does not establish that every domestic or overseas business is eligible to collect through the same arrangement.
Merchant onboarding and integration
NPCI’s merchant FAQ directs businesses to an acquiring bank and describes due diligence, merchant identifiers and the assignment of an appropriate merchant category code. Those controls remain relevant even when the customer experience is a simple QR scan. Use a merchant arrangement that accurately describes the products, expected volumes and sales channels, rather than presenting business revenue as unrelated personal transfers.
For a physical checkout, confirm whether the QR includes the order amount and reference or requires manual customer entry. For a mobile website, ask the provider which supported app hand-off is appropriate. Validate the current integration specification before implementation; older public examples of collect requests should not be assumed to represent every live checkout flow. Test the exact production journey across the supported devices and apps.
Know the funding source and applicable limits
UPI can support more than the familiar bank-account-funded purchase. NPCI separately documents eligible prepaid-wallet interoperability and RuPay credit-card payments to merchants. Funding-source support should therefore be confirmed with the acquirer rather than inferred from the presence of a UPI QR. A personal transfer and a merchant purchase may also be treated differently for permitted use and operational handling.
NPCI’s August 2025 circular expanded limits for specified categories of verified merchants while preserving banks’ discretion to apply lower internal limits. The practical conclusion is that one headline UPI ceiling cannot describe every checkout. Request the current category-specific, per-transaction and daily limits for the approved merchant configuration. Do not split a purchase to evade restrictions; provide an alternative supported method where the legitimate order exceeds the available limit.
International acceptance is selective
NPCI describes UPI Global Acceptance as QR-based payment at selected international merchant locations using eligible Indian bank accounts and supported applications. Customers need the relevant international functionality enabled and should review the foreign and rupee amounts, exchange rate and applicable fees. This is a defined acceptance route, not general permission for an overseas website to receive domestic Indian UPI collections.
An international merchant should ask who provides local acquiring, which customer banks and apps are enabled, and how the merchant receives settlement. Confirm whether the proposal covers in-person QR, ecommerce or another channel. A country-level launch announcement does not establish support for every merchant in that country. Document the entity and product approval before placing UPI branding in checkout or promising Indian customers that payment will work.
AutoPay is a separate mandate journey
UPI AutoPay provides recurring e-mandates rather than requiring a new ordinary purchase payment for each renewal. NPCI’s enhancement circular describes mandate lifecycle operations, including viewing, pausing, revoking and modifying mandates, with additional portability provisions. Merchants should implement the specific supported AutoPay product and provider requirements instead of treating a saved UPI address as permission to collect automatically.
Before enrolment, show the customer the amount or permitted limit, frequency and cancellation route. Store the mandate reference and status separately from the subscription record. Test a paused mandate, insufficient funds, an expired authorisation and a customer cancellation after a renewal is initiated. Obtain current rules for notifications, authentication and retries from the provider; historic launch thresholds are not a reliable specification for today’s service.
Confirmation, settlement and commercial terms
Build an authoritative transaction-status check into the order system. A customer screenshot or a sound from a device should not replace the provider’s confirmed record when the order is uncertain. Match the amount, merchant identity and reference, and make notification handling idempotent. If the customer retries after a timeout, check the first attempt before requesting or accepting another charge for the same purchase.
Ask the provider to distinguish payment confirmation, credit to any collection account and payout to the merchant’s operating bank account. Obtain a commercial schedule covering the actual funding sources and any gateway, platform, hardware or settlement services. Do not describe all commercial services as free merely because customers associate ordinary UPI payments with no charge. Compare the net amount received and the operational service supplied under the merchant contract.
Reversals, refunds and customer protection
The RBI’s failed-transaction framework distinguishes an account transfer with no beneficiary credit from a merchant payment whose confirmation was not received. For the latter domestic UPI scenario, it specifies automatic reversal within T+5 days and compensation for delay beyond that period. This framework concerns failed transactions; it is not a universal timetable for a merchant’s voluntary refund after a completed purchase.
Keep failed-payment reversal, duplicate-payment correction and purchase refund as separate support cases. Preserve the transaction reference, final status and customer communication, and use the provider’s refund process. Do not ask customers for their UPI PIN, one-time passwords or remote access to their phone to investigate a payment. Escalate unresolved discrepancies through the acquiring provider and relevant customer complaint channel, with a clear record of what has been verified.
What it means to Merchants
UPI can support a straightforward payment experience when merchant approval, funding source and checkout integration align. Verify category limits, distinguish domestic acceptance from selected international routes, and treat AutoPay as an explicitly authorised mandate product. Confirm payment status before fulfilment and separate failed-payment reversals from refunds and settlement. Commercial terms and FixPays availability require confirmation for the specific merchant, rather than assumptions based on the UPI brand.