IO-002
Needs the native harness
Companion iOS harness — Standard merchant intent
pa — A payment needs a payee address. Nothing can be launched without pa.
This measures something a browser cannot observe — installed apps, an activity result, an app version. It needs the companion harness.
What would unblock it
The harness is specified in docs/NATIVE_HARNESS.md and has not been built. Until it exists this slot is planned, not runnable.
Parameters
pa
tr
LABYKRHKY6GSQB7
am
2.00
cu
INR
Advanced details
- Launch
- Scheme
- upi:// and app-specific schemes
- Profile
- P01 — pa + pn + tr + am + cu
- Platform
- Ios
- Browser
- None — this is not a browser method.
- Docs
- Apple UIApplication and Universal Links documentation. (vendor documented)
- Reference
- LABYKRHKY6GSQB7
- Registry
- 1.0.0
The control. Every other profile is this one plus something, so a failure here is a failure of the destination or the app, never of an optional field.
Expected
Which of the app-specific schemes resolve on this device. iOS allows at most 50 declared query schemes, so a harness must choose which to ask about.
Limitations
- NOT RUNNABLE FROM A BROWSER, AND THE HARNESS DOES NOT EXIST YET. Counted in the planned 166 and excluded from the runnable count.
- iOS restricts scheme queries far more tightly than Android; several questions that are answerable on Android are not answerable at all here.
Prerequisites
- The companion iOS harness, which is SPECIFIED BUT NOT YET BUILT (docs/NATIVE_HARNESS.md).
- A physical iPhone with the payment apps installed.
- An Apple developer account to sideload it.
Notes
- This method has no browser launch mechanism.
How the lab runs it
Specified in docs/NATIVE_HARNESS.md.