Nothing for the cashier
No prompt to read out, no card to hand over, no second device on the counter.
Channel
The question on the terminal itself
Terminal Mode runs the 7Stamp Scanner application in a dedicated mode on a standard Android payment terminal. The rating appears after the transaction, on the screen the customer is already looking at.
It sits outside the payment flow, so it changes nothing about how a payment is taken and needs no payment-side certification.
At a glance
- What it is
- A mode inside the existing Scanner APK
- Hardware
- Standard Android payment terminal
- Certification
- None — it never touches the payment
- For fleets
- One application to certify and support
Updated
Why it goes onto a fleet without a fight
The objections an acquirer raises are about certification, versioning and support — not about feedback.
01
One application, not two
Feedback collection is a mode of the Scanner APK, so the fleet carries one package, one version and one support line.
02
No certification path
The application is installed beside the others and never enters the payment flow, so no payment-side certification applies.
03
No new device
The terminals are already deployed, already powered and already in front of the customer at the right moment.
04
A second subscription
For an acquirer, the same estate earns twice: merchants running Terminal Mode can switch feedback on with no rollout at all.
On screen
After the payment, not during it
The payment completes exactly as it does today. Only then does the terminal ask the question, take one tap and offer the same two options as every other channel.
Attribution for free
The terminal is a staff login, so the location and the workstation come with every submission.
Deeper integration on request
Partners who want the question inside their own payment screens can integrate through the API.
Where the stack allows it
Recognising a returning customer without personal data
Where the payment stack exposes PAR or a stable token at the moment of the transaction, the same card can be recognised on the next visit. This is built and running with a payment partner — not a roadmap item, and not a claim that it works on every stack.
The card number is never used and never hashed. The QR carries an opaque session id, the enrolment QR is the moment of consent, and PAR is not stored for a card that never enrolled. EMVCo and scheme rules are confirmed with the acquirer or BIN controller.
The purpose is narrow: recognise the same person well enough not to ask them too often. Without PAR, the fallback is a token stable within one acquirer; joining data across acquirers is only possible through PAR.
Questions from terminal fleets
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 runs on your terminals
If it is Android and it is already in the field, the answer is usually that nothing new has to be deployed.