UPI Testing

PhonePe

PH-007 Not applicable here

PhonePe — Minimum amount

No mam set, so this is the same payload as the plain control.
Why
Profile P07 is defined by mam, and neither your UPI profile nor this run supplies one — so comparing P07 against P01 would be comparing a method against itself and reading the noise as a finding. Set mam 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.
You are on a desktop browser, which has no UPI app to open. The URI is still shown and can be copied.
What would unblock it
Open this page on the phone you want to test, or use a QR-scan method (QR group) which is designed for exactly this situation.
Test PH-007

Scan with the phone you want to test.

Advanced details
phonepe://pay?pa=&tr=LABMGSTYGJHMN5Z&am=2.00&cu=INR
Launch
app scheme
Scheme
intent:// (Android) · phonepe://pay (iOS)
Profile
P07 — P01 + mam
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. PhonePe publishes a merchant SDK/PG integration instead. (observed)
Reference
LABMGSTYGJHMN5Z
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

PhonePe 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.
  • 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.
  • On iOS: PhonePe installed and registered for phonepe://pay
  • On Android: PhonePe installed (com.phonepe.app).

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 com.phonepe.app, with no browser_fallback_url so a failure to open stays visible. iOS: the phonepe://pay scheme carrying the same query.