What does transaction-backed review provenance mean?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
Transaction-backed provenance means a review is tied to a specific transaction by a controlled reference: the business attaches the order, invoice or booking reference, ReviewProof stores only its SHA-256 hash and a masked form (the raw reference is never stored, and email-shaped references are refused), and the published provenance result can be verified by anyone who holds the reference and presents it. A review without backing publishes as unverified — never dressed up as more than it is.
What is transaction-backed provenance?
Transaction backing is the link between a review row and a transaction record in the business's own systems, established by a reference the business controls. Its published form is deliberately minimal: a status (backed or unverified), a masked reference, the kind of source evidence retained, and timestamps for attachment, publication and last verification. Its verification form is a comparison of hashes — the presented reference is hashed and matched, never stored or displayed — so proof travels without customer data travelling with it.
Why hash-and-mask is the right shape for proof
A published order number is a privacy leak and a forgery invitation: anyone can copy it onto a fabricated review. A hash inverts the problem. The business proves it held the reference at attachment time (the hash could only come from the reference), the public sees only a masked fragment (enough to recognise, useless to reuse), and the one person who can complete the verification is the person who legitimately holds the reference — the customer, or an examiner the customer or business authorises. Even the input is policed: email-shaped references are refused, because an email address in the reference field is personal data wearing the wrong label, and the system declines to store it in any form.
The FTC fake-review rule, 16 CFR Part 465, has been in force since October 2024. It bans fake and AI-generated reviews, buying positive or negative sentiment, insider reviews without disclosure, review suppression, and misrepresenting review sites as independent. ReviewProof was built as the evidence layer for that rule: imported reviews carry a provenance chain — import, transaction link, analysis, moderation decisions — and the Pro evidence export includes the moderation log with negative reviews kept, which is how a business shows suppression did not happen. Proof, in this design, is a record anyone can inspect, not a badge a business awards itself.
Backed is a claim about a transaction, not about a text
Precision here protects everyone. Backing establishes that a specific transaction exists in the business's records and is attached to this review. It does not establish that the review's opinions are fair, that its author is the transacting customer in every metaphysical sense, or that the text carries no risk signals — a backed review can still be flagged for wording patterns, and the signals remain in the record beside the backing. Holding both ideas at once — backed, and still audited — is what separates provenance from the badge economy, where one word ('verified') is asked to mean everything and ends up meaning nothing.
In practice the routine takes minutes. Export or copy the reviews for the location, import them into ReviewProof by CSV or paste, and read the report top-down: total rows, flagged count, risk score, then the per-signal breakdown. Open the flagged rows themselves — the report traces each signal to its row precisely so you can do this. Decide moderation openly (kept, published, or flagged internally; there is no delete), check which reviews carry a transaction link, and publish or refresh the verified widget so the public claim matches the audited record. On Pro, export the evidence pack while the file is fresh.
Mistakes that undo the work
Attaching references the business does not actually hold — copied from a platform page, guessed from a date — is fabrication with extra steps, and hashing does not launder it. Publishing unmasked references anywhere (a screenshot, a PDF) defeats the mask; treat the raw reference like a password for the transaction. And describing backed reviews as 'FTC-approved' invents an endorsement no regulator gives: the backing is your evidence, presented honestly, nothing more.
Enforcement and platform action both turn on records, not intentions. A business that can produce the underlying row, its source, its date, its transaction link or the honest absence of one, and every moderation decision taken about it, is in a different position from a business holding only a star average. That is why ReviewProof never silently deletes: imported reviews default to kept, moderation is limited to kept, published or flagged internally, and every decision is written into the chain of custody. The evidence pack (a Pro and Agency feature) assembles that chain so it can be handed over as one document.
Worked example: verification, performed by a stranger
A fictional worked example, written to show the numbers and the decisions in practice.
A equipment-hire firm published a transaction-backed provenance result for a five-star review (the sample format is visible on ReviewProof's sample page with fixture data). A corporate client's auditor, testing the claim, asked the firm to demonstrate verification live. The firm's manager opened the published result — masked reference, check code, evidence kind 'order system export' — and the auditor presented the hire reference from the client's own copy of the paperwork. The system hashed it, matched it against the retained hash, and confirmed. At no point did the firm's system reveal the reference, the reviewer's name or the review text to the result page. The auditor's note was one line: 'Backing verified by presentation; no personal data exposed.'
Your five-action checklist
- Attach references only from records your business actually holds
- Confirm the stored form is hash plus masked reference — never raw
- Test verification by presenting a reference you hold, as a stranger would
- Keep source evidence with the review, labelled by kind, unpublished
- Publish unbacked reviews as unverified; never round them up to backed
Frequently asked questions
What part of the transaction reference is stored?
Only a SHA-256 hash and a masked form. The raw reference is never stored, and email-shaped references are refused at input.
How does a third party verify a backed review?
By presenting the transaction reference on the review's provenance result. It is hashed in the request and compared to the retained hash — never stored or shown.
Does the published result show the review text or reviewer name?
No. The result exposes no reviewer name, no review text and no full reference — status, masked reference, evidence kind and timestamps only.
Can a backed review still carry risk signals?
Yes. Backing speaks to the transaction; the wording analysis still runs and its signals stay in the record. The two layers answer different questions.
Keep reading
Related guides from the ReviewProof library:
- What does the FTC fake-review rule actually ban?
- Why does keeping negative reviews protect your business?
- What should an evidence pack for a review dispute contain?
- What is a chain of custody for a customer review?
- What is a review provenance certificate?
- How do you audit your own reviews, step by step?
- How should you moderate reviews without suppressing them?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.