Hilfe - Alle Produkte & Anleitungen

SoftPOS in Kiosk Mode

SoftPOS card payment in kiosk mode works on the bessa POS, but not on the bessa Gastro Kiosk — with one important exception: bessa Pay is integrated directly into the POS app and works in the POS Self-Service Mode without any extra configuration. Third-party SoftPOS solutions (e.g. Hobex POSit, Global Payments GPTom) run as standalone apps and require an app switch, which means additional setup. This page explains the technical background and shows how to set up a bessa POS as a self-service Sales Point with SoftPOS. The audience is operators of 24/7 self-service shops, unattended pickup stations, and Sales Points running in the bessa POS Self-Service Mode who want to use a tap-to-pay solution.

How SoftPOS and kiosk mode interact

SoftPOS solutions are standalone Android apps. During payment, the device automatically switches to the SoftPOS app, processes the NFC payment, and returns to the POS app afterwards.

Kiosk modes (app lock, lock task, immersive mode) prevent exactly this app switch — that is their purpose: customers should not be able to leave the active app. This creates a direct conflict: no app switch means no SoftPOS transaction.

Classic network or ZVT terminals are not affected by this limitation. They run as external devices and do not require an app switch on the POS.

Special case: bessa Pay

bessa Pay is a tap-to-pay solution integrated directly into the bessa POS app and uses the device's NFC chip without a separate app. There is no app switch — the POS's kiosk mode keeps running with full app-lock protection. No additional device-level configuration is needed. bessa Pay is currently available on the bessa POS; on the bessa Gastro Kiosk it is not yet enabled.

Status per product and payment solution

Scenario

Status

Mechanics

bessa POS (standard mode) — any SoftPOS solution

Yes

No enforced app lock; app switching is always possible.

bessa POS in Self-Service Mode (

Self-Service Mode

) + bessa Pay (Tap to Pay)

Yes, normal

bessa Pay is integrated into the POS app; no app switch needed; the internal app lock can stay active.

bessa POS in Self-Service Mode + third-party SoftPOS (Hobex POSit, GPTom, etc.)

Conditional — see setup below

The POS detects the SoftPOS payment method and suppresses its internal app lock. The device-level lock has to be set by the operator via the operating system's kiosk mode.

bessa Gastro Kiosk

+ bessa Pay

Currently not available

Would be technically compatible; bessa Pay is not yet enabled on the Gastro Kiosk.

bessa Gastro Kiosk + third-party SoftPOS

No

The ordering app uses lock task mandatorily, so an app switch to the SoftPOS app is not possible. Vendor detail pages reflect this with "bessa Kiosk (kein SoftPOS)".

bessa Tap

No (for SoftPOS)

Same as Gastro Kiosk. Use a network or ZVT terminal instead.

Setting up SoftPOS on the bessa POS in Self-Service Mode

Pick the variant that matches your payment solution.

Variant A — With bessa Pay (Tap to Pay)

Because bessa Pay is integrated directly into the POS app and does not trigger an app switch, the POS Self-Service Mode runs as usual — the POS's internal app lock stays active. No additional device configuration is needed.

  1. Set up bessa Pay as a payment method.

  2. Activate the Self-Service Mode module on the bessa POS.

  3. Run an end-to-end test: start a sale → complete the tap-to-pay transaction → receipt is created. Customers cannot leave the POS app — the app lock works as usual.

Variant B — With third-party SoftPOS (Hobex POSit, Global Payments GPTom, etc.)

Third-party SoftPOS solutions run as standalone apps and require an app switch. The POS therefore has to suppress its internal app lock — protection is provided by the operating system's kiosk mode instead.

Step 1 — Configure the SoftPOS provider

Set up the SoftPOS payment method in the bessa POS first. Which providers support SoftPOS and which configuration parameters are required is documented on the respective vendor detail page:

Step 2 — Activate Self-Service Mode on the POS

Activate the Self-Service Mode module on the bessa POS. As soon as a third-party SoftPOS payment method is configured, the POS disables its internal app lock automatically — otherwise the switch to the SoftPOS app would not be possible.

Because the POS intentionally does not set its app lock in this scenario, the lock has to be enforced at the device level. Without an OS kiosk mode, customers can leave the POS app via the home button, recents, or quick settings.

Step 3 — Activate the device kiosk mode and whitelist both apps

Set up kiosk mode at the operating system level and whitelist both the bessa POS and the SoftPOS app:

  • Sunmi devices (e.g. T2, T3, V2 Pro): activate the app lock / kiosk mode via Sunmi Tools or the Sunmi Launcher and whitelist both apps. See the Sunmi vendor documentation for details.

  • iMin devices (e.g. M2 Pro, S1, D3): create a kiosk profile in the iMin Manager and allow both apps. See the iMin vendor documentation for details.

  • Generic Android devices (Android 8 or newer): set up a kiosk profile via device owner mode or an MDM solution (Android Enterprise, Scalefusion, Esper, Headwind, etc.) and add both package names.

Step 4 — Run an end-to-end test

  1. Start a POS sale and select the SoftPOS payment method — the switch to the SoftPOS app must work smoothly.

  2. Perform an NFC payment on the device.

  3. After completion, the SoftPOS app returns to the POS, the receipt is created or printed.

  4. Verify the lock: try to leave the POS app via the home button, recents, or a swipe gesture. The device kiosk mode must block this — otherwise the whitelist is incorrect or the OS kiosk mode is not active.

FAQ

Why doesn't the bessa Gastro Kiosk support third-party SoftPOS? The Gastro Kiosk uses lock task mandatorily so customers cannot leave the ordering app. Because third-party SoftPOS requires an app switch, the two mechanisms cannot be combined. Use a classic network or ZVT terminal on the Gastro Kiosk for now.

Does bessa Pay work on the bessa Gastro Kiosk? Not yet. bessa Pay is not yet enabled on the Gastro Kiosk, even though it would be technically compatible (no app switch). On the bessa POS (including the Self-Service Mode module) bessa Pay is fully supported.

Which SoftPOS providers are confirmed for use in POS Self-Service Mode? Three providers (per the vendor detail pages): bessa Pay (Tap to Pay, no extra app), Hobex (POSit), and Global Payments (GPTom). bessa Pay is the only solution that does not require a device kiosk mode.

Do I need a device kiosk mode for bessa Pay? No. bessa Pay is integrated into the POS app; the POS's app lock stays active and protects against app switching. An OS-level kiosk configuration is only required for third-party SoftPOS.

Do I need an MDM for the device kiosk mode (Variant B)? Not on Sunmi or iMin devices — both vendors ship the kiosk mode built in. On generic Android devices, an MDM or device owner configuration is recommended to enforce the whitelist reliably.

Can I switch back from third-party SoftPOS to a classic terminal or to bessa Pay later? Yes. As soon as no third-party SoftPOS payment method is configured anymore, the bessa POS re-enables its internal app lock. The device kiosk mode can then optionally be deactivated.

Troubleshooting

Symptom: Tapping the payment method does not switch the POS to the SoftPOS app. Resolution: Check the payment method configuration — is the SoftPOS provider mapped correctly? Follow the vendor detail page (Hobex, Global Payments / GPTom, bessa Pay).

Symptom: Customers can leave the POS app via the home button. Resolution: The device kiosk mode is not active, or the app whitelist is incomplete. Check in the device settings that kiosk / app lock mode is running and that both apps (bessa POS and the SoftPOS app) are included.

Symptom: The SoftPOS app crashes or does not return to the POS. Resolution: Update the SoftPOS app to the latest version and consult the vendor documentation of the SoftPOS provider (POSit, GPTom, etc.). If the POS does not come back, restarting the POS app usually helps.

Symptom: The POS enforces its internal app lock despite a configured SoftPOS payment method. Resolution: The POS does not recognize the provider as SoftPOS. Save the payment method again and restart the POS. If the behaviour persists, report it to bessa support including provider and app version.