Merchant data separation
Each merchant sees only their own customers, programmes, rewards and reporting. Shared counter devices do not expose wider customer history.
Security
Merchant trust and customer privacy are built in.
perkpass. keeps each merchant's loyalty activity separated, prevents reward redemption by guessed email address and records sensitive actions in an audit trail.
One-time reward references
Available rewards use opaque references and one-time redemption, so knowing a customer's email address is not enough to spend their reward.
Audit and reversal history
Corrections create clear reversal records. Loyalty history stays explainable instead of being quietly overwritten.
Operational control
Controls that match real counter work.
Owners need administrative control; staff need fast operational tools; customers need privacy. perkpass. keeps those contexts separate so a counter terminal does not become an open owner account.
Verified accounts
Customer history is shown only after email ownership is verified. Merchant users are tied to business permissions, not just hidden navigation links.
Payment safety
Subscription and invoice management is kept away from the counter workflow, and raw card details are never handled inside perkpass.