What is a review provenance certificate?
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
A provenance certificate is the public page for a single review: it shows the reviewer, rating, source and date, the transaction reference marked as attested or imported (or the UNLINKED seal when there is none), the moderation state, and the chain-of-custody timeline behind the review. Anyone can open it — from the verified widget — and see what the business's claim rests on. ReviewProof issues a certificate page for every imported review, verified or not; the honesty about the unverified ones is what loads the verified ones with meaning.
What is a provenance certificate?
A review provenance certificate is a published, per-review evidence summary: the review's identity and origin, its transaction backing or recorded lack of it, and the custody events it has passed through. Transaction-backed results under ReviewProof's provenance system publish the reference masked — the underlying record holds a SHA-256 hash and a masked form, never the raw reference — and a holder of the true reference can verify the match without any customer data being exposed.
A certificate persuades by what it admits
Read a good certificate sceptically and notice the admissions. The transaction reference is labelled attested or imported by the business — the certificate does not pretend an independent party witnessed the purchase. The moderation state is shown, so a kept negative reads as kept. An UNLINKED certificate states the absence plainly. These admissions are load-bearing: a page that concedes the limits of its own evidence can be believed about the rest. Compare the alternative — a badge that says 'VERIFIED REVIEWS' with nothing behind it — which asks for trust while offering nothing checkable, and collapses the first time a careful buyer clicks.
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.
Where certificates do their work
Certificates earn their keep at moments of doubt distributed across your whole presence: behind the verified widget on your own site, where each displayed review opens into its certificate; in a sales or partner conversation, where one link replaces a paragraph of reassurance; in vetting, where an examiner samples certificates the way an auditor samples invoices; and in a dispute, where the certificate is the public face of the deeper chain in the evidence pack. The sample report at ReviewProof's /provenance-sample page shows the format with fixture data, labelled as a sample — the same instinct: show the instrument, mark its limits, let it be examined.
ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.
Mistakes that undo the work
Linking certificates only for five-star reviews recreates gating at the publication layer — the widget rule (linked and kept or published) exists precisely to prevent selection by sentiment. Writing marketing copy that overstates the certificate ('independently verified!') contradicts the page itself, which honestly labels the reference as attested or imported by the business. And letting certificates exist but never linking them from anywhere real buyers go wastes the instrument.
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.
Worked example: a certificate that won a contract clause
A fictional worked example, written to show the numbers and the decisions in practice.
A commercial cleaning firm bidding for a facilities contract was asked, in the tender, how it substantiated its testimonial claims — a question written by a procurement team that had been burned by fabricated references before. The firm linked three provenance certificates from its verified widget: each showed a transaction-backed review, the masked contract reference, the date, the source, and a moderation state of kept. One linked review was four stars with a complaint about scheduling inside it — kept, unedited. The firm won the clause and then the contract; the buyer cited the four-star certificate specifically: 'Anyone can fake five stars. Nobody fakes a scheduling complaint with a contract reference attached.'
Your five-action checklist
- Open three of your own certificates and read them as a sceptical buyer
- Confirm each shows source, date, transaction state and moderation state
- Check an UNLINKED certificate states the absence plainly
- Link the verified widget so every displayed review opens its certificate
- Use the sample provenance report to train staff on what the page proves — and does not
Frequently asked questions
What does a provenance certificate show?
Reviewer, rating, source, date, the transaction reference marked attested or imported (masked on published results), the moderation state, and the chain-of-custody timeline.
Does the certificate expose customer data?
No. Published results expose no reviewer contact data and no raw transaction reference — only a masked form, with the hash held in the record for verification.
Can anyone verify a certificate's transaction claim?
A holder of the actual transaction reference can present it; it is hashed and compared against the retained hash. A match verifies the backing without the reference ever being stored or shown.
Do UNLINKED reviews get certificates?
Yes — showing an UNLINKED seal and the absence of a link. The certificate system covers every imported review; only the widget restricts itself to verified ones.
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 does transaction-backed review provenance mean?
- 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.