Skip to main content
Unilink is a single, reusable link per workflow that starts the hosted Didit verification flow — no backend required. Put it behind a button on your site, send it to users, or print it as a QR code. Each visit spins up a session for that workflow; results are visible in the Business Console for manual review.
Choose Unilink when you want zero backend integration and maximum speed to market, especially for manual or operational review scenarios:

Low-code / no-code teams

No API integration or backend setup needed.

MVPs and pilots

Validate your verification flow before investing in a full integration.

In-person KYC

Use the QR code in-store, at a branch, or on a kiosk.

Affiliate or referral verification

Share the link via email, SMS, or WhatsApp.
Skip Unilink if you need any of the following — use the API (Create Session) instead:
  • Deep backend control over sessions and lifecycle
  • Fully automated user journey (no manual steps)
  • Silent or background checks
  • Dynamic workflows based on user attributes
  • Complex conditional logic (branching by country, risk, document type)
  • High-volume, highly customized enterprise orchestration
Simple rule of thumb: if you want speed and simplicity, choose Unilink. If you want control and automation, choose the API integration.
1

Configure a workflow

In the Business Console, set up your verification steps, liveness/AML checks, and branding.
2

Copy the Unilink

Each workflow has a unique Unilink. Copy it from the workflow settings.
3

Distribute

Share the link via:
  • A button on your website
  • Email / SMS / WhatsApp
  • Printed or on-screen QR code
4

Review results

Operators review results in the Console and match to internal records.

​
Example: website button

​
Best practices

  1. Start with Unilink for manual ops and MVPs; evolve to Create Session as automation needs grow.
  2. Sandbox vs. Live — test with sandbox keys/links; swap for production at go-live.
  3. Security — if you expose the link publicly, consider bot-mitigation on the host page.
  4. Webhooks — verify signatures, retry on failure, and store event history if you automate later. See the Webhooks guide.