UPI Testing

Google Pay

GP-016 Needs credentials

Google 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.
This is a vendor web integration behind merchant onboarding.
What would unblock it
A merchant identifier issued by the vendor and a supported gateway. The lab will not fabricate either.
Advanced details
Launch
Scheme
(none — JavaScript API)
Profile
P10 — P01 + mid + msid + mtid
Platform
Android + iOS
Browser
A browser supporting the Google Pay JavaScript API.
Docs
Google Pay API for Web — requires a Google Pay merchant profile and a supported payment gateway. (vendor documented)
Reference
LABJNSH5YAKRNH2
Registry
1.0.0

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

Expected

A Google Pay sheet inside the page, with no app switch. This is a genuinely different integration from every other method here — it is listed so the catalogue is honest about what exists, not because the lab can run it today.

Limitations

  • NOT IMPLEMENTED AND NOT RUNNABLE. It needs merchant onboarding the lab has no part in.
  • Counted in the planned 166 and excluded from the runnable count.

Prerequisites

  • A Google Pay merchant identifier issued to you by Google.
  • A supported payment gateway with its own credentials.
  • The lab will not fabricate any of these, so this slot stays unavailable until they exist.

Notes

  • This method has no browser launch mechanism.

How the lab runs it

Not implemented.