Skip to content
ponch
← Back to features

Real-time stamps

Stamp from any phone, with no app and no reader

There's no app to install, no NFC reader to buy and no terminal to wire up. You stamp from the browser on the phone already in your pocket.

  • Stamp from any phone or computer — nothing to install
  • No NFC reader, no terminal, no point-of-sale integration
  • Every stamp logged with who, where and when
  • Your customer's pass updates instantly

The number one reason a digital loyalty program fails isn’t the reward or the card design. It’s that stamping takes too long. If the process adds fifteen seconds per customer during the morning rush, your team quietly stops doing it in week two and the program dies on its own.

So stamping in Ponch has no hardware in the middle of it.

What you actually need

A phone with a browser. The one you already carry.

There’s no app to install at the counter, no NFC reader to buy, no terminal to rent, and no point-of-sale integration for somebody to build. You open your dashboard in the browser, scan the code on your customer’s pass, and that’s it.

Why we don’t hook into your point of sale

It’s the question we get most, and the answer is deliberate: stamping is separate from taking payment.

Tying it to the point of sale sounds better than it is. It means depending on which terminal you run, waiting on someone to build the integration, and having your loyalty program go down whenever your payment system does. Keeping them separate means your program works on day one, with the equipment you already have, no matter how you take money.

Who can stamp

Your team doesn’t need — and shouldn’t have — access to everything. You can grant stamping-only access: that person can give stamps and nothing else, with no view of your numbers and no way to touch the campaign settings.

And every stamp is logged: who gave it, at which store, at what time. The difference from a hole punch isn’t distrust, it’s that there’s a record. When the numbers look off one day, you can check instead of guess.

What it looks like during the rush

  1. Your customer opens their pass in their wallet while they wait.
  2. You scan the code.
  3. Their phone lights up with the new stamp.

That’s the whole process. You don’t ask for a name, a phone number, or to spell out an email — the pass already knows who they are — which is why it fits inside the time it already takes to hand over an order.

What comes next

On the other side of the counter, what makes this work is where the card lives: in Apple Wallet and Google Wallet, not in an app your customer would have to download.

Frequently asked questions

Do I need to buy any hardware?

No. You stamp from the browser on any phone or computer you already own. The QR code on the counter is a sheet you print yourself.

Do I have to connect it to my point of sale?

No, and that’s a design decision rather than a missing feature. Stamping is separate from taking payment, so you don’t depend on your terminal or on someone building an integration.

Can anyone on my team stamp?

Yes, with exactly the right permission. You can give someone stamping-only access, so they can’t see or change how your program is set up.

How do I stop staff giving stamps away?

Every stamp is logged with who gave it, at which store, and at what time. This isn’t standing suspicion of your team — it’s that, unlike a hole punch, there’s a record you can actually check.

What if the internet goes down in the store?

Stamping needs a connection, the same as taking card payments. If your store drops offline for a while, the practical move is to note it down and stamp afterwards, or use mobile data on the phone you stamp from.