Process cloud payments with the New POS Experience
Beta: The New POS Experience is currently in beta. For the stable experience, see Payment processing.
A cloud-reader payment in the New POS Experience routes the charge to a paired terminal. The terminal displays the amount, the guest taps, swipes, or inserts their card, and the surface returns the auth result in real time. Offline mode queues charges and replays them on reconnection.
Audience: Front desk staff taking card payments through a paired cloud reader in the New POS Experience.
Before you begin
- Your organization has Stripe terminal (or another supported cloud-reader integration) enabled.
- A reader is paired with your iPad or terminal.
- You have the Take Payment permission.
Steps
1. Pick the cloud-reader payment method
In the Payment segment of the right pane, select Credit card (cloud reader). The amount defaults to the invoice's outstanding balance.
2. Send the charge to the terminal
Select Charge. The cloud-payment screen opens and the paired terminal displays the amount. The screen shows the terminal status in real time: idle, waiting, processing, approved, or declined.
3. Hand the reader to the guest
The guest taps, swipes, inserts a chip card, or enters PIN as required. The terminal sends the auth request and returns the result.
4. Confirm the result
- Approved β the surface returns the credit-card receipt with the transaction ID, amount, last 4 digits, status, and date / time. The footer balance updates.
- Declined β the surface displays the decline reason. Ask the guest for a different card or different payment method.
5. Cancel a pending charge
Before the guest presents the card, you can cancel the pending charge from the cloud-payment screen. After the guest has presented the card, cancel is no longer available β wait for the auth result.
Offline mode
When the processor supports it and your network drops mid-charge:
- The terminal queues the charge locally.
- The surface displays an offline indicator.
- When connectivity returns, the terminal replays the queued charge and the surface returns the auth result.
Do not retry the charge while offline. Wait for the queued charge to settle on reconnection. Retrying creates duplicate charges.
Tips
- The credit-card receipt screen surfaces only after the cloud-reader charge clears. If you closed the surface before the receipt appeared, the receipt is still accessible from the closed-invoice view via Reprint receipt.
- For organizations that require OTP verification on card-on-file save, the OTP prompt appears after the cloud-reader charge clears. See Save a guest card with the New POS Experience.
Troubleshooting
- Terminal status is stuck on waiting. Confirm the terminal screen is on and the terminal is paired. If pairing was lost, re-pair from the front-desk shell's terminal settings.
- A queued charge replayed twice. Contact your administrator with the transaction ID. The processor's audit log will show the actual settlement count.
- The auth result is approved but the invoice still shows a balance. Refresh the invoice; the footer should update. If it does not, the payment may have been booked to a different invoice β check the invoice audit log via View invoice audit logs.