08GR-P9DV-8YJH-1SME
Why it matters
Amazon Pay — Minimum amount
Why
What would unblock it
Parameters
pa
tr
LAB24QT0S457329
am
2.00
cu
INR
Advanced details
- Launch
- Scheme
- intent:// (Android only)
- Profile
- P07 — P01 + mam
- Platform
- Android
- Browser
- Android: Chrome or any browser that follows intent: URIs. iOS: Safari, only where the app registers a scheme.
- Docs
- No public UPI deep-link scheme. Amazon Pay UPI lives inside the Amazon shopping app. (npci spec)
- Reference
- LAB24QT0S457329
- 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
Amazon Pay 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.
- Not runnable on iOS at all through this method.
Prerequisites
- A saved UPI profile with a payee address.
- On iOS: not addressable — Amazon Pay publishes no URI scheme the lab is willing to claim. Use the Generic UPI group (GN) on iPhone.
- On Android: Amazon Pay installed (in.amazon.mShop.android.shopping).
Notes
- Amazon Pay publishes no URI scheme the lab is willing to claim, so it cannot be addressed directly from a non-Android browser.
How the lab runs it
Android: an intent:// URI naming in.amazon.mShop.android.shopping, with no browser_fallback_url so a failure to open stays visible. iOS: not implemented, because no scheme exists to implement.