Skip to main content

Productivity Tips

Customer Identity Verification at a Self-Service Kiosk

Published: 05/11/2026

Customer Identity Verification at a Self-Service Kiosk

A kiosk identity workflow collects the information required by a service and obtains a decision from the authorised verification system. Automating capture can reduce repeated data entry, but reading a document or fingerprint does not itself approve a customer, open an account or satisfy every compliance requirement.

Azimut SDK connects supported document readers, cameras and biometric devices to the application. The application coordinates the steps with the bank, telecom operator or identity provider that owns the decision. The KYC and identity use case explains this division of responsibility.

Design for an incomplete or unsuccessful capture

Tell the customer what to present, when to hold it still and how to recover when the reader cannot obtain the required information. Distinguish unavailable hardware, an unreadable document and a rejected verification result. Each needs its own customer message and support outcome.

Where the service requires liveness, chip authentication or additional checks, verify that the selected reader and connected service support them. A generic biometric or document-reader listing is not evidence that every check is available. Use the passport reader guide for compatibility and recovery questions.

Keep session data under control

Agree which fields the service needs, who can access them and where they may be retained. Keep biometric templates, document images and personal fields out of routine logs and analytics. Use the deployment’s approved authentication and origin controls when connecting a browser application to a local runtime or backend.

Cancellation, timeout and session expiry must prevent a late capture from updating another customer’s record. On failure, follow the operator’s retry or assisted-service policy instead of repeatedly collecting sensitive data without a clear outcome.

Evaluate the complete journey with the identity-service team, including missing fields, rejected checks, disconnection and abandonment. For changing the kiosk’s wider service catalogue, use the separate kiosk extension guide. Contact the team with the document types, devices and required decisions for your workflow.

Try it yourself

Book a demo

See how Azimut SDK works in your self-service environment. We'll walk through your use case, hardware setup, and integration options.

Book a demo