Incode supports multiple integration methods across web and mobile platforms. This section guides you through the setup and implementation details for each approach.
Use the tables below to identify the right integration method for your platform and technical requirements.
Web
These integration methods run Incode’s identity verification in a browser environment. They vary in how much code you write and how much control you have over the user experience.
| Integration Method | What it is | Technical effort |
|---|---|---|
| Flows / Workflows | A hosted, Incode-managed web app your users complete at a URL you share or redirect to. Configured in Dashboard; no front-end code required. | Minimal. Backend session start recommended |
| iFrame | Embed the Incode-hosted flow inside your own web page using an HTML <iframe>. Keeps users on your domain. |
Low. A few lines of code |
| Redirect URL | Redirect users from your web or mobile app to the Incode-hosted flow, then back to your app on completion. | Low. Backend session start + redirect logic |
| WebViews | Load the Incode-hosted flow inside a native mobile app’s embedded browser component. | Moderate. Requires specific native app configuration |
| Web SDK | Integrate identity verification directly into your custom web application using the Incode Web SDK. Full control over flow and UI. | High. Requires dedicated front-end development |
Mobile
These integration methods use Incode’s native and hybrid mobile SDKs to embed identity verification directly into your iOS, Android, or cross-platform mobile application.
| Platform | SDK Type | Technical effort |
|---|---|---|
| iOS | Native SDK | High |
| Android | Native SDK | High |
| React Native | Hybrid SDK | High |
| Flutter | Hybrid SDK | High |
| Xamarin | Hybrid SDK | High |
| Cordova | Hybrid SDK | High |
Each platform page covers environment setup, Workflow and Flow-based integration, full SDK integration, and platform-specific advanced configuration.
API-Only Integration
If you need to orchestrate identity verification server-side without a front-end SDK, you can use the Incode Omni API directly.
See the following references in the API documentation:
- Create an Onboarding Session: Start a session and generate an onboarding URL
- How to Fetch Results and Data: Retrieve scores, OCR data, images, and device info
- API Batch Processing: Run ID validation and face validation programmatically
Considerations for API-Only integrations
API-Only integrations have no SDK download impact, but they also do not include Incode's on-device Device and Camera trust signals, which the SDKs use to detect face and document deepfakes at the capture layer. With API-Only, deepfake protection relies on server-side video and image analysis. To add device-level protection to an API-Only integration, you should use Deepsight. Deepsight requires additional licensing; contact your Incode representative for more information.
With API-Only, you are also responsible for building the capture experience: selfie capture, document capture, and any user-facing UI are not provided by Incode in this integration model.