UPI Testing
Save your workspace key — shown once.

57SY-7EBX-RHQ6-TBJ9

Why it matters
It is the only way to reach these profiles and results from another device. The lab stores a hash of it, so nobody here can recover it for you.

Paytm

PT-010 Needs your identifiers

Paytm — 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.
Test PT-010

Scan with the phone you want to test.

Advanced details
paytmmp://pay?pa=&tr=LABKZ1W4EHRS0DZ&am=2.00&cu=INR
Launch
app scheme
Scheme
intent:// (Android) · paytmmp://pay (iOS)
Profile
P10 — P01 + mid + msid + mtid
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
LABKZ1W4EHRS0DZ
Registry
1.0.0

Whether an acquirer-issued merchant triple changes the receiving experience.

Expected

Paytm 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.
  • 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.
  • 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: 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.