Verify

Verify the receipt, not the document packet

Public verification surface for Formara receipts. Verification is independent, deterministic, and free.

Verify a live receipt Open public verification

Anyone can verify a Formara receipt without reopening the underlying document packet.

Verification is reproducible across environments, not dependent on the issuing system.

Public verification artifacts

Deterministic verification flow

Verification is always free

Why this exists

Verification should be
public, not procedural

Compliance trust should not depend on reopening private document packets or repeating issuer-controlled review.

A reusable receipt only matters if counterparties can verify it independently.

Verification must produce the same result for the same receipt, regardless of who performs it.

Public verification is what turns receipts from a claim into a trust surface.

This is the point where compliance starts behaving like infrastructure.

What gets verified

A deterministic verification result

Verification recomputes the receipt, validates the signature, and enforces deterministic replay against the same rulepack result.

Verification is performed against public verification artifacts, canonical receipt hashing, the published signing key registry, and the rulepack-bound receipt outcome.

Verification can include transparency inclusion and proof consistency as part of the public trust surface.

The result is not inferred from a PDF packet. It is derived from the receipt and its verification material.

Deterministic replay

The same receipt should reproduce the same verification result across environments

Canonical hash match

Recomputed against the canonical verification artifact and compared to the signed result

Signature + rulepack integrity

Checked against the published signing key registry and bound to a fixed rulepack result

Verification preview

A live public verification object

Start with a real receipt. Verify the same result that retailers, operators, and counterparties can check independently.

Verification result

US cosmetic safety requirements (MoCRA)

The same receipt should always produce the same result.

Rulepack

US-COS-MOCRA-BASELINE@2026-03-03

Verification result

PASS

GTIN

99177034731593

Receipt ID

r_05c58b2440e9...e2b3f140

Verify this receipt

Public verification can occur without reopening the underlying document packet.

Verification invariant

Same receipt = same verification result

If two parties produce different results for the same receipt, one of them is wrong.

Failure detection

Verification should fail
when trust breaks

A public verification surface is only credible if invalid, tampered, or inconsistent receipts do not pass silently.

Integrity failure

Tampered receipt content or a canonical hash that no longer matches the signed result.

Authenticity failure

Invalid signature or unknown signing key in the published key registry.

Determinism failure

Non-deterministic replay or engine mismatch for the same receipt and bound rulepack result.

Inclusion failure

Missing or inconsistent transparency proof where inclusion is expected as part of the trust surface.

Verification is not a styling layer. It is a trust boundary.

How to use it

Start with a receipt ID
or GTIN

Enter a receipt ID or GTIN in the public verification surface to retrieve and verify the associated result.

Receipt ID is the direct path to a specific verification artifact.

GTIN can be used to discover associated public receipts where available.

Retrieve the public verification artifact

Recompute the canonical receipt hash

Verify the signature against the published key registry

Compare the result against the bound receipt and rulepack outcome

Verification happens on the dedicated public surface, not inside a closed workflow.

Open public verification

Public trust surface

Verify a real Formara receipt

Start with a live example or open the public verification surface directly.