Under your brand
Your domain, every channel
With White Label the 7Feedback page and the system emails are served from your own domain. The printed QR, the follow-up pages and the chat-bot's web page 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
Notifications that keep going
Every new review, from any channel, is emailed to the business owner, the Admins and users with CRM access. A negative rating on the printed QR or a POS also sends an immediate Telegram message to those of them who have Telegram linked.
These emails do not count against the account's email allowance and are sent even when it is used up. Only an account that sends through a Branded sender has them counted, like every email it sends, and even there they are never held back.
So switching collection on needs no email setup first: the business hears about every review from the start.
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 needs no integration at all. Your own POS can ask through the Integration API if you want the question on its screen.
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 — the printed QR, the follow-up pages and the chat-bot's web page 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.