UPI QR vs EMVCo QR: How They Differ
Compare India UPI QR workflows with EMVCo merchant-presented mode payloads, including when each format applies and how merchants should choose.
Why this comparison matters
In India, consumers often scan UPI QR codes through banking and wallet apps. Globally, many markets use EMVCo Merchant-Presented Mode (MPM) as the shared QR payment grammar. Merchants, product teams, and developers need to know which format they are generating and which apps will accept it.
What EMVCo MPM standardizes
EMVCo MPM defines a Tag-Length-Value (TLV) payload with mandatory fields such as payload format indicator, point of initiation method, merchant account information, merchant name/city, country code, and CRC-16. Currency uses ISO 4217 numeric codes in Tag 53. Amount appears in Tag 54 when the payment is dynamic.
What UPI QR typically carries
UPI QR commonly encodes a payment address (VPA), payee name, and optional amount or transaction note in a UPI intent-style URI. Consumer apps resolve the VPA through the UPI ecosystem rather than through a generic EMVCo merchant account template. Many Indian acceptance products also support Bharat QR / EMVCo-compatible formats for broader interoperability.
Key practical differences
UPI QR is optimized for India's UPI rails and VPA addressing. EMVCo MPM is designed as a cross-market payload grammar that national schemes can extend. A wallet that only understands UPI intent strings may not parse a full EMVCo TLV string, and vice versa, unless the app explicitly supports both.
When merchants should use which
If your acceptance is India-only UPI, generate the format your acquirer documents. If you need multi-scheme or cross-border readiness, prefer an EMVCo MPM payload that includes the correct local merchant account template. Always validate CRC and test with the actual consumer apps your customers use.