RNH5-2CSB-V8QD-9VN2
Why it matters
Paytm — Minimum amount
Why
What would unblock it
Scan with the phone you want to test.
Parameters
pa
tr
LAB1ZN0M5N486C5
am
2.00
cu
INR
Advanced details
- Launch
- app scheme
- Scheme
- intent:// (Android) · paytmmp://pay (iOS)
- Profile
- P07 — P01 + mam
- 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. Paytm publishes a merchant payment gateway with issued credentials. (observed)
- Reference
- LAB1ZN0M5N486C5
- Registry
- 1.0.0
mam constrains an amount the payer may edit. Beside a fixed am it is contradictory, and WHICH ONE each app honours is the finding. The lab warns about the contradiction and sends it anyway — that is the experiment.
Expected
Paytm opens on its payment confirmation screen showing the payee and ₹2.00. mam constrains an amount the payer may edit. Beside a fixed am it is contradictory, and WHICH ONE each app honours is the finding. The lab warns about the contradiction and sends it anyway — that is the experiment.
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: Paytm installed and registered for paytmmp://pay
- On Android: Paytm installed (net.one97.paytm).
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 net.one97.paytm, with no browser_fallback_url so a failure to open stays visible. iOS: the paytmmp://pay scheme carrying the same query.