Save your workspace key — shown once.
CVQJ-1KR4-582K-TPHX
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.
CR-012
Needs an import
CRED — Imported exact payment URI
This profile replays an original payload byte-for-byte, and this UPI profile has none.
What would unblock it
Paste an original payment URI into this profile first (QR Decoder → Save as exact original).
Advanced details
- Launch
- exact replay
- Scheme
- intent:// (Android only)
- Profile
- P12 — The imported URI, byte-for-byte
- Platform
- Android
- Browser
- Android: Chrome or any browser that follows intent: URIs. iOS: Safari, only where the app registers a scheme.
- Docs
- No public UPI deep-link specification. (npci spec)
- Reference
- —
- Registry
- 1.0.0
The same ground truth for an intent you were given as a link rather than a QR.
Expected
CRED opens on its payment confirmation screen showing the payee and ₹2.00. The same ground truth for an intent you were given as a link rather than a QR.
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.
- Replays imported bytes. The parameters shown are whatever the original payload contained, not the lab's.
Prerequisites
- A saved UPI profile with a payee address.
- Paste an original payment URI into this profile first (QR Decoder → Save as exact original).
- On iOS: not addressable — CRED publishes no URI scheme the lab is willing to claim. Use the Generic UPI group (GN) on iPhone.
- On Android: CRED installed (com.dreamplug.androidapp).
Notes
- No imported payload is attached to this profile.
How the lab runs it
Android: an intent:// URI naming com.dreamplug.androidapp, with no browser_fallback_url so a failure to open stays visible. iOS: not implemented, because no scheme exists to implement.