Mosey Tap: Everything a Customer Is Owed, on One Screen

A customer walks up to your counter. They are owed a free coffee on their loyalty card, they have a table booked for Thursday, and there is a collection order with their name on it. Your till knows about none of that, and neither does the person serving them.

Mosey Tap puts all three on one screen, in the two seconds it takes somebody to tap their phone on the counter.

It works with the till you already have

This is the part venues usually expect to be the catch. It is not.

Tap does not take payments, does not need to see your till, and does not care what you sell things through. It runs on a phone, a tablet or the computer already behind your counter, in a browser. If you are on a card terminal from your bank and a till you bought in 2019, Tap works exactly as well as it does for a venue running everything on Mosey.

What it adds is the customer layer that almost no till has: who this person is to you, and what you already owe them.

How it works

1. Stick a tag where people already stop. A Mosey tag is a small NFC sticker. The counter edge is the obvious place; the card machine, the tables and the door are all useful too. Each tag has its own code, so your reporting can tell a door tap from a counter tap.

2. The customer taps, or reads out a code. Tapping opens their card on your screen. If their phone is in a bag, they read out the six-digit code from the app and your staff type it. Same card either way.

3. Their card opens on your Counter screen. One card per customer, live for ten minutes. On it: their loyalty standing with you, any reward that is ready, a table booked today, an order waiting to be collected, an event ticket, a food trail stamp, a membership perk.

4. Staff confirm what is actually happening. Add the visit. Redeem the reward. Mark the order collected. Seat the booking. Each is one press.

A tap is a request, never a grant

This is the rule the whole thing is built on, and it is worth being explicit about because it is what makes Tap safe to put on a public counter.

Tapping a tag does not give anybody anything. It opens a card. Your staff decide what happens, and nothing changes until they press something. A customer cannot tap their way to a free coffee any more than they could take one off the shelf.

There are exactly two exceptions, both off by default, both switched on per item, and both chosen deliberately:

• Checking themselves in to an event, at a door tag, within an hour of the start — because a queue of ticket-holders at a door is the one place where a member of staff pressing a button per person is the bottleneck.
• Stamping a food trail stop, but only once their phone confirms they are within 200 metres of you — because a trail is a walk between venues and the whole point is that it keeps moving.

Everything else waits for a person.

Undo, and why it restores rather than recalculates

Staff press wrong things. A busy counter guarantees it.

Every action records what it changed, and undo puts back exactly that — the stored snapshot, not a figure recalculated from your current settings. That distinction matters more than it sounds: if you edit a stamp card between the credit and the undo, a recalculation would restore a number that was never true. After fifteen minutes an undo needs a manager and a reason, so a mistake stays fixable and a habit stays visible.

One thing is deliberately not undoable. Once an order is marked collected the customer has been told and the visit credited, so the remedy is a refund rather than a reversal, and the screen says so before the press.

What it tells you that a till cannot

Because every tap and every action is recorded against a customer and a tag, you get answers a payment terminal has no way to produce:

• How many of the people who tap actually get served, and where they are dropping off
• Which tag gets used — whether the one on the door is earning its place
• Which of your regulars have stopped coming in
• Whether one member of staff is crediting far more than the rest, measured against your own venue's normal rather than somebody else's

That last one flags rather than blocks. A cross-venue threshold would fire constantly on the busiest venue and never on a quiet one, so the comparison is a venue against itself.

What it costs

There is no separate charge for Mosey Tap.

What a tap triggers carries its normal rate, and nothing more:

• A loyalty visit — 1% of the spend the programme rewards, capped at €150.00 of commission per venue per month, then 0.4% above that
• An in-store payment with Mosey Pay — 1.5%
• Confirming a booking, seating a table, marking an order collected — nothing

If you never run a loyalty programme and never take a payment through Mosey, Tap costs you nothing at all and still tells your staff who is standing in front of them.

A worked example

A café with 400 customers a week puts one tag on the counter and runs a frequency programme: ten visits, one free coffee.

Say 120 of those customers tap. Each is a visit credited without anybody stamping a card, and roughly twelve free coffees a week go out, on drinks that cost the café about €0.70 each to make. The commission Mosey takes is 1% of the spend those visits rewarded — on a €4.00 coffee, four cent a visit.

The café's owner also finds out that 31 of their regulars have not been in for a month, and can say something to them about it.

What it connects to

Tap is the front door to most of the rest of Mosey:

• Run a loyalty programme — the visits and rewards a tap credits
• Take payments in store with Mosey Pay — 1.5%, and every payment counts as a visit automatically
• Reservations and deposits — the booking that shows on the card
• Run a food trail — the stamps a tap can give
• What Mosey costs — every rate on one page

If you are starting from nothing, get discovered on Mosey comes first: claim your listing, then put a tag on the counter.