Workflow Design
Design Pre-Staged Kiosk Workflows
Published: 15/05/2026
By Azimut Team
Updated:
A pre-staged kiosk workflow starts with context prepared elsewhere and finishes the steps that require the kiosk or its connected services. The design task is to identify which information can be reused and which decisions must be made again at the point of service.
The definition guide distinguishes customer-session preparation from device provisioning. For a customer arriving from a phone, use the mobile handoff guide. This page focuses on mapping the complete workflow.
Map each prepared value to its owner
A prepared bill reference can identify the intended account, while the biller remains responsible for the current amount and payment acknowledgement. A selected SIM plan can establish customer intent, while the carrier decides eligibility and activation. An application record can reduce data entry without replacing required identity checks.
Write down the source, freshness requirement and allowed use of each prepared field. The application should obtain a fresh decision where the service requires it. Avoid treating a retrieved record as an instruction to perform a financial or physical action automatically.
Design the remaining kiosk steps
Azimut SDK connects the application to supported peripherals. The application coordinates capture, payment and fulfilment with the responsible backends. Distinguish the result of each physical action from the backend result: cash acceptance, biller posting and receipt output are separate outcomes.
Agree how references expire, how repeated use is controlled and what can be resumed after abandonment. Keep unresolved operations linked to their original references and reconcile uncertain acknowledgements before repeating them. Clear the previous customer’s local context when the session ends.
Test prepared and unprepared journeys with the same service requirements. Include expired references, changed bill amounts, rejected identity checks, hardware faults and network loss. Compare completion and support outcomes as well as time at the machine. Discuss the workflow using the service interfaces and devices you intend to deploy.
Related solutions
Where this work fits in the platform.
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.
Continue reading
A Smarter Way to Handle Currency Exchange with Azimut
Upgrade currency kiosks with multi-currency, AML, and real-time rate support.
Modernise Legacy Kiosks Without New Hardware
Legacy kiosks fall behind your app. Modernise them with Weave, Azimut SDK and middleware, keeping your hardwar…
Reading ID Chip Data for Kiosk Identity Workflows
Separate document capture, chip access, signature validation and the identity decision when integrating ID rea…