One mechanic, many placements
There is no separate receipt product and no separate kiosk product — the same call returns the same link.
Partner track
One call, one link, anywhere you can draw a QR
For a POS, ERP, CRM or e-commerce platform the integration is small on purpose: your system asks the API for a link and encodes it into a QR code. Where that code appears is a placement, not a separate feature to build.
The page behind the link is the same one the terminal and the table tent open, so nothing about the customer experience has to be rebuilt in your product.
At a glance
- What you integrate
- A link request, then a QR you already render
- Placements
- Receipt, insert, kiosk screen, checkout page
- What travels with it
- Till, location, shift, time, receipt contents
- Under your brand
- White-label serves the page from your domain
Updated
Where your customers put it
Four placements, one mechanic. None of them needs a different endpoint or a different page.
01
Printed on the receipt
Receipt QR: your till requests the link at the end of the sale and prints it in the footer it already controls.
02
On somebody else's kiosk
A self-service kiosk shows the code on the post-purchase screen the customer is already looking at.
03
In the delivery bag
Delivery Inserts carry the same link on a printed card, with no courier integration at all.
04
On the checkout page
An online store shows the code or the link on the final screen, rating the order and the checkout together.
What the link carries
The purchase context travels with the code
A submission that came from a receipt knows the till, the address, the shift number, the time and the contents of the receipt. That is what separates a usable report from a stream of anonymous stars.
The fiscal route needs nothing
In fiscalised markets the customer can scan the tax authority's own QR instead, with no integration on your side.
Attribution is automatic
The API integration is itself a staff login, so every submission that comes through it is attributed to a location.
Integration 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
Send us where you would put the code
Receipt footer, kiosk screen, order confirmation. From that we can tell you exactly what the integration is on your side.