Basic information: The issuer has implemented the feature to active Apple Card via URL Verification. The feature implemented by issuer is supported both in the APP and Clips. When Apple queries the activation method from UnionPay, UnionPay returns the "URL" activation method to Apple. Additionally, the apple-app-site-association file has been correctly deployed, and the configuration for Universal Links has been completed. Both the APP and Clips have undergone testing for Universal Link calls.
The desired experiece is that when the APP is installed, Apple Wallet launches the APP, and the user completes the activation within the APP, and if the APP is not installed, Apple Wallet calls Clips, and the user completes the activation in Clips.
Problem description: Under iOS 17 and iOS 18, when triggering Apple Pay card activation, the APP or Clips can be called as expected, and the activation can be completed well. However, Under iOS 26, regardless of whether the APP is installed, under the same circumstances, an internal browser within Apple Wallet opens to access the H5 page corresponding to the URL, instead of redirecting to the APP or Clips. Please assist in confirming whether this is a new feature of iOS 26 and how the same user experience can be achieved.
Hi @TristanJi369,
You wrote:
I really wanna know if there is difference about the univerlink between the ios18/ios17 and the ios 26. It works under ios18.
iOS 26 introduce significant security and privacy hardening at the system level. I'll outline the changed behaviors next.
The behavior of the activationURL handling is described below:
- iOS 18 or earlier: Triggers Universal Links — routes to native App or App Clip
- iOS 26 and later: Opens in embedded browser inside Wallet
The behavior if the app is installed is described below:
- iOS 18 or earlier: system launches issuer app directly
- iOS 26 and later: Web page loads; app isn't automatically launched
The behavior if the app isn't installed is described below:
- iOS 18 or earlier: system triggers App Clip via AASA
- iOS 26 and later: Web page loads; App Clip doesn't auto-trigger
The support of Universal Link/AASA is described below:
- iOS 18 or earlier: Yes
- iOS 26 and later: Bypassed for the initial URL load
To gracefully handle both flows, redesign the activation URL endpoint as a smart H5 landing page that actively attempts app launching via user-initiated deep links. This landing page would handle the following scenarios:
- App Clip / Smart Banner for
SFSafariViewControllercontexts - Explicit CTA using Universal Links
- Attempt Universal Link redirect on page load
- Show manual button as a fallback
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
