Checked instantly on submission
The system checks that guest's submission frequency, receipt age, and receipt value before any points are awarded.
Features
Guests photograph their own receipts to earn points — so what about fraud?
Control layers keep self-serve points earning from becoming a loophole: hourly and daily receipt limits, receipt age, value thresholds, brand-wide image matching, and risk-tiered actions.
GUARD RAILS
Updated August 2026 — This is the first question every venue owner asks, and the answer isn't 'trust the guest.' Every receipt submission runs through multiple control layers: hourly and daily submission limits, receipt age, value thresholds, image matching against every receipt already submitted across the brand, and automatic action based on risk level.
Updated: 2026-08-09
Quick facts
- Suggested starting limit
- 3 receipts per hour and 10 per day per guest — adjustable.
- Image matching
- Checked against receipts submitted in the last 90 days brand-wide.
- Other thresholds
- Receipt age and value ceiling/floor — set by your venue.
- Action
- Critical: blocked. High: held for review. Medium: points awarded, admin notified.
How it works
Brand-wide image matching
New images are compared against receipts submitted in the last 90 days across every branch. A match flags both submissions, not just the later one.
Risk-tiered action
Critical risk is blocked instantly. High risk is held for review. Medium risk gets points awarded but flags an admin to check.
Integrity controls on customer receipt scans
| Control | What it catches | Setting |
|---|---|---|
| Rate limits per hour and per day | A single member can only submit so many receipts in an hour, and so many in a day. This caps how fast any one account can claim, whatever else it tries. | Suggested start: 3 per hour, 10 per day |
| Receipt age | A bill older than your limit is rejected, so nobody stockpiles receipts and claims them in a batch later. | Configurable per venue |
| Value thresholds, upper and lower | Bills below your floor are ignored so trivial claims do not farm points, and bills above your ceiling are held for a human look. | Configurable per venue |
| Duplicate image matching across 90 days, brand-wide | Every submitted photo is matched against submissions from the whole brand for the last 90 days. When the same image turns up twice, both submitters are flagged — not just the second one. | Similarity threshold configurable per venue |
| Repeated failed-scan detection | A member who keeps sending images the system cannot read is usually probing to learn what gets accepted. That pattern is flagged on its own. | Always on |
| Risk-tiered actions | Severe risk is blocked outright. High risk is held pending approval. Medium risk goes through but notifies an administrator, so you see the pattern without punishing the customer. | Always on |
Which venues this fits best
- Venues that want self-serve points earning without losing control of reward costs.
- Multi-branch chains, where the same receipt could otherwise be submitted at two locations.
- Venues with high average bill sizes, where every miscredited point is a real cost.
Check your own venue
- What currently stops the same receipt from being pointed twice at your venue?
- If one guest submitted 20 receipts in one evening, who would catch it?
- Does your venue keep a log to trace back a suspicious points award?
What this does not solve on its own
- Thresholds set too tight hold up genuine guests for review — every threshold is adjustable, and the review queue is visible so your venue can clear it same-day.
- Thresholds set too loose barely do anything — so a baseline set of checks always runs and can't be switched off, even if you loosen the rest.
- No system catches 100% of cases — the goal is keeping fraud cost below the value of a wider member base, and every point award is logged for tracing.
Questions owners ask
What happens if the same receipt is submitted twice?
The image is matched against every receipt the brand has received in the last 90 days. A match flags both submissions and routes them to review instead of awarding points.
How many receipts can one guest submit?
The suggested starting default is 3 receipts per hour and 10 per day per guest. Your venue can adjust it to match its real traffic.
What about old receipts or ones with a tiny value?
There are configurable receipt-age and value thresholds, upper and lower. Receipts outside those thresholds are rejected or routed to review, depending on setup.
What if a guest keeps submitting failed image scans?
The system tracks each guest's chain of failed scans. An abnormal streak is flagged as probing behavior and that account moves to a higher risk tier.
Who decides whether to block or allow a submission?
The system sorts submissions by risk tier, but your venue keeps final say. Critical risk is blocked automatically; High sits in a review queue; Medium gets points awarded with an admin notification.
The PEKO ecosystem
PEKO and LOOP are two products from the same company. PEKO is the AI retention layer and runs alongside the POS you already use. LOOP is the AI-native POS that covers operations: recipe-level inventory, staff shifts, table plans and the kitchen display. Each works on its own, and run together they share one dataset, so nothing has to be entered twice. See PEKO + LOOP in one ecosystem