Under your brand
Your domain, every channel
With White-label the 7Feedback page and the system emails are served from your own domain. Table QR, receipt, terminal, kiosk and bot all resolve to your address, so the customer of your merchant never sees ours.
For a terminal fleet sold under an acquirer's brand this is a condition of the deal rather than an upsell, and it is treated that way commercially.
At a glance
- What is served from you
- The feedback page and the system emails
- Which channels
- All of them — there is no exception
- Who needs it most
- Acquirers, POS vendors, franchise networks
- Commercials
- Agreed per deal, with volume terms
Updated
What the brand boundary actually covers
Four surfaces the merchant's customer can see, and where each one comes from once White-label is on.
The feedback page
Served from your domain in every entry point, including the printed codes that were produced before the change.
System emails
The notification a merchant receives comes from your domain through your sending method, not from a name they do not recognise.
One brand, many owners
A franchise network keeps one domain and one look while the locations underneath are separate legal entities.
Nothing leaks in a screenshot
A merchant showing their own manager the page is showing your product, which is the point of the arrangement.
Say this out loud
The one setup that looks broken while being perfectly configured
Feedback notifications go out through the account's active email sending method — the same one the account uses for everything else. That is deliberate, and it has one consequence worth naming before a deal, not after.
On an account with no email sending configured, the default state is that no emails are sent at all. Switch feedback collection on there and the account will collect ratings and receive nothing, with every other setting correct.
So when the module goes onto that kind of account, the sending method is part of the checklist. It is the only scenario in which the product looks dead while working exactly as designed.
Partner 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 the size of the estate
Volume terms, White-label and billing for acquirers, POS vendors and franchise networks are set per deal.