Getting started with ID Verification

The ID Verification Service (referred to as IDV) is a comprehensive system designed to facilitate identity verification processes for organizations. It ensures the accurate and secure handling of user identification by leveraging customizable templates, real-time verification checks and detailed session management features. This documentation provides an in-depth guide to configuring, managing and reviewing verification sessions within the service.

Key functionalities

IDV is divided into several components, each tailored to streamline specific administrative and operational tasks.

1. Administrators can easily create and manage verification templates, configure key settings and oversee ongoing and completed verification sessions.
2. The system also supports generating unique verification links, enabling efficient and user-friendly identity checks across different platforms, including web, iOS and Android.
3. In addition to standard verification functionalities, the service offers robust data analysis tools. Detailed session summaries, activity logs, raw data views and analyst logs provide transparency and auditability, empowering administrators to monitor and refine the verification process.

The SEON Platform currently supports two types of license keys, each serving a distinct purpose. Understanding the difference between them is crucial, as it affects how you integrate and authenticate with SEON’s services, ensuring proper access control and optimal system performance.

Fraud API keys

These are the keys that you can use to access the standard SEON products like Fraud API, AML or any other backend APIs. However this license key is also used for the IDV APIs — which is currently only the standalone face match feature.

Warning: These keys must never be used within the IDV SDKs, as doing so exposes them to potential theft due to limited security controls in client-side environments.

IDV SDK License Key Usage Guidelines

License keys for the IDV SDK are strictly platform-specific and are bound to a unique platform identifier (Platform ID). These keys must only be used within the corresponding IDV SDKs. Due to limited security controls in client-side environments, each license key is restricted to a single platform and Platform ID combination.

iOS

Once registered with SEON, you must provide your iOS app’s Bundle Identifier. The licenseKey we provide is tied to this Bundle ID.

Note:  Build configurations and environment-specific suffixes (like .dev, .staging, etc.) may alter your Bundle ID. If you have multiple environments, request a separate license key for each one.

Android

The Platform ID is the application’s Package ID. When registering, provide your Android app’s Application ID (also known as the Package ID). Your licenseKey will be validated against this ID.
If the SDK throws an "invalid license key" error, ensure your current app’s Package ID matches what you’ve registered.

Tip: As with iOS, build variants or environment-specific suffixes may affect this ID. Each variant should have its own license key if the Package ID differs.

Web

Platform ID is the application’s domain name. For web integrations, the licenseKey is matched against your application’s domain name (e.g., app.example.com).

If you encounter a license key validation error, it may be because the domain name your SDK is running on doesn’t match what was registered with SEON. Domains with www. can be accessed from the base domain, and vice versa. (e.g. www.example.com  will work with example.com and www.example.com  and www.example.com  will work with both as well)

Tip: For environments with multiple subdomains (like staging.example.com, test.example.com), you can request a wildcard domain license (e.g., *.example.com). The example wildcard domain will work with any subdomain, but also with the base domain example.com. Always register each unique domain you intend to use with SEON for accurate license validation.