UPI Testing
Save your workspace key — shown once.

QC6E-Y4SA-Y8FZ-F833

Why it matters
It is the only way to reach these profiles and results from another device. The lab stores a hash of it, so nobody here can recover it for you.
QR-012 Not applicable here

Any UPI app with a scanner — With merchant category code

No mc set, so this is the same payload as the plain control.
Why
Profile P03 is defined by mc, and neither your UPI profile nor this run supplies one — so comparing P03 against P01 would be comparing a method against itself and reading the noise as a finding. Set mc on the profile first, or run P01 and know what you measured.
pa — A payment needs a payee address. Nothing can be launched without pa.
The active UPI profile has no payee address.
What would unblock it
Add or select a UPI profile first.
Test QR-012

Scan with a payment app.

Advanced details
upi://pay?pa=&tr=LAB55NEEZ0JXHXX&am=2.00&cu=INR
Launch
qr scan
Scheme
upi://pay (encoded in the QR)
Profile
P03 — P01 + mc
Platform
Android + iOS
Browser
The QR is rendered in this browser; the scan happens on a phone.
Docs
NPCI UPI Linking Specification; ISO/IEC 18004. (npci spec)
Reference
LAB55NEEZ0JXHXX
Registry
1.0.0

THE most important comparison in the catalogue. Several apps switch from a person-to-person flow to a merchant flow when mc appears — changing limits, fees and whether the amount can be edited. P01 against P03 on the same app, same destination, same minute is the controlled experiment that shows it.

Expected

The QR the lab generated from your parameters is scanned by a payment app, which opens on its payment screen.

Limitations

  • A scan is a DIFFERENT CODE PATH inside a payment app from a deep link. An app that accepts a parameter by scan may reject it by intent, and vice versa — that difference is the entire reason this group exists.

Prerequisites

  • A saved UPI profile.
  • A second device, or the same phone scanning a screen.

How the lab runs it

The URI from the selected profile is encoded as a QR and rendered on screen.