Retail counter
Start with the basket and customer in SABSUS POS. The supported reader handles card acceptance while the order remains the reference for payment, stock and receipt workflows.
SABSUS · Connected payment hardware
Card readers connected to your POS, orders and appointments.
Connect supported payment readers to SABSUS and keep the transaction inside the business workflow. Checkout, appointments, customer history and payment status belong together, whether you run a shop, a salon or a service team.
- Build the saleProducts, services and the customer come from the order.
- Start collectionUse the configured payment connection.
- Customer paysFollow the reader's supported acceptance flow.
- Review the resultKeep payment status and the order together.
Choose hardware around the way customers pay
Salon reception
Find the appointment, review completed services and any deposit, then collect the remaining amount. Keep the sale connected to the employee and the customer's visit history.
Hospitality checkout
Keep the payment attached to the correct order instead of matching a terminal total to a separate ticket afterward. The chosen equipment should fit the counter or attended service process.
Customer-facing payment screen
Use a clear payment experience alongside the business workflow. Confirm the supported screen, reader and provider combination before designing the installation.
Choose the checkout before choosing the reader
The reader is where the customer presents a card. The business workflow determines which order is being paid, whether a deposit has already been collected and what balance remains. Demonstrate this complete sequence before selecting equipment.
Retail counter
Start with a basket, complete the configured payment and follow the result back to that sale. Include a declined attempt and a return in the demonstration, rather than evaluating the hardware only on a successful tap.
Salon reception
Open the visit, review the completed services and account for any advance payment. Confirm which supported screen displays the amount and where configured tips or receipt details are collected: not every reader offers the same controls.
When a payment outcome is unclear, check the existing attempt before retrying. A refund must refer to the original transaction and follow employee permissions and the provider's supported process.
Choose the right connection
A mobile reader, network terminal and phone are different setups.
| Checkout | Connection to evaluate | What determines compatibility |
|---|---|---|
| Phone or tablet with a reader | A supported mobile application and provider reader integration | Reader generation, mobile OS, application version, merchant country and account |
| Counter with a network terminal | The supported terminal/API flow for that provider | Exact terminal model, pairing, network and supported payment operations |
| Tap to Pay on a phone | A supported native mobile payment integration, without a separate reader | Eligible phone, OS, provider and account country; NFC alone is insufficient |
| Customer-facing kiosk | The provider-approved installation and attendance model | Hardware certification and whether staff are present; a mobile SDK is not blanket approval for unattended use |
Stripe documents separate reader connection paths for mobile, network and Tap to Pay setups. Square distinguishes Mobile Payments SDK from Terminal API. These provider capabilities must be matched to the connection implemented in SABSUS; an ordinary browser cannot simply pair with every Bluetooth payment reader.
Compatibility is a complete setup, not a connector shape
USB, Bluetooth, NFC or a network connection does not by itself make a device usable with every payment integration. The reader model, merchant provider, country, application environment and operating system must work together. SABSUS supports reader connections; equipment selection should use the actual supported combination.
Before rollout, test a successful payment, a declined attempt, an interrupted connection and the appropriate refund workflow. Check what staff see in the order and what the payment provider confirms. This is more useful than choosing a reader from its appearance alone.
An attended checkout and an unattended kiosk are different deployment scenarios. A reader approved for use with an employee present should not be assumed suitable for an unattended installation. Provider and hardware requirements are checked for the intended setup.
Card reader questions
Can I keep the reader I already own?
Possibly. Provide the exact model, provider and account country. Existing hardware can be evaluated against the supported SABSUS connection before replacing equipment.
Are Tap to Pay and card readers the same feature?
No. A reader is a separate payment device. Tap to Pay uses a compatible phone for contactless acceptance. Both can be part of SABSUS payment workflows, with different setup requirements.
Does connecting a reader change my processing fees?
Connection alone does not establish a new rate. Processing fees, settlement timing and merchant approval are governed by your provider arrangement. Review these separately from software and hardware costs.
Does an offline POS guarantee offline card acceptance?
No. Local order handling and card authorization are different capabilities. Offline card acceptance, where offered, depends on the payment provider and exact equipment configuration.
See a complete checkout, not just a terminal.
Share the reader model, cashier device, merchant country and provider. Review an ordinary sale and the exception that matters most to your team before choosing equipment.
Request a connected checkout demonstration