Prepare a Kiosk Session from Mobile

Mobile pre-staging prepares information for a later kiosk session. A customer might choose a service, supply an account reference or start an application before reaching the machine. At the kiosk, the application retrieves the permitted context and completes the identity, payment or physical-device steps required by the service.

This differs from device staging, which prepares a machine’s software and configuration before installation. The pre-staging definition guide explains both meanings. This article covers customer-session preparation; it does not describe loading firmware or provisioning security keys from a mobile phone.

Decide what is prepared and what remains at the kiosk

The business application owns the prepared record and the rules for retrieving it. Azimut SDK handles the supported peripherals needed to finish the workflow. For example, a bill reference selected on mobile can lead to a fresh bill lookup at the kiosk before a customer pays. A prepared application can still require document capture or an identity decision before approval.

Confirm current values with the responsible backend at the point where they matter. Prepared information is context, not proof that a bill remains payable, an identity check passed or a service is approved. A generic no-code promise is inappropriate when the service still needs backend mapping, security design or device integration.

Agree handoff and recovery rules

Choose the handoff method with the application team. Define what a reference or token permits, how long it remains valid, how it is bound to the intended customer and how repeated use is handled. These controls belong to the implemented workflow and must be verified for the selected system.

Decide what happens when the customer abandons the kiosk session, the reference expires or a backend reply is delayed. Keep incomplete work distinguishable from submitted transactions. Clear local customer context before the next session and retain only the audit information permitted by the service’s policy.

Test the mobile-to-kiosk journey with valid, expired and previously used references, as well as network interruption and cancellation. See pre-staged self-service workflows for the wider journey, and discuss your service with the team to agree the application and hardware responsibilities.

If your service already lives in a mobile app, Weave can run that Android, iOS or web app natively on the kiosk itself, so the journey a customer starts on their phone looks the same when they finish it in store.