Eligible Android POS
Contactless collection needs an eligible device and an approved SoftPOS integration.
Connected payments
Payments that move with your restaurant.
One order. Flexible ways to collect. A centrally controlled payment workflow is the next step for connected restaurant service.
Keep the order at the centre.
One restaurant order
Table 12 £42.80
Cashier selects “Charge £42.80”
TableSyncAI coordinates the workflow
Synthetic order · no payment is being taken
- Eligible Android POSPlanned
- Authorised Staff devicePlanned
- Customer QRIn development
- Payment linkIn development
- Configured terminalPlanned
Provider result → backend checks → verified order state
Payment coordination is in development and is not deployed in the production API. Electronic collection through these routes is not yet available.
An eligible route for the way you serve.
Authorised Staff device
Assign collection within the same restaurant and location, while POS keeps order control.
Customer QR
Continue an eligible hosted payment journey from a customer-scanned code. Live checkout is not enabled.
Payment link
Continue through a supported, configured channel. Delivery and provider acceptance remain to be completed.
Configured terminal
Use compatible, approved payment hardware when that integration becomes available.
Windows POS would control the order and use an eligible external collection route. It does not provide native NFC collection. Hardware, provider and regional eligibility must be verified before a route becomes available.
One coordinated workflow, with checks where they matter.
- The cashier chooses the amount on the restaurant order.
- The backend checks the authorised device, location and eligible route.
- The customer completes that route.
- Backend verification and reconciliation establish the provider result.
- The order receives the verified payment state, visible to authorised devices.
Development includes order-linked sessions, route eligibility, idempotency, reconciliation and uncertainty handling. The intended workflow checks an uncertain result before allowing further collection. It is not a guarantee against every duplicate charge or a promise of instant confirmation.
Provider-specific objects and collection methods may differ. No single provider payment object is promised to work across all routes.
Restaurant payments and software plans are separate.
The connected collection routes here concern diners paying a restaurant. Your restaurant’s software plan is a separate subscription and access decision.
Explore the connected POSCompare software plans