Save your workspace key — shown once.
6D4C-93VN-KXH0-5NBG
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-013
Needs an import
Any UPI app with a scanner — With merchant category code
This profile replays an original payload byte-for-byte, and this UPI profile has none.
Advanced details
- Launch
- exact replay
- 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
- —
- 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 lab re-renders your imported payload byte-for-byte as a QR. Scanning it should be indistinguishable from scanning the original placard — if it is not, the difference is in the image, not the data.
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.
- Requires an imported payload.
Prerequisites
- A saved UPI profile.
- A second device, or the same phone scanning a screen.
Notes
- No imported payload is attached to this profile.
How the lab runs it
The stored original bytes are re-encoded as a QR with no rebuild.