Custom hardware integrations
Each diagram below illustrates one possible high-level integration flow, not a fixed specification. For the authoritative reference on each integration, see the the specific integration articles.
The message flow between the kiosk frontend, FO, the kiosk integration (cloud and on-device), and the POS depends on which capabilities your kiosk integration provides. This article gives one diagram per scenario, so find the heading that matches your integration rather than reading all of them.
Scanner integration
If your kiosk uses barcode or QR code scanning, refer to the following diagram. Scanning does not depend on, or change, the payment or printing flow.
This diagram shows the messages exchanged when the guest scans a barcode or QR code, independent of any payment or printing scenario below.
See Scanner service for the plugin-side implementation.
Without external payment terminal integration
Use this section if the kiosk does not integrate with a payment terminal — for example, if the guest pays with a mobile wallet, a stored value card, or another payment method that is not connected to the kiosk itself.
Non-fiscal country
Without receipt printing option selection
This diagram shows a kiosk order placed without any kiosk payment terminal integration, in a non-fiscal country, with no receipt printing option offered to the guest.
With receipt printing option selection
This diagram shows the same non-fiscal, no-payment-terminal scenario, but with the guest offered a receipt printing option after a successful order placement.
Fiscal country
When payment does not go through the kiosk's own payment terminal integration, there is no payment reservation or capture flow to anchor fiscalization to. Instead, Kiosk Integration Cloud listens for the order.placed_in_pos event from FO and fiscalizes based on that event.