Partner track
A second subscription on hardware you already placed
Merchants running a terminal estate you deployed can switch feedback collection on with no new device, no new rollout and no second application on the fleet. For the acquirer it is margin on an estate that is already paid for.
For a terminal channel sold under your brand, White-label is a condition of the deal rather than an option — and it is treated that way in the commercials.
At a glance
- Applications on the fleet
- One — feedback is a mode of the Scanner
- Certification
- None: it sits outside the payment flow
- Card-linked recognition
- Live with a payment partner, needs PAR
- PAN
- Never used and never hashed
Updated
The four questions your team will ask
In our experience they arrive in this order, and none of them is about feedback.
What do we certify?
Nothing new. The application is installed beside your others and never enters the payment flow, so no payment-side certification applies.
How many packages?
One. Feedback collection is a mode inside the existing Scanner APK, so you version and support a single application across the estate.
Whose brand does the merchant see?
Yours. With White-label the feedback page and the system emails are served from your domain in every channel.
What happens to card data?
Nothing. The card number is never used and never hashed; the QR carries an opaque session id, and PAR is not PAN.
Card-linked recognition
Live, with one partner, under real conditions
The flow is built and running with a payment partner. The single question that decides whether it works on your estate is whether the stack can return PAR or a stable token at the moment of the transaction.
The constraints travel with the claim, every time it is made: PAR is not universal, the fallback is a token stable within one acquirer, joining across acquirers needs PAR, enrolment is the moment of consent, and EMVCo and scheme rules are confirmed with you or the BIN controller.
Tap-to-collect over Apple VAS or Google Smart Tap is a different mechanism and is available on request, with certified terminals and key provisioning. A live card-linked flow is not evidence that VAS is live, and we do not present it as one.
Questions from acquirers
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.
Can franchisees be billed separately?
Today a network's locations are paid for through the partner's access codes, and separate franchisee billing is an early invitation for selected partners rather than a released feature. What is available now is one branded domain, one set of system emails and analytics that roll up across locations run by different legal entities.
Next step
Send us the estate and the stack
Terminal count, markets, and whether PAR is available. That is enough for a commercial number and a straight technical answer.