UPI Testing
Save your workspace key — shown once.

05Z7-VT89-N6A6-8QR0

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-014 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.
Test GN-014

Scan with the phone you want to test.

Advanced details
upi://pay?pa=&tr=LAB4W0BK4H23GQK&am=2.00&cu=INR
Launch
dispatch gn 014
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
LAB4W0BK4H23GQK
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

Some in-app browsers handle this differently from an anchor. Still inside a user gesture, so it should be allowed.

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

Script sets window.location.href to the UPI URI inside the tap handler.