Device-to-device verification
You can use two different devices for a single transaction. This is known as device-to-device verification (D2D). As smartphones have better cameras than laptop webcams, this feature enables higher-quality image capture.
You start a transaction on a laptop or desktop computer (primary device), and when you are at the document scanning step, the browser SDK will generate a QR code which you can scan with another (secondary) device, such as a smartphone.
This QR code will link to another web app which also uses the browser SDK. Users then open this web app on their mobile browser, and complete the transaction there.
You can self-host the secondary web app, or you can use the default Microblink web app. We describe the tradeoffs in the Run address article.
Workflow support
No workflow-level configuration is required for device-to-device to work. In other words, all workflows are supported, and you can use the D2D mechanism with every workflow.
Device switching supported
You can switch between devices during the execution of a workflow.
For example, if you have a workflow composed of several steps (capabilities), you can start the execution on the primary device, transfer (at the beginning) to a secondary device by scanning a QR code, perform the first step, exit, and be transferred back to the primary device where you will complete the rest of the steps.
If you switch back to the primary, you cannot re-switch to the secondary again.
No workflow configuration
Device-to-device is not the default method of completing workflows. Since every workflow supports being run this way, this means that you can only configure device-to-device on the SDK itself.
Read more on that in the Browser SDK section.
Browser SDK
Device-to-device scanning is supported by the browser SDK. Mobile-to-mobile flows are not supported: you cannot use the iOS SDK or the Android SDK to generate QR codes, or to finish flows with generated QR codes.
Read more about how to configure the SDK in the SDK configuration for D2D.