> For the complete documentation index, see [llms.txt](https://docs.identomat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.identomat.com/platform-concepts/continuing-verification-on-mobile.md).

# Continuing verification on mobile

Move users from desktop to their phone and choose whether they finish in the mobile browser or in the Identomat app.

Many verification steps work best on a phone: the camera is better suited to document capture and liveness, and only a phone can read a document's NFC chip. With **Force user to continue on mobile device** enabled, a session can only be completed on a mobile device. You decide where on the phone the flow continues: **Web** or **App**.

## How it works

1. The user opens the verification link on a desktop.
2. Instead of starting the flow, the widget shows a QR code.
3. The user scans the QR code with their phone and continues there. Progress is kept, so nothing has to be repeated.

What happens after the scan depends on the option you choose:

<table><thead><tr><th width="218.17578125"></th><th width="197.2578125">Web</th><th>App</th></tr></thead><tbody><tr><td>Where the user continues</td><td>The mobile browser</td><td>The Identomat mobile app</td></tr><tr><td>QR screen title</td><td>Continue verification on your phone</td><td>Continue in the Identomat app</td></tr><tr><td>Installation</td><td>Not needed</td><td><strong>The Identomat app is required</strong>. Users without it are redirected to the App Store or Google Play</td></tr><tr><td>NFC chip reading</td><td>Not available</td><td>Available</td></tr><tr><td>Best for</td><td>Lowest friction, broad reach</td><td>High-assurance flows and strongest document checks</td></tr></tbody></table>

If the user opens the session directly on a phone, there's no QR code. With **Web**, they continue in the browser. With **App**, they're handed off to the Identomat app.

If the Identomat app isn't installed, scanning the QR code redirects the user to the App Store or Google Play to download it. After installing, they continue the same session in the app.

Inside the app, the user can either **Scan QR code** or paste the verification link or session token and tap **Start verification**.

### Download the Identomat app

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>iOS: App Store</strong></td><td><a href="https://images.unsplash.com/photo-1563203369-26f2e4a5ccf7?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwxMHx8YXBwbGV8ZW58MHx8fHwxNzk0ODEyMTY0fDA&#x26;ixlib=rb-4.1.0&#x26;q=85">https://images.unsplash.com/photo-1563203369-26f2e4a5ccf7?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwxMHx8YXBwbGV8ZW58MHx8fHwxNzk0ODEyMTY0fDA&#x26;ixlib=rb-4.1.0&#x26;q=85</a></td><td><a href="https://apps.apple.com/us/app/identomat/id6812367502">https://apps.apple.com/us/app/identomat/id6812367502</a></td></tr><tr><td><strong>Android: Google Play</strong></td><td><a href="https://images.unsplash.com/photo-1607252650355-f7fd0460ccdb?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwyfHxhbmRyb2lkfGVufDB8fHx8MTc5NDgxMjE4NXww&#x26;ixlib=rb-4.1.0&#x26;q=85">https://images.unsplash.com/photo-1607252650355-f7fd0460ccdb?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwyfHxhbmRyb2lkfGVufDB8fHx8MTc5NDgxMjE4NXww&#x26;ixlib=rb-4.1.0&#x26;q=85</a></td><td><a href="https://play.google.com/store/apps/details?id=com.identomat.app">https://play.google.com/store/apps/details?id=com.identomat.app</a></td></tr></tbody></table>

***

## Why continue in the app

### NFC: the most reliable way to verify a document

Biometric passports and most modern ID cards contain a chip that stores the holder's data and photo. That data is digitally signed by the issuing authority. When the app reads the chip over NFC:

* **Authenticity is proven cryptographically.** The signature confirms the data was issued by the authority and hasn't been changed. A visual check can only estimate this from an image.
* **Forgeries and copies are caught.** Printed copies, edited photos and screen replays have no valid chip, so they fail the check. On documents that support it, the chip also proves it's the original and not a clone.
* **Data is exact.** Name, document number and dates are read directly from the chip, with no OCR errors from glare, blur or worn documents.
* **Face matching is stronger.** The chip photo is the official image issued by the authority, and it's used as a trusted reference for liveness and face matching.

NFC reading needs the phone's native hardware access, so it's available in the Identomat app and mobile SDKs, but not in mobile browsers. To use it, select **NFC** as the **Method** in the **ID verification** step.

### Certified protection against video injection

Video injection attacks replace the live camera feed with prerecorded or AI-generated footage, such as deepfakes or virtual cameras. Identomat has successfully certified its video injection attack protection under the **CEN/TS 18099** standard, meeting the requirements of the **High** level.

### Native capture and device checks

* **Native camera control.** Sharper document and face images, faster capture and fewer retries than in a browser.
* **Device integrity checks.** Access from devices with altered system integrity is blocked.
* **Consistent experience.** The flow doesn't depend on browser versions, permissions or settings.

***

## Choosing between Web and App

* **Choose App** for regulated or high-risk onboarding, flows that need NFC, or when you want the strongest protection against spoofing and injection attacks.
* **Choose Web** when you want the user to start right away without installing anything, or when your audience may not be able to install apps.

## How to enable

1. Open the configuration in the No-code workflow builder.
2. In the **Configuration settings** tab, turn on **Force user to continue on mobile device**.
3. Select **Web** or **App**.
4. For NFC, open the **Configuration steps** tab and enable NFC reading in the **ID verification** step.
5. Click **Save**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.identomat.com/platform-concepts/continuing-verification-on-mobile.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
