PACTVERITYBuy / swap PVTY

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