PH-014
Not applicable here
PhonePe — Standard merchant intent
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
LABEXDY31GRDFFD
am
2.00
cu
INR
Advanced details
phonepe://pay?pa=&tr=LABEXDY31GRDFFD&am=2.00&cu=INR
- Launch
- app scheme
- Scheme
- phonepe://pay
- Profile
- P01 — pa + pn + tr + am + cu
- Platform
- Android + iOS
- Browser
- iOS Safari primarily; also resolvable on Android.
- Docs
- No public PhonePe specification for third-party deep links. The scheme is observed in the wild. (observed)
- Reference
- LABEXDY31GRDFFD
- Registry
- 1.0.0
The control. Every other profile is this one plus something, so a failure here is a failure of the destination or the app, never of an optional field.
Expected
PhonePe opens directly if it registers the scheme. A failure here is the EXPECTED outcome if PhonePe does not expose it — and that negative is worth recording, because it is the answer to "can we deep-link PhonePe on iPhone".
Limitations
- UNDOCUMENTED. A working result must not be treated as a supported integration; PhonePe can remove it at any time.
- PhonePe's supported path for merchants is their SDK / payment gateway, which is not a deep link and is out of scope for this lab.
Prerequisites
- PhonePe installed.
Notes
- Undocumented scheme. Failure is a perfectly ordinary outcome and is worth recording.
How the lab runs it
An anchor whose href is phonepe://pay?… built from profile P01.