Save your workspace key — shown once.
WJH9-HP33-5N72-44CD
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.
PH-009
Needs your identifiers
PhonePe — 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.
Scan with the phone you want to test.
Parameters
pa
tr
LABA7WB41GENMNR
am
2.00
cu
INR
Advanced details
phonepe://pay?pa=&tr=LABA7WB41GENMNR&am=2.00&cu=INR
- Launch
- app scheme
- Scheme
- intent:// (Android) · phonepe://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
- No public third-party deep-link specification. PhonePe publishes a merchant SDK/PG integration instead. (observed)
- Reference
- LABA7WB41GENMNR
- 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
PhonePe 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.
- The iOS scheme used here is observed, not vendor-documented. A working result is evidence, not a supported integration.
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: PhonePe installed and registered for phonepe://pay
- On Android: PhonePe installed (com.phonepe.app).
Notes
- This scheme is observed, not vendor-documented. A result either way is evidence about today, not a supported integration.
How the lab runs it
Android: an intent:// URI naming com.phonepe.app, with no browser_fallback_url so a failure to open stays visible. iOS: the phonepe://pay scheme carrying the same query.