At the counter
Use a supported reader setup for the current sale. Staff work from the catalog and order instead of entering an unexplained amount into an unrelated checkout.
SABSUS POSPayment provider integration
Take payment for the order your team is already working on. SABSUS connects supported Square reader and Tap to Pay configurations to its business workflow, bringing payment collection together with orders, appointments and customer context.
Use a supported reader setup for the current sale. Staff work from the catalog and order instead of entering an unexplained amount into an unrelated checkout.
SABSUS POSOpen the service visit, account for the confirmed deposit and collect the remaining balance. A supported phone can provide Tap to Pay without a separate reader.
Appointment depositsCollect payment in an attended workflow using the compatible mobile setup. The courier or waiter checks the result against the original order before treating it as paid.
Phone payment workflowsConfigure the correct merchant location and staff access for each payment setup. Keep a device's provider assignment separate from the employee's access to business records.
Multi-location operations| Requirement | How to evaluate it |
|---|---|
| Taking a payment | Use the supported SABSUS payment connection, eligible merchant account and compatible device. |
| Reading the payment outcome | Review the provider transaction reference and the corresponding order balance. A timeout is not proof of a decline. |
| Refunds and adjustments | Use the supported provider operation and employee permissions. Check the original transaction before making a change. |
| Catalog, stock and CRM synchronization | Define the exact entities, direction and ownership separately. Payment acceptance does not establish complete two-way synchronization of every Square product. |
| Replacing Square business software | A migration is a separate data and operating-process project; it is not the same as authorizing a payment provider. |
Square's Mobile Payments SDK is designed for native iOS and Android payment experiences; Terminal API is a different integration path. Confirm the path supported by your SABSUS application, the merchant country, hardware generation and operating-system version before purchasing equipment.
Do not assume that a phone's NFC chip or a reader's Bluetooth connection establishes compatibility. Tap to Pay needs the supported mobile app; opening an ordinary web page is not enough.
Square's SDK documentation restricts unattended installations. Tap to Pay has its own network requirements and must not be presented as offline acceptance merely because another SDK payment mode supports offline processing. Provider availability and terms can change.
Square remains the payment provider for this connection. Merchant onboarding, eligible countries, settlement and processing fees follow the provider's terms. SABSUS software charges and provider charges are separate.
No. Authorization permits the granted operations. Importing historical orders, customers, catalogs or stock needs a separately defined supported data process.
One ordinary payment, a declined attempt and a checked interrupted attempt, all starting from a known SABSUS order. Include a refund where that operation is supported and relevant.
Share the business type, merchant country, phone or reader model and the SABSUS workspace your team uses. Review the complete order-to-payment path on a matching setup.
Discuss the Square connection