Android kiosk with a card payment terminal
Take card and contactless payments from your Android app through a supported PCI-compliant terminal. The app sends one JSON request; Azimut SDK drives the terminal and returns the result.
Azimut SDK
NEW · AZIMUT SDK FEATURE
Weave
Android kiosk software that works with your kiosk hardware
Run your Android, iOS or web app natively on every kiosk.
Android iOS Web
Weave is an Azimut SDK feature that runs your existing Android, iOS or web app natively on self-service kiosks. Customers get the same look, journeys and offers they know from your app, and the kiosk’s card, cash, ID, SIM and printer hardware stays connected through Azimut SDK.
ANDROID KIOSK HARDWARE
Connect your Android app to real kiosk hardware
Android kiosk-mode tools lock a tablet to one app. Self-service kiosks also need payments, cash, printing, ID and SIM hardware. With Weave, your Android app keeps its screens and calls Azimut SDK’s JSON API for every supported device, whichever model each kiosk uses.
Android kiosk with a cash acceptor
Accept notes for bill payments and top-ups. Your app reads the confirmed amount from Azimut SDK instead of talking to the cash device directly.
Android kiosk with a receipt printer
Print receipts, eSIM QR codes and vouchers from the same app screens customers use on their phones.
Android kiosk with an ID and passport scanner
Capture identity documents for KYC and SIM registration, then pass the result to your verification service.
Android kiosk with a SIM card dispenser
Issue physical SIM cards from a supported dispensing module after identity checks and payment are complete.
Android kiosk with a barcode and QR scanner
Read bills, vouchers and phone QR codes to start or continue a journey without typing.
Android kiosk with a biometric scanner
Add fingerprint or face capture where your KYC policy requires it. Your identity provider handles matching.
iOS and web kiosk apps
Weave runs iOS and web apps on kiosk hardware the same way: your app keeps its screens, and Azimut SDK handles the devices.
TWO MODES
Mirror your app, or embed it
The difference is where your app runs. Hardware stays on Azimut SDK either way.
MODE 01
Weave Mirror
Change your app. The kiosk follows.
AI-assisted tooling analyses each change in your Android, iOS or web app and applies the same screens and journeys to the kiosk app, rebuilt for the kiosk and its hardware. Every change goes through automated tests and a staged, reversible release.
MODE 02
Weave Embed
Your app, running in the kiosk.
Your app runs natively on a device inside the kiosk, exactly as it runs for customers, so every app release reaches the kiosk when it reaches phones. A Windows enclave in the kiosk keeps payment, cash, ID, SIM and printer hardware connected through Azimut SDK.
Choose the right mode
| Comparison | Weave Mirror | Weave Embed |
|---|---|---|
| How it works | AI-assisted tooling reads changes in your app and updates the kiosk app | Your app runs natively on a device inside the kiosk |
| Update speed | Fast: each change is converted, then tested | Immediate: the same release as phones |
| Existing kiosk software | Existing kiosk software is kept and reused | Kiosk journeys move into your app |
| Hardware | One Windows enclave per kiosk | App device plus Windows enclave |
| Who builds kiosk journeys | Azimut, in the kiosk app | Your app team, with Azimut |
With Weave Embed, every kiosk journey — including payments, SIM and ID — is built in your app. Weave Mirror keeps those journeys in the kiosk app. Both keep the hardware in the Windows enclave under Azimut SDK.
ARCHITECTURE
Modern frontend. Any back end.
Weave brings your app to the kiosk. Azimut SDK handles the devices. Azimut middleware sits between the kiosk and your back end. It translates every request so legacy billing, CRM and document systems work seamlessly with a modern app frontend — over REST, SOAP/XML, message queues or SFTP — without replacing them.
See it for mobile operatorsYOUR APPScreens, journeys, offers
WEAVEMirror or embed your app
AZIMUT SDKEvery device, one JSON API
AZIMUT MIDDLEWAREREST · SOAP/XML · MQ · SFTP
YOUR SYSTEMSCatalogue · billing · CRM · KYC
SATELLITEReleases & fleet health
Weave FAQ
Can an Android app control kiosk hardware like card readers and printers?
Yes. With Weave, your Android app calls Azimut SDK’s JSON API for supported card payment terminals, cash acceptors, receipt printers, ID and passport scanners, barcode scanners, biometric scanners and SIM dispensers. The SDK handles each device model, so the app doesn’t need vendor drivers.
How do I turn my Android app into a kiosk app?
Weave offers two routes. Weave Embed runs your Android app natively on a device inside the kiosk, with the same release as phones. Weave Mirror applies changes from your Android app to a dedicated kiosk app with AI-assisted tooling, automated tests and staged releases. Both connect to kiosk hardware through Azimut SDK.
Is Weave the same as Android kiosk mode?
No. Android kiosk mode, usually set through device management, locks a device to a single app. Weave brings your app to a self-service kiosk and connects it to payment, cash, printer, ID and SIM hardware. Satellite can manage the kiosk fleet alongside it.
Does Weave support iOS and web kiosk apps?
Yes. Weave runs existing Android, iOS and web apps natively on self-service kiosks. Confirm your app platform, framework and target kiosk configuration during scoping.
What is the difference between Weave Mirror and Weave Embed?
Weave Mirror uses AI-assisted tooling to apply changes from your app to the kiosk app, with automated tests and staged releases, and keeps your existing kiosk software. Weave Embed runs your app natively on a device inside the kiosk, so kiosk updates arrive with the same release as phones.
Where does the kiosk hardware run?
In both modes, card, cash, ID, SIM and printer hardware stays connected to the Windows enclave through Azimut SDK and its JSON API. Your app requests device operations; the SDK handles the devices.
How are Weave Mirror changes tested?
AI-assisted conversion is always paired with automated tests and staged, reversible releases through Satellite, so a change reaches a small group of kiosks before the wider fleet.
Does Weave work with legacy back-end systems?
Yes. Azimut middleware translates kiosk requests for your systems over REST, SOAP/XML, message queues or SFTP, so legacy billing, CRM and document systems work with your app frontend without being replaced.
See your app on a kiosk
Tell us about your app, your back end and your kiosk estate.
Request a Weave demo