UPI Testing
Save your workspace key — shown once.

ZGAM-2E6H-QXSA-85G3

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.
QR-011 Needs an import

(no app — decoding only) — Imported exact QR

This profile replays an original payload byte-for-byte, and this UPI profile has none.
What would unblock it
Import a QR into this profile first (QR Decoder → Save as exact original).
Advanced details
Launch
exact replay
Scheme
(none)
Profile
P11 — The imported QR payload, byte-for-byte
Platform
Android + iOS
Browser
Any modern browser.
Docs
EMVCo merchant QR specification; NPCI UPI Linking Specification; ISO/IEC 18004 (QR). (npci spec)
Reference
—
Registry
1.0.0

The ground truth. Your bank's own placard, unmodified, against each app — the baseline every edited copy is compared to.

Expected

A payload carrying sign/orgid is identified as signed, and every field whose edit would invalidate the signature is locked in the editable copy.

Limitations

  • Decode-only. No app opens and no money can move, so this method is safe to run as often as you like.
  • The lab cannot verify a signature — only the issuing PSP holds the key. It reports presence and the consequences of editing, never validity.

Prerequisites

  • Something to decode.

Notes

  • No imported payload is attached to this profile.

How the lab runs it

Signature detection plus the edit-impact analysis in SignatureImpact.