Save your workspace key — shown once.
WAJ8-JHWS-QFEM-YQEX
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-004
Not applicable here
PhonePe — Category code and note
No mc and tn set, so this is the same payload as the plain control.
Why
Profile P04 is defined by mc and tn, and neither your UPI profile nor this run supplies one — so comparing P04 against P01 would be comparing a method against itself and reading the noise as a finding. Set mc and tn 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.
Scan with the phone you want to test.
Parameters
pa
tr
LABSJE40MXX87FG
am
2.00
cu
INR
Advanced details
phonepe://pay?pa=&tr=LABSJE40MXX87FG&am=2.00&cu=INR
- Launch
- app scheme
- Scheme
- intent:// (Android) · phonepe://pay (iOS)
- Profile
- P04 — P01 + mc + tn
- 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
- LABSJE40MXX87FG
- Registry
- 1.0.0
Whether the note survives the merchant flow. Some apps that show a note in a P2P flow drop it in a merchant one.
Expected
PhonePe opens on its payment confirmation screen showing the payee and ₹2.00. Whether the note survives the merchant flow. Some apps that show a note in a P2P flow drop it in a merchant one.
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.
- 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.