Sealed Attestations

Product declarations
that cannot be walked back.

A supplier statement held on the supplier's own server is not evidence. ProntoID binds a declaration to a verified legal entity and a product identifier, then seals it — so it is clear who said what, about which product, and exactly when.

Identity-bound
Timestamped
Independently verifiable
Scope

Precisely what
a seal is worth

Overstating this would make the product useless. The boundary is stated plainly, because the boundary is what makes the attestation reliable.

What it proves

  • Which verified legal entity made the statement
  • Which named, identity-verified individual signed it
  • Exactly what was stated, down to the byte
  • When it was sealed, to the second
  • Which supporting documents were attached, by digest
  • That nothing has been altered since sealing

What it does not prove

  • That the declared claim is factually true
  • That the physical item matches the record
  • That the product meets any standard or specification
  • Any certification, approval or inspection outcome
  • Compliance with any statutory labelling requirement

Assessment of product claims remains with accredited certification bodies, inspection bodies and competent authorities. ProntoID performs no product certification.

How It Works

From statement
to sealed instrument

01

The declarant is verified

Before any statement can be sealed, the legal entity is verified through ProntoID KYB and a named individual is bound to it as an authorised signer. An unverified declarant produces no attestation.

02

The claim is bound to an identifier

The declaration is attached to a product identifier — a GTIN, and where relevant a batch or lot number — so the statement refers to an unambiguous, resolvable subject rather than to a product name.

03

Supporting documents are hashed

Certificates, analysis reports and supplier declarations are referenced in the record by SHA-256 digest. The record therefore points to exact bytes, and a substituted document no longer matches.

04

The record is canonicalised and sealed

The payload is serialised deterministically under RFC 8785 and a detached JWS is produced using an ECDSA P-256 key held in AWS KMS. The sealed instrument is written to an append-only ledger.

05

The declaration resolves publicly

The sealed record is exposed at a stable resolver address, so it can be surfaced from an existing product page, a GS1 Digital Link QR code, or a buyer's own due-diligence system.

PREREQUISITE

Every declarant is KYB-verified

The entire value of a sealed declaration rests on knowing who made it. Business verification is not an optional add-on here — it is the foundation.

See ProntoID KYB
Two Configurations

Who is doing
the declaring

The mechanism is identical in both cases. The evidential weight is not.

FIRST-PARTY

The producer declares

The manufacturer or supplier makes the statement themselves. The value is non-repudiation and dating: they cannot later claim they never said it, never said it in those terms, or said it at a different time. Useful for supplier declarations flowing to a buyer who needs a defensible record of what they were told.

  • Non-repudiable statement
  • Dated to the second
  • Amendment history preserved
THIRD-PARTY

An accredited body declares

The declarant is an accredited certification or inspection body, a consortium, or another independent authority. The attestation then carries that body's assessment rather than a self-declaration — a materially stronger claim. ProntoID's role is unchanged: it seals what the body stated and certifies nothing itself.

  • Independent assessment
  • Attestation released from PDF
  • Machine-readable and resolvable
Integration

Behind the code
you already print

ProntoID does not ask you to add a second barcode, adopt a new consumer app, or migrate your product content anywhere. Declarations are bound to the identifiers you already use.

Where a GS1 Digital Link QR code and a product information page already exist, a sealed declaration resolves alongside them. Where a buyer's procurement system needs the record directly, it resolves there instead.

Bound to GTIN and batch
Declarations attach to standard product identifiers, at whichever granularity the claim requires.
Surfaced from existing pages
An embeddable element resolves the sealed record from a product page you already control.
Available to systems, not just people
The same record resolves programmatically for buyers, retailers and compliance tooling.
DECLARATION STRUCTURE
subject.gtin The product identifier the claim refers to
subject.batch Batch or lot, where the claim is batch-specific
declarant KYB-verified legal entity and its identifiers
signer Identity-verified individual and authority basis
statements[] Each declared attribute, in the declarant's own terms
evidence[] Supporting documents referenced by SHA-256 digest
supersedes Digest of the record this instrument replaces, if any
sealed_at RFC 3339 timestamp of sealing
signature Detached JWS over the RFC 8785 canonical payload

Illustrative structure. Exact schema is agreed during integration.

Who It Is For

Anyone answerable
for someone else's claim

Retailers and importers

You carry due-diligence exposure for claims your suppliers make. A sealed declaration is a defensible record of exactly what you were told and when you were told it.

Consortia and protected designations

Anti-counterfeiting programmes hold genuinely valuable attestations. Sealing releases them from unstructured documents into a form buyers and systems can actually check.

Certification and inspection bodies

Your assessments currently end their life as a PDF. Sealed attestations bound to a product identifier make them resolvable, machine-readable and tamper-evident.

Brand owners

Where a claim is central to positioning, a sealed and dated declaration is meaningfully harder to imitate than a marketing badge anyone can print.

Platforms and marketplaces

Require sealed declarations from sellers making regulated or high-risk product claims, and retain evidence of what each seller declared at listing time.

Procurement and compliance teams

Replace a folder of supplier PDFs with a verifiable chain of who declared what, when, and against which supporting evidence.

Frequently Asked Questions

Declarations, answered

What is a ProntoID Product Supplier Declaration?

It is a statement about a product — its origin, composition, certification status or any other declared attribute — made by a legal entity that ProntoID has verified, bound to a product identifier, and cryptographically sealed. The seal makes the declaration non-repudiable: the declarant cannot later deny having made it, and the wording cannot be altered without detection.

Does ProntoID verify that the declaration is true?

No, and this distinction is deliberate. ProntoID verifies the identity of the declarant and seals the exact statement they made, at a recorded point in time. ProntoID does not inspect products, audit facilities or certify claims. Assessment of the underlying claim remains with accredited certification bodies, inspectors and competent authorities.

Then what does the seal actually prove?

It proves four things: which verified legal entity made the statement, which named and identity-verified individual signed it, exactly what was stated down to the byte, and when. Those four facts together make a declaration usable as evidence, which a self-hosted PDF on a supplier website is not.

Can an accredited certification body use this instead of the producer?

Yes, and that is the stronger configuration. Where the declarant is an accredited control body, a consortium or an inspection body, the sealed attestation carries the weight of that body's assessment rather than a producer's self-declaration. ProntoID's role is unchanged: it seals what the accredited body stated, and takes on no certification role of its own.

How does this work with GS1 barcodes and QR codes?

ProntoID sits behind the identifier rather than replacing it. A declaration is bound to a GTIN and, where relevant, a batch or lot number. Existing GS1 Digital Link QR codes and product information pages can resolve a sealed declaration alongside the content they already serve, so no separate scanning journey is required.

What happens if a declaration needs to be corrected?

Nothing is ever overwritten. A correction is issued as a new sealed instrument that references the digest of the record it supersedes. The ledger therefore preserves both what was declared originally and what replaced it, along with the dates of each — which is precisely what makes the history defensible.

Who is this for?

Primarily for organisations that carry due-diligence exposure for statements made by others: retailers, importers, brand owners and platforms who need a defensible record of what a supplier declared. It is also used by consortia and certification bodies that hold valuable attestations currently trapped in unstructured documents.

Does this replace regulatory labelling requirements?

No. Statutory labelling and information obligations are set by law and are unaffected. A sealed declaration is a supplementary evidentiary layer designed to support due-diligence and traceability processes; it is not a substitute for any mandatory disclosure, certification or inspection regime.

Make supplier claims
defensible

Talk to us about declaration schemas, identifier binding and how sealed records fit your existing product data.

Contact Sales Start with KYB

Identity attestation only  ·  Not a product certification service  ·  Independently verifiable