WA-010
Needs your identifiers
WhatsApp Pay — Bank-issued merchant identifiers
No mid and msid and mtid set, so this is the same payload as the plain control.
Why
Profile P10 is defined by mid and msid and mtid, and neither your UPI profile nor this run supplies one — so comparing P10 against P01 would be comparing a method against itself and reading the noise as a finding. Set mid and msid and mtid 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.
Missing mid — values a bank, PSP or acquirer issues and the lab must never invent.
What would unblock it
Needs the merchant / store / terminal identifiers your acquirer actually assigned you. An invented mid is not a merchant identifier, it is a string, and a result against one would be meaningless.
Parameters
pa
tr
LABP1Q24R0CRYTT
am
2.00
cu
INR
Advanced details
- Launch
- Scheme
- intent:// (Android only)
- Profile
- P10 — P01 + mid + msid + mtid
- 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. WhatsApp's own wa.me links are messaging links, not payment intents. (npci spec)
- Reference
- LABP1Q24R0CRYTT
- Registry
- 1.0.0
Whether an acquirer-issued merchant triple changes the receiving experience.
Expected
WhatsApp Pay opens on its payment confirmation screen showing the payee and ₹2.00. Whether an acquirer-issued merchant triple changes the receiving experience.
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.
- Needs the merchant / store / terminal identifiers your acquirer actually assigned you. An invented mid is not a merchant identifier, it is a string, and a result against one would be meaningless.
- On iOS: not addressable — WhatsApp Pay publishes no URI scheme the lab is willing to claim. Use the Generic UPI group (GN) on iPhone.
- On Android: WhatsApp Pay installed (com.whatsapp).
Notes
- WhatsApp 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 com.whatsapp, with no browser_fallback_url so a failure to open stays visible. iOS: not implemented, because no scheme exists to implement.