H00Q-ABTJ-8N5H-NBJ0
Why it matters
BHIM — With merchant category code
Why
What would unblock it
Parameters
pa
tr
LAB1S1Z5D2RPEWS
am
2.00
cu
INR
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
- NPCI UPI Linking Specification — BHIM is the reference implementation of the generic upi:// handling. (npci spec)
- Reference
- LAB1S1Z5D2RPEWS
- 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
BHIM 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 — BHIM publishes no URI scheme the lab is willing to claim. Use the Generic UPI group (GN) on iPhone.
- On Android: BHIM installed (in.org.npci.upiapp).
Notes
- BHIM 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.org.npci.upiapp, with no browser_fallback_url so a failure to open stays visible. iOS: not implemented, because no scheme exists to implement.