PH-012
Needs an import
PhonePe — Imported exact payment URI
This profile replays an original payload byte-for-byte, and this UPI profile has none.
What would unblock it
Paste an original payment URI into this profile first (QR Decoder → Save as exact original).
Advanced details
- Launch
- exact replay
- Scheme
- intent:// (Android) · phonepe://pay (iOS)
- Profile
- P12 — The imported URI, byte-for-byte
- 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
- —
- Registry
- 1.0.0
The same ground truth for an intent you were given as a link rather than a QR.
Expected
PhonePe opens on its payment confirmation screen showing the payee and ₹2.00. The same ground truth for an intent you were given as a link rather than a QR.
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.
- Replays imported bytes. The parameters shown are whatever the original payload contained, not the lab's.
Prerequisites
- A saved UPI profile with a payee address.
- Paste an original payment URI into this profile first (QR Decoder → Save as exact original).
- On iOS: PhonePe installed and registered for phonepe://pay
- On Android: PhonePe installed (com.phonepe.app).
Notes
- No imported payload is attached to this profile.
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.