Points on every payment
Clover payment webhook awards points automatically, idempotent per order, with your own point rules.
Feature
A Clover loyalty app that lives on the register.
Most loyalty products bolted onto Clover are a second screen, a second login, and a staff habit nobody keeps. This one runs on the Clover device your staff already touch every sale: type a phone number, see the balance, tap the reward, keep ringing. Points post themselves when the payment lands.
01 — At the counter
Four taps, inside the sale you're already in
- Look up by phoneThe number is the identity. No cards, no app download, no “what was my email again?” at a queue of three people.
- Only the rewards they can affordThe screen shows the balance and the rewards that balance actually unlocks. Staff never have to do points math, and nobody gets told no after being told yes.
- One tap puts the discount on the open ticketThe reward is applied to the order in front of you — not read aloud for someone to key in as a manual discount and get wrong.
- Free-item rewards find the itemA free-product reward is matched by SKU, then by item code, then by name. If the item is already on the ticket we discount that line; if it isn't, we add one unit and zero it. Exactly one unit — a free shaker never zeroes both shakers.
- Enroll in the same flowNew customer? Name, phone, done, on the same screen. SMS consent is a separate unchecked box the customer taps themselves, stored with source and timestamp.
- Points post on payment, not on memoryClover tells us the payment happened and the points land on the member record. Award is idempotent per order, so a retried webhook can't double-credit.
If a free-item reward can't be matched to anything in your inventory, the register says so and tells staff to hand it over manually. It does not report success and quietly apply nothing — a loyalty integration that lies about a redemption is worse than one that asks for help.
02 — Setup
The device authenticates itself. Nobody types a secret.
Most POS add-ons hand you an API key and a support ticket. Here the register does its own introduction: the app asks Clover which merchant this device belongs to, and we check that claim against Clover's API before trusting it — a merchant id by itself proves nothing, so the returned merchant has to match. Only then does the device get its own long-lived token, stored hashed on our side and tied to that serial number. Re-provisioning a device revokes the row the old one was using, and every register shows up in your portal settings with a delete button. A device that walks out the door is one click from useless.
Permissions are deliberately narrow: merchant read, orders read and write, payments read, customers read and write, inventory read. No employee data, no ecommerce, no inventory writes — selling an item moves your stock, we never edit it. We fixed that list before launch on purpose. Clover grants permissions at install time, so adding one later forces every merchant to uninstall and reinstall the app, which is a phone call to every store. Getting the set right the first time is not a detail.
Points, lookup, and redemption on Clover are live today. The register app itself is with Clover for App Market review, so if you're on Clover and you want it on your Station, the demo is where we tell you exactly where that stands and what runs in the meantime.
Lookup & redeem
Find a member, apply a reward to the latest open Clover order — from the portal or the kiosk.
The on-register app
Self-provisioning, lookup, enroll, one-tap redeem on the Clover device. Built and signed; awaiting App Market approval.
03 — In practice
One customer record, two systems that agree
The failure mode with any POS loyalty bolt-on is drift. Somebody fixes a misspelled name in the rewards portal, the Clover customer record keeps the typo, and six months later your receipts and your texts disagree about who this person is. When a member's name or email changes on our side, we push it back to the Clover customer record they came from. We never blank a field you filled in, and we never touch the phone number — that's the identity key, and rewriting it is how two people become one by accident.
What you get on top of the register is the part Clover was never going to build: SMS campaigns with carrier registration filed for you, lifecycle segments computed from real reorder behavior, a rewards catalog you control, and a counter kiosk for visits that don't come with a purchase. If you run more than one store, visits roll up per location so you can text one store's customers without double-texting the regulars who shop at both.
And if you're weighing this against the loyalty app your processor sells you: the honest comparison is on the Square Loyalty page, and the whole integration list — Shopify, Clover, and what's early — is on integrations. Pricing is published: $200/mo, 5,000 texts included, 2¢/text after, $500 one-time setup and migration, no contract.
04 — Questions
Straight answers.
Do I have to type an API key into the register?
No. The app asks Clover who the device belongs to, and we verify that answer against Clover's own API before we trust it — a merchant id on its own is not proof. The register then gets its own token, tied to that device serial, revocable from your portal. No merchant credentials ever sit on the device, and nobody at your counter is handed a secret to lose.
What Clover permissions do you ask for, and why?
Merchant read, Orders read and write, Payments read, Customers read and write, and Inventory read. Orders write applies the discount to the open ticket. Payments read is how points post automatically. Customers read and write keeps the member record and the Clover customer record in sync. Inventory read is only there so a free-item reward can find the item by SKU. We do not ask for Employees, Ecommerce, or Inventory write.
How does SMS opt-in work when someone signs up at the register?
Consent is an explicit box, unchecked, that the customer taps themselves, and it is recorded with its source and timestamp. If they do not tap it, we create the member with no marketing consent at all — enrolling somebody never quietly opts them into texts.
Can I keep using Clover for payments and still own my customer list?
Yes. Nothing here touches how you process cards. The loyalty program lives on your own subdomain in your own branding, and the member list exports whenever you want it.
05 — Next step
Bring your Clover setup to the call.
Twenty minutes: the register flow, the portal, a real campaign send, and an honest read on what connecting your Clover merchant would take.
$200/mo platform · 5,000 texts included · no contracts