Card payments at the
counter or table.

In four steps. Ring up the ticket on any Vertex terminal and the total is pushed straight to the card device, so nobody re-keys the amount. The guest taps or dips and chooses a tip, then the POS updates and prints or emails the digital receipt. Because the figure comes from the ticket rather than being typed again, counter terminals that sync with your fixed POS cut input errors during peak rush. Refunds are managed through the same POS workflow.

Yes. Table-side payment with supported handheld devices lets a server finish the transaction in front of the guest instead of walking a card back to a fixed station, which is aimed at improving table turnover and guest convenience in one step. The same setup drives counter payment on a fixed reader when the priority is keeping a high-volume queue moving.

The tip prompt appears on the device once the total has been pushed to it. Percentage levels are venue-configurable, so you set your own presets alongside custom and no-tip options, and suggested amounts adapt to the bill total when configured. The interface is deliberately discreet to keep the guest's choice their own, and the tip flows into the same payment and staff reporting workflow rather than being captured separately.

Central Device Management puts every registered device on a single dashboard, split into live and offline views: terminal name, online status, battery level, last activity and location. New hardware is registered from the same screen, and connection detail is visible per device — Bluetooth connection state on a Stripe Terminal reader, signal strength and IP address on a PAX/UPA unit — so a flat handheld sitting in storage is something you spot before service rather than during it.

Payment data does not touch your local servers: the transaction flow is handled directly by the secure hardware provider, sensitive card details are replaced by tokenized references, and the point of interaction uses end-to-end encryption. That architecture is designed to support your PCI-DSS obligations and limit the card data your own systems ever see — it is not a certification in itself. Your compliance status, and the processing terms behind it, remain matters for you, your payment provider and your acquirer.