PACTVERITYAll resources

35 / Verification badge

Turn each public receipt into inspectable distribution.

Every voluntarily published receipt receives a share card and a receipt-specific SVG badge. External sites can embed the badge and link directly to the bounded evidence record.

FormatSVGReceipt-specificYesBacklink targetEvidence
No generic endorsement:A badge exists only for a valid public receipt summary. It does not certify the publisher, independently observe the evidence, prove adoption or guarantee service quality.

01 / Publish

Create, verify and voluntarily publish a bounded receipt summary.

  1. 01

    Create a receipt

    Run explicit criteria and supplied evidence through the Proof Engine.

  2. 02

    Verify consistency

    Recalculate the canonical SHA-256 commitment and check every deterministic result.

  3. 03

    Publish the summary

    Only digest, outcome, engine version, check counts, signature status and timestamps enter the public ledger.

  4. 04

    Copy the badge

    The public receipt page generates the exact image and evidence-link HTML.

02 / Embed

Use the receipt-specific code—never a decorative trust mark.

<a href="https://pactverity.com/receipts/RECEIPT_SHA256" rel="noopener">
  <img src="https://pactverity.com/api/v1/public-receipts/RECEIPT_SHA256/badge"
       alt="Verify this PactVerity receipt" width="330" height="72">
</a>

The image endpoint returns 404 until the exact receipt digest exists in the public ledger. That fail-closed behaviour prevents an unrecorded badge from implying verification.

03 / Share card

Use a native evidence card for social and editorial contexts.

Each public receipt also exposes a 1200 × 630 SVG card for link previews and native uploads. The card includes the digest, result, check counts and evidence limitation.

Create a real record

Run the Proof Engine and publish a privacy-minimised summary.

Open Proof Engine

04 / Installation checks

Test the evidence link, not just the image.

  1. Generate and verify a receipt in the Proof Engine. Publishing is optional; do not publish sensitive service evidence.
  2. After a public summary exists, open its receipt page and copy its generated HTML. The digest in the image URL and evidence URL must match exactly.
  3. Open the evidence link in a separate session and inspect the digest, scope, engine version and observation time. A green image alone is not evidence of a current service measurement.
  4. For a negative test, change one digest character to an unrecorded digest. The badge endpoint must return 404; do not replace a missing badge with a decorative passing badge.
  5. If the badge or evidence endpoint becomes unavailable, display “Evidence unavailable” on the embedding site. Remove the embed if it no longer represents the claim being made.

Historical receipts are not continuously monitored certifications

A stored receipt describes its recorded inputs and rules. It does not automatically expire, revoke a publisher, monitor future service quality or certify an organisation. Superseding a result requires a separately identified receipt and a clear explanation; an old valid digest is not a fresh measurement.

Inspect the API contract → · Review the reproduction procedure →