Choose your integration method: From quick no-code iframes to full programmatic control with our JavaScript SDK, or drop-in plugins for WordPress, Shopify, and Salesforce.
Integration Methods
| Method | Setup Time | Backend? | Best For |
|---|---|---|---|
| JavaScript SDK | 3 minutes | Optional | Full control — React/Vue/Angular/Next.js/Nuxt/Svelte/vanilla |
| InContext (Iframe) | < 1 minute | Optional | Embedded experience without redirect |
| Redirect | 5 minutes | Yes | Maximum compatibility, cross-device flows |
| WebView (iOS/Android) | 15 minutes | Yes | Mobile fallback when no native SDK is available |
| WordPress + WooCommerce | 5 minutes | No-code | WordPress sites, WooCommerce stores |
| Shopify | 5 minutes | No-code | Shopify stores — checkout or account verification |
| Salesforce | 10 minutes | No-code | Salesforce CRM — Contact/Lead record verification |
Recommendation: For production web apps, use the JavaScript SDK for the best UX and full programmatic control. Use InContext iframe for the quickest setup, Redirect when cross-device verification is needed, and the dedicated WordPress / Shopify / Salesforce integrations if you live on those platforms.
JavaScript SDK
The Didit JavaScript SDK provides a programmatic way to integrate verification with full control over the user experience. Key Features:- Session management and event callbacks
- React, Vue, Angular, NextJS, Nuxt, Svelte and vanilla JS support
- Full TypeScript support
- Modal & inline modes
InContext (Iframe)
Embed the verification flow directly within your application using an iframe. Seamless experience without redirecting users away from your site. Key Features:- UniLink (no backend required) - setup in < 1 minute
- API Session (with backend) - full customization
- Modal and inline implementations
- React component examples
Redirect
Redirect users to the Didit-hosted verification page. After completion, users return to your callback URL. Key Features:- Maximum browser compatibility
- Cross-device verification support
- Simple integration
- Works when iframe camera access is problematic
Comparison
| Feature | JavaScript SDK | InContext (Iframe) | Redirect |
|---|---|---|---|
| Setup time | 3 min | < 1 min | 5 min |
| Backend required | Optional | Optional | Yes |
| Stays on your domain | Yes | Yes | No |
| Cross-device support | Yes | Yes | Yes |
| Full programmatic control | Yes | Limited | Callback only |
| Event callbacks | Real-time | postMessage | Callback only |
| White-label | Yes | Yes | Yes |
| Browser compatibility | All | All | All |
All three methods deliver final, signed results via webhooks — the comparison above describes the in-browser UX, not how you receive the verification decision.
Configuration
Required Iframe Permissions
For InContext iframe integrations, always include these permissions:Example Repositories
SDK Web Examples
React, Vue, Angular, Next.js, Nuxt, Svelte, and vanilla JS examples
Iframe Example
UniLink and API-session iframe examples
Full Next.js Demo
End-to-end Next.js integration
NPM Package
@didit-protocol/sdk-web on npmRelated
- Webhooks — receive signed verification results on your backend
- Create Session API — the endpoint behind every web SDK
- Native SDKs — iOS, Android, React Native, Flutter