Check kiosk payments and order printing

1. Confirm the provider-approved hardware

Check the terminal model, supported integration and payment-slip printing responsibilities for unattended use. A portable terminal installation is not automatically suitable for a kiosk. eService’s native Android library also requires a compatible architecture and installed application build.

2. Check the local connection

In Technician Mode, configure the terminal’s supplied endpoint and run its connection check. Compare the identity with the physical device. Connection success alone does not confirm purchase authorization, a printed slip or a normal saved customer order.

3. Check the order printer

Match the local USB, LAN/TCP or paired Bluetooth profile to the installed printer. Printing policy, paper width, copies and automatic order-confirmation behavior come from the published configuration. Test printer and inspect the physical paper. A disconnected profile must be reconnected deliberately.

4. Verify a complete customer flow

With authorized test conditions, build a normal order, confirm options and total, complete payment and inspect the order number and expected printout. Verify the corresponding order reaches the intended POS preparation queue. Do not repeat a payment to solve a paper problem.

Important: a kiosk ticket is not a fiscal receipt

The kiosk’s ordinary order confirmation does not itself perform Posnet fiscalization. Where the configured workflow fiscalizes the paid kiosk order through POS, inspect that separate original fiscal result in POS.