How Do You Verify a Digital Product Passport?
Verification runs in three layers. Resolve: scan the QR data carrier and confirm it opens a live, structured passport tied to a persistent unique product identifier (ESPR Article 10). Check: match the identifiers — product, operator, facility — and, for customs, the registration identifier the registry stores under Articles 13 and 15. Prove: confirm the data itself is authentic and unaltered, which is where version history, cryptographic hashes and signed credentials separate real passports from decorated PDFs.
Written by the DPPLive Team · Last updated: 17 October 2026
How do you verify a Digital Product Passport?
Verify a Digital Product Passport in three layers. First, scan the QR code and confirm it opens a live, structured passport, not a PDF. Second, check that the product, operator and facility identifiers are consistent with the registry record. Third, confirm the data is unaltered through version history, cryptographic hashes or signed credentials.
This is where implementation quality becomes visible. DPPLive publishes every passport version with a SHA-256 hash and issues W3C Verifiable Credentials, so a buyer, auditor or recycler can confirm — independently, cryptographically — that what they scan today is what was published, unaltered. Ask any provider the same question: how would a stranger prove this record hasn't changed?
Quick Answers
Go Deeper
- Regulation (EU) 2024/1781 (ESPR) — full text on EUR-Lex — Article 10 (essential requirements), Article 11 (access rights), Article 13 (registry), Article 15 (customs controls)
- W3C — Verifiable Credentials Data Model 2.0
A Passport Is Only Worth Its Proof
Anyone can put data behind a QR code. The passports that survive audits, borders and buyer scrutiny are the ones a stranger can verify without trusting the publisher. That standard — hashed, signed, independently checkable — is how DPPLive builds every record.