POS Velocity keeps card handling on the PAX terminal and combines kiosk restrictions, sign-out when the screen goes off, per-role rights, change history, and remote device controls.
The payment app on the terminal reads the card. Downstream, POS Velocity keeps only masked details — the last four digits, the brand, and the approval.
Terminal live. Digits entered on the keypad are shown encrypted.This interactive illustration does not process a payment. In production, card input is handled within the configured PAX terminal and payment environment, while device access controls are managed through the portal.
POS Velocity does not store full card numbers. The configured PAX payment flow handles card input and returns the transaction information required for receipts, reporting, and supported follow-up operations.
Below is the live read-out from the terminal above — the same entry, shown the way each hop of the chain sees it. The terminal's payment app reads the card; POS Velocity keeps only masked details.
Review each control and what it does, in clear language.
Keep scrollingCard-present payments are read by the payment app on the PAX terminal. POS Velocity keeps only masked card details — never the full number or security code. A payment link is the one exception: the card is typed on a hosted page, passed to the gateway, and only a masked number is kept.
Void, refund, cash refund, manual card entry, and price changes are set per role, with limits per site. Voids and refunds always need a named employee.
Terminals and the portal connect to POS Velocity over HTTPS.
Once signed in, the terminal hides the system bars, disables Home and Recents, brings the app back if another app takes over, and needs the terminal passcode to exit.
A cashier is signed out when the terminal's screen turns off, and 5 seconds after the app leaves the foreground. An idle sign-out of 1 to 30 minutes can be set per terminal. The next person signs in with a PIN.
Each sale records the employee, terminal, and shift, and price changes record the approving manager. Edits to terminals and staff keep who changed what, and when.
A terminal signs in only when the merchant ID in its payment app matches your account. On a mismatch it stops at a blocking screen and your managers are alerted.
If a terminal is lost or stolen, use the portal to restrict access and review the device before restoring it.
Open the portal on any browser, click the terminal you've lost.
Turn on Lock Device on the terminal's page. An online terminal locks at once, and the portal tells you if it could not be reached. Switching the terminal to not operational stops it signing in or syncing.
Once the lock is applied, POS Velocity access is restricted until an authorized recovery action is completed.
When the terminal is recovered, an authorized user can review it and restore access from the portal.
Roles set what each person can do, and employees can be bound to a site. Administrators see every location of the account.
Card-present payments are read by the payment app on the PAX terminal, not by POS Velocity. POS Velocity keeps masked card details — the last four digits, the brand, and the approval references — and never the full number or security code. For a security questionnaire, contact us.
A payment link opens a hosted page where the customer types the card and completes a 3-D Secure check. The card is passed to the payment gateway and dropped; only a masked number is kept.
You can lock the terminal from its page in the portal. An online terminal locks at once, and you can also switch it to not operational to stop it signing in or syncing. An authorized user can review and restore it after recovery.
Yes. Terminals and the portal connect to POS Velocity over HTTPS.
Access is scoped by account and role, and employees can be bound to a site. Administrators see every location of the account.
Tell us what your review needs — card handling, access controls, change history, lost-device controls — and we'll answer in writing.