BankingTelecomGovernment

Connect kiosk identity capture to your verification service

Azimut SDK handles supported biometric and document capture devices through a unified API. Your application connects the captured data to the configured identity service and uses its result to guide the customer journey.

Request a Demo See the platform

Azimut SDK connects supported capture devices. The configured identity service owns verification and liveness decisions, while the bank or operator owns eligibility and compliance decisions. Agree consent, access, retention and session cleanup for sensitive data before rollout.

How it works

How the kyc & identity flow works

The SDK handles supported device operations. Your application coordinates the workflow with the services responsible for identity, payment and account decisions.

Document or account lookup

Customer presents ID document or existing account reference. SDK reads and parses the document via the document scanner.

Biometric capture

SDK triggers the fingerprint or facial scanner, collects the biometric sample, and manages device session state during capture.

Liveness check

Where required, the application follows the identity provider’s liveness flow. The provider determines the required capture steps and returns the liveness result.

Identity verification

The application submits the required capture data to the configured identity service and handles its response or timeout. The identity service owns the verification decision.

Result and continuation

The application presents the provider’s result and applies the operator’s continuation, retry or review policy. SDK device errors remain distinct from identity-service decisions.