Applications call capabilities, not drivers
Reduce coupling and allow hardware models to change without rewriting business journeys.
PLATFORM ARCHITECTURE
Secure, API-first kiosk middleware
A policy-driven coordination layer between business applications, peripherals, central operations and digital identity services.
TECHNICAL DECISION RECORD
Architecture designed for hardware change and operational control
Identity-aware local service
Every request is bound to application identity, session, scope and device state.
Desired state separated from immediate commands
Configuration, release, command and rollback carry history, TTL and verified outcomes.
End-to-end Trace ID
Connect applications, Agent, adapters, devices and backends in one audit chain.
API FIRST
Applications no longer integrate each driver
- Capability-based APIs independent of hardware model
- Local-only endpoints by default
- JWT, mTLS and signed assertions for app, user and device identities
- Offline queues, retry policies and event buffering
- End-to-end trace IDs across application, middleware, device and backend
CORE CAPABILITIES
Runtime at the edge, governance at the center
Session management
Checkpoints, timeout, incident recovery, single-writer lock and duplicate prevention.
Policy Engine
Decides which application may use which device in which tenant and context.
Secure Storage
Encrypts temporary data, purges it at session end and never stores PIN/OTP/biometrics.
Event & Offline
Normalizes events, queues locally, retries by policy and synchronizes audit evidence.
Trust Layer
OIDC/OAuth2, consent, step-up authentication, signed evidence and remote signing.
Observability
Telemetry, audit trails, SLA, tracing and controlled support bundles.
DEPLOYMENT
Four deployment models
On-premise
For banks, government, healthcare and data sovereignty requirements.
Hybrid
Cloud/private-cloud Control Plane with sensitive services in private zones.
Managed Service
Mobile-ID assisted operations, monitoring and SLA for distributed fleets.
Multi-tenant SaaS
For partners, SIs, franchises and multi-brand ecosystems.
DEVELOPER FLOW
Five-step execution flow
01
Register application
Issue app identity and device access scope.
02
Start session
Obtain a local token and discover kiosk capabilities.
03
Call normalized APIs
Print, scan, capture, NFC and pay through one API surface.
04
Enforce & route
Middleware checks identity, authorization, session and policy.
05
Audit & trust
Events reach the Control Plane; Trust Layer is invoked when required.