Returning guests
Recognise the guest who came back, without a sign-up wall.
A guest can become a recognised member straight from the payment screen — no separate account, no password. When you need more certainty, a one-time passcode by SMS confirms who they are.
—
Three ways to know your guest.
TabbPay separates two things most systems tangle together: identity (who is this) and assurance (how sure are we). A guest who just paid can be recognised from that payment alone — enough to earn points. Sensitive actions, like charging to an account, ask for an SMS one-time passcode that lifts them to verified.
You pick the model in Business profile. An open or closed venue can run OTP only. A commercial venue can run frictionless enrol-at-payment with no OTP, or both — verified loyalty — when redeeming or charging to account should require a confirmed identity. A global kill-switch and a per-venue rail keep it under your control.
What is in this
Enrol at payment
The guest opts in from the payment-success screen. No download, no password, no form to fill in before they can order.
SMS one-time passcode
When assurance matters, a code by SMS (sent via AWS SNS) confirms the guest and unlocks charge-to-account and verified redemption.
Three business profiles
Open/closed (OTP only), commercial verified (OTP + enrol), or commercial frictionless (enrol only). Switch presets from the dashboard.
Capabilities gated by assurance
Each action requires a level of certainty, not just 'a token' — earning needs identity, charging needs verified.
Kill-switches you hold
A global switch and a per-venue rail mean you decide exactly how much verification each location asks for.