UPI Testing

Amazon Pay

AZ-003 Android only

Amazon Pay — With merchant category code

No mc set, so this is the same payload as the plain control.
Why
Profile P03 is defined by mc, and neither your UPI profile nor this run supplies one — so comparing P03 against P01 would be comparing a method against itself and reading the noise as a finding. Set mc on the profile first, or run P01 and know what you measured.
pa — A payment needs a payee address. Nothing can be launched without pa.
Addressing one named app from a browser needs an Android intent URI, and you are not on Android. There is no iOS equivalent for this app.
What would unblock it
Open the lab on an Android phone, or use the Generic UPI (GN) group here.
Advanced details
Launch
Scheme
intent:// (Android only)
Profile
P03 — P01 + mc
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
LABP30PQXNGMQZE
Registry
1.0.0

THE most important comparison in the catalogue. Several apps switch from a person-to-person flow to a merchant flow when mc appears — changing limits, fees and whether the amount can be edited. P01 against P03 on the same app, same destination, same minute is the controlled experiment that shows it.

Expected

Amazon Pay opens on its payment confirmation screen showing the payee and ₹2.00. THE most important comparison in the catalogue. Several apps switch from a person-to-person flow to a merchant flow when mc appears — changing limits, fees and whether the amount can be edited. P01 against P03 on the same app, same destination, same minute is the controlled experiment that shows it.

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.