Software development kitSDK

The prebuilt capture component you drop into your app.

Instead of building a camera screen for ID and selfie capture from scratch, a developer adds the SDK, and it handles the capture experience.

A client library handling capture guidance, quality checks, encryption, and device integrity. A client library is code that runs inside your own app on the user's device, and device integrity means checks that the device and app have not been tampered with.

An SDK typically handles several jobs:

• Capture guidance, by showing the user how to position a document or face and giving live feedback.
• Quality checks, by detecting blur, glare, and poor framing before an image is sent.
• Encryption, by protecting the data on its way to the server.
• Device integrity, by detecting emulators, rooted devices, and signs of tampering.
• Liveness and other on-device steps, by running part of the checks on the phone.

A developer typically uses it like this:

1. They add the SDK to their iOS, Android, or web app.
2. They configure it with their account details and flow settings.
3. The SDK runs the capture experience and sends the data for verification.
4. The result returns to the app, often through a webhook or a callback.

An SDK sits next to terms that are easy to mix up:

• Webhook delivers decisions to a server, while the SDK works on the device.
• API is a way to call a service directly, and an SDK wraps those calls with a ready-made interface.
• Screen replay detection is one of the checks an SDK can help perform at capture.