Choosing an Integration Method

eKYC has three integration paths. Pick one before you write code — switching later is expensive.

Quick Comparison

What	Description
API	You build the capture UI yourself. Your backend calls the API directly. Most control, most work.
Mobile SDK	The SDK handles capture, on-device quality checks and the API calls. Android, iOS, Flutter.
Web SDK	The same, in the browser. Works inside a WebView too.

Which One

What	Description
Native Android or iOS app	Mobile SDK. Auto-capture and on-device quality checks cut down retakes.
Flutter app	Mobile SDK (Flutter). It is also the only platform with full theming across all five screens.
Web or WebView	Web SDK. Requires HTTPS and camera permission.
Server-to-server	API. Right when images come from elsewhere — a branch counter, pre-scanned files, a legacy system.
You already have a capture screen	API. An SDK would collide with your existing UI.

Differences That Matter

On-device quality checks. The Mobile and Web SDKs run the quality models on the device before uploading, so the user sees a "too blurry" prompt while still holding the card. With the API every piece of feedback costs a network round trip.

Key safety. The Access Key belongs on your backend and nowhere else. SDKs authenticate with a per-transaction JWT minted by Create Transaction. Whichever path you choose, your backend is still in the loop.

Theming. Flutter offers the most — five screens, light and dark themes, custom fonts. Android and iOS only let you replace the loading view. The Web SDK lets you inject your own views at the architecture level.

INFO

These paths are not mutually exclusive. A common pattern: the Mobile SDK handles capture and quality, while your backend calls Search Faces directly for duplicate detection — something no SDK does for you.

Next Steps

• Getting Started — try it with cURL before committing
• Mobile SDK Overview — concepts shared across the three platforms
• Web SDK Overview — environment requirements and packaging