Save your workspace key — shown once.
EK90-BP3F-JK8G-CDGT
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.
GN-015
Not applicable here
Any installed UPI app — Standard merchant intent
pa — A payment needs a payee address. Nothing can be launched without pa.
You are on a desktop browser, which has no UPI app to open. The URI is still shown and can be copied.
What would unblock it
Open this page on the phone you want to test, or use a QR-scan method (QR group) which is designed for exactly this situation.
Scan with the phone you want to test.
Parameters
pa
tr
LABYS6DZSDQ8S8X
am
2.00
cu
INR
Advanced details
upi://pay?pa=&tr=LABYS6DZSDQ8S8X&am=2.00&cu=INR
- Launch
- dispatch gn 015
- Scheme
- upi://pay
- Profile
- P01 — pa + pn + tr + am + cu
- Platform
- Android + iOS
- Browser
- Differs by technique — that is the point of the method.
- Docs
- Browser behaviour, not a UPI specification. See each browser's external-protocol handling. (undocumented)
- Reference
- LABYS6DZSDQ8S8X
- Registry
- 1.0.0
The control. Every other profile is this one plus something, so a failure here is a failure of the destination or the app, never of an optional field.
Expected
A legacy technique. Modern browsers block custom-scheme navigation from a non-top-level frame, so FAILURE IS THE EXPECTED RESULT — this method exists to prove the block, because integrations still ship it.
Limitations
- Holds the URI constant and changes only the dispatch, so a difference between GN-013 and this method is a BROWSER difference and never a UPI one.
Prerequisites
- A saved UPI profile.
How the lab runs it
The URI is assigned to the src of an off-screen iframe.