No order id, no page
Without the order id the rating is stored and no follow-up page is offered.
Partner track
The rating screen on your own POS
For a POS connected through the Integration API, the rating screen comes with each operation. When the POS sends the order id, every option on the scale carries the page it leads to, and the POS shows its QR after the tap.
A negative rating leads to a private page for the manager, a neutral or positive one to a page that can offer a Google review. The pages are ours, so nothing about them has to be built in your product.
At a glance
- What you integrate
- The rating screen, then a QR you already render
- Without the order id
- The rating is stored, no follow-up page
- What travels with it
- Terminal, shift, cashier, receipt amount
- Under your brand
- White Label serves the page from your domain
Updated
What the POS shows
Four things the rating screen does on a POS, all through the same API.
01
The rating screen
Comes with each operation, on the business's scale. A business that issues no Stamp cards can still ask on its POS.
02
The follow-up QR
With the order id, the option the customer taps carries its page, and the POS shows the QR of it.
03
Spaced out by the product
The page with the Google button goes to a customer the POS identifies at most once in ninety days; without an identifier, every fifth purchase at a terminal, not more often than every fifteen minutes, at most twenty times a day.
04
The manager hears at once
A negative rating sends an immediate Telegram message with the Staff Login, terminal, shift, cashier, time and amount.
What the rating carries
The purchase context travels with the rating
A rating from a POS carries the terminal, the shift, the cashier and the receipt amount, and the journal filters by them. That is what separates a usable report from a stream of anonymous stars.
A printed QR needs nothing
A Staff Login's printed QR asks with no integration on your side, beside the POS or instead of it.
Attribution is automatic
The API integration is a Staff Login, and ratings that come with the order id carry it.
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 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 what your POS shows
Which screen the customer sees at payment, and whether you send an order id. From that we can tell you exactly what the integration is on your side.