Distribution Methods

Distribution methods define how your application delivers the verification workflow to the end user. The right choice depends on your integration type, whether users are on desktop or mobile, and whether delivery is real-time or asynchronous.

---

Direct Redirect

The default Gateway delivery method. Your application constructs an OIDC /authorize URL and redirects the user's browser to the ID Dataweb hosted verification UI. When verification is complete, the user is redirected back to your application with a signed ID Token.

When to use:

• Standard Gateway or SSO integration
• Web applications with redirect support
• OIDC-compatible identity platforms (Auth0, Ping, ForgeRock, etc.)

See Gateway (OIDC) Integration for the full implementation guide.

---

QR Code

QR code delivery allows you to move a verification session from a desktop or server-side flow to the user's mobile device — without requiring an SMS or email. The user scans the QR code and completes verification on their phone. The mobile session shares the same ASI (transaction ID) as the original session, maintaining full continuity.

Supported workflows: SMS Link, MobileMatch, Government ID and Selfie Match (document + selfie capture).

When to use:

• Desktop-first flows that require mobile document capture or selfie
• When SMS or email delivery is not available or preferred
• Frictionless mobile handoff with no additional friction for the user beyond scanning

sequenceDiagram
    participant Desktop as User (Desktop)
    participant App as Your Application
    participant IDW as ID Dataweb Platform
    participant Mobile as User (Mobile)

    App->>IDW: Initiate verification session (Gateway or API)
    IDW-->>App: QR code for this session
    App->>Desktop: Display QR code on screen
    Desktop->>Mobile: User scans QR code
    Mobile->>IDW: Continue verification on mobile device
    IDW-->>App: Verification result (same ASI)

Key details:

• Works with both Gateway and API integrations
• Gateway: QR code customization (size, shape, border) is not available — visual is fixed
• Instructional text shown with the QR code is configurable per workflow (including localization)
• You must choose either QR Code or SMS/Email delivery per API key — they cannot be active simultaneously

To enable: Contact your ID Dataweb team to configure the sendDocumentLinkAsQRCode flag on your API key.

---

Email / SMS Link

A verification link is sent directly to the user's phone (SMS) or inbox (email). The user clicks the link and completes the workflow in the hosted Gateway UI. Delivery can be triggered programmatically via API or manually via the Admin Console.

When to use:

• Asynchronous verification where the user is not actively on your site
• Onboarding or re-verification flows initiated by your system
• Cases where the user should complete verification on their own time

Programmatic delivery: Use the ID Dataweb API to generate and send a verification link. Contact your ID Dataweb team for the link generation API reference.

Manual delivery: Use the Admin Console's Send Verification Link feature — covered in Agent-Guided Verification.

---

Voice / SMS OTP or PIN

A one-time passcode (OTP) or PIN is delivered directly to the user's phone through SMS or voice call. The user enters the code in the hosted Gateway UI to complete the workflow. Delivery can be triggered programmatically via API or manually through the Admin Console.

When to use:

• Real-time verification during an active user session
• Login, step-up authentication, or transaction confirmation flows
• Cases where the user can immediately retrieve and enter a verification code

Programmatic delivery: Use the ID Dataweb API to generate and deliver an OTP or PIN through SMS or voice. Contact your ID Dataweb team for the OTP delivery API reference.

Manual delivery: Use the Admin Console's verification delivery features — covered in Agent-Guided Verification.

---

Admin Console (Agent-Guided)

Administrators and support agents can initiate verification directly from the Admin Console using Try Now, Send Verification Link, or Copy Link — no integration code required.

This covers two patterns:

• Agent-driven: Agent fills in user info and sends a challenge to the user's device
• End user-driven: Agent generates a link; user completes verification independently

See Agent-Guided Verification for the full guide.

---

Embedded API

With the ID Dataweb API, there is no redirect or hosted UI. Your application collects user attributes directly and submits them to the API. The user never leaves your application.

When to use:

• Full UI control required
• Mobile-native applications
• Headless or kiosk flows
• Brand requirements prevent external redirects

See ID Dataweb API for implementation details.