Save your workspace key — shown once.
G2G9-7GWB-9NFT-S52M
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.
PT-014
Not applicable here
Paytm — 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
LABVVSPMKGY98SS
am
2.00
cu
INR
Advanced details
paytmmp://pay?pa=&tr=LABVVSPMKGY98SS&am=2.00&cu=INR
- Launch
- app scheme
- Scheme
- paytmmp://pay
- Profile
- P01 — pa + pn + tr + am + cu
- Platform
- Android + iOS
- Browser
- iOS Safari primarily; also resolvable on Android.
- Docs
- No public Paytm specification for third-party deep links. The scheme is observed in the wild. (observed)
- Reference
- LABVVSPMKGY98SS
- 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
Paytm opens directly if it registers the scheme.
Limitations
- UNDOCUMENTED. Paytm's supported merchant path is their payment gateway with an issued merchant ID — a different integration entirely, and one the lab deliberately does not pretend to implement.
Prerequisites
- Paytm installed.
Notes
- Undocumented scheme. Failure is a perfectly ordinary outcome and is worth recording.
How the lab runs it
An anchor whose href is paytmmp://pay?… built from profile P01.