Solution
The customer who never comes inside
Most of a station's visitors pay at the pump, take the receipt and drive away. The terminal in front of them is the only screen they ever see, which makes it the only place a question can be asked.
The estate is already deployed and already Android. Terminal Mode installs beside the applications on it, outside the payment flow.
At a glance
- Usually first
- Terminal Mode on the existing terminals
- Second
- Stickers in the washrooms and shop
- Attribution
- One staff login per island or per shop till
- Scale that suits
- Faces — one tap, gloves, weather, hurry
Updated
What a station finds out
Fuel is a commodity, so everything a driver chooses a station for is operational — and all of it is invisible without a channel.
The pump that is broken
A driver will not walk inside to report a card reader that took three attempts. They will tap one face on the way out.
The washroom
A sticker by the door is the most-used code on most stations, and it usually calls cleaning rather than rates the visit.
Night shift versus day
Every submission carries the staff login and the time, so a pattern that only happens after midnight is visible as one.
Nothing added to the forecourt
No screens, no cables, no certification work. The terminals are already there and already running Android.
What a network rolls out
For an operator with an acquirer relationship this is usually a fleet decision rather than a per-station one.
- 01 Switch Terminal Mode on across the estate — one application, already deployed, no second package to certify.
- 02 Give each island or shop till its own staff login so the ratings arrive attributed to a position.
- 03 Add printed codes where there is no terminal: washrooms, the car wash, the air line, the coffee counter.
Common questions
Do we need to integrate with our POS?
No. The terminal application installs next to your other Android apps and does not touch the payment flow, so it needs no payment-side certification. A printed QR or a fiscal receipt QR needs no integration at all. A deeper API integration exists for partners who want the question inside their own payment screens.
Can we run it under our own brand and domain?
Yes. With White-label the feedback page and the system emails come from your domain in every channel — table QR, receipt, terminal, kiosk and bot alike. For a terminal fleet sold under an acquirer's brand this is a condition of the deal rather than an option.
Is card-linked recognition actually live?
It is built and running with a payment partner, on stacks that expose PAR or a stable token at the moment of the transaction. It is not a claim that it works on every stack: without access to PAR the fallback is a token stable within one acquirer. The card number is never used and never hashed.
How many applications go onto the terminal fleet?
One. Feedback collection is a mode inside the existing 7Stamp Scanner APK, so an acquirer certifies, versions and supports a single application across the fleet. A second application is not published and is not offered.
Next step
Tell us what is on your forecourt
If the terminals are Android and already in the field, there is usually nothing to install and nothing to certify.