UPI Testing

Google Pay

GP-009 Needs your identifiers

Google Pay — Documented initiation metadata

No mode and orgid and sign set, so this is the same payload as the plain control.
Why
Profile P09 is defined by mode and orgid and sign, and neither your UPI profile nor this run supplies one — so comparing P09 against P01 would be comparing a method against itself and reading the noise as a finding. Set mode and orgid and sign 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.
Missing orgid — values a bank, PSP or acquirer issues and the lab must never invent.
What would unblock it
Needs an orgid your PSP issued you, and — to be a genuine signed intent — a sign they generated. The lab will not create either. Until you supply them this method cannot run, because sending a made-up orgid tests nothing that exists.
Test GP-009

Scan with the phone you want to test.

Advanced details
tez://upi/pay?pa=&tr=LABGEH2HRJ6JA1Q&am=2.00&cu=INR
Launch
app scheme
Scheme
intent:// (Android) · tez://upi/pay (iOS)
Profile
P09 — P01 + mode + orgid (+ sign when supplied)
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
LABGEH2HRJ6JA1Q
Registry
1.0.0

How an app treats a payload that declares an initiation mode and a signing organisation. Only meaningful with real values.

Expected

Google Pay opens on its payment confirmation screen showing the payee and ₹2.00. How an app treats a payload that declares an initiation mode and a signing organisation. Only meaningful with real values.

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.
  • Needs an orgid your PSP issued you, and — to be a genuine signed intent — a sign they generated. The lab will not create either. Until you supply them this method cannot run, because sending a made-up orgid tests nothing that exists.
  • 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.