You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a workflow for when the native app/mobile web is requesting verification (e.g., Know Your Customer) and the wallet is on the mobile device? The documented flow uses QR codes and requires multiple devices.
The text was updated successfully, but these errors were encountered:
Great question, and this might be worth an update to the documentation. We've built and tested a solution in the app that uses feature detection to present a clickable button on mobile instead of a QR code.
For configurations using OID4, a openid4vp:// link will appear on the screen when the user is on a mobile device. This will enable them to route the request to whatever handler wallet is installed on that device. It should just work out of the box. But please feel free to test and let us know of a specific configuration (e.g. app is loaded in a web view on a certain model phone) if you find it is not working in all scenarios that you're using.
The translations configuration enables a wide variety of customization of instructions and links on this page, in case you need to direct your users to an app store to pick up a recommended wallet. The use of custom openid4vp scheme in the OID4VP spec doesn't enable for app discovery after the user clicks, if a relevant app isn't already installed on the device.
Is there a workflow for when the native app/mobile web is requesting verification (e.g., Know Your Customer) and the wallet is on the mobile device? The documented flow uses QR codes and requires multiple devices.
The text was updated successfully, but these errors were encountered: