Save your workspace key — shown once.
KZAJ-FF9Z-SXHD-PSE5
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-015
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.
Scan with a payment app.
Parameters
pa
tr
LABAF46J4DRYSA0
am
2.00
cu
INR
Advanced details
upi://pay?pa=&tr=LABAF46J4DRYSA0&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
- LABAF46J4DRYSA0
- 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 same generated QR scanned from a second phone, to separate "this app rejects this payload" from "this phone has a problem".
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.
- Needs two devices, each recorded separately in the results matrix.
Prerequisites
- A saved UPI profile.
- A second device, or the same phone scanning a screen.
How the lab runs it
Same QR as QR-012; the result records a second device.