UPI Testing
Save your workspace key — shown once.

E65M-1F4F-NFPJ-MEQ1

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.

Google Pay

GP-003 Not applicable here

Google Pay — 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.
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 GP-003

Scan with the phone you want to test.

Advanced details
tez://upi/pay?pa=&tr=LABKBYYEX0WTKDN&am=2.00&cu=INR
Launch
app scheme
Scheme
intent:// (Android) · tez://upi/pay (iOS)
Profile
P03 — P01 + mc
Platform
Android + iOS
Browser
Android: Chrome or any browser that follows intent: URIs. iOS: Safari, only where the app registers a scheme.
Docs
Google Pay for India developer documentation — UPI deep link / Tez scheme. (vendor documented)
Reference
LABKBYYEX0WTKDN
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

Google Pay opens on its payment confirmation screen showing the payee and ₹2.00. 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.

Limitations

  • A browser cannot tell you whether an app is installed. "App did not open" and "app is not installed" look identical from here; AN-004 in the Android harness is what separates them.

Prerequisites

  • A saved UPI profile with a payee address.
  • On iOS: Google Pay installed and registered for tez://upi/pay
  • On Android: Google Pay installed (com.google.android.apps.nbu.paisa.user).

How the lab runs it

Android: an intent:// URI naming com.google.android.apps.nbu.paisa.user, with no browser_fallback_url so a failure to open stays visible. iOS: the tez://upi/pay scheme carrying the same query.