Public product data your store can use
Every Digital Product Passport issued on Verifable has a public side: information meant to be consumed by e-commerce stores, product pages, QR codes, mobile applications, public catalogues, partner systems, search agents, and AT Protocol clients — without requiring those consumers to hold any Verifable credential of their own.
The public passport surface works today — issue one and open it. Storefront feed and embedding metadata are not exposed as a guided integration.
What exists today
Every passport issued here has, from the moment it is issued:
- a stable public URL
- a JSON document (
dpp.json) - a did:web product identity
- a public/controlled field boundary, where restricted fields are masked until access is granted
See the public passport view and issuing for how these are produced.
On the way for storefronts
Each of these builds on the public passport surface above; availability is stated beside the relevant integration.
- Language negotiation
- Freshness and version metadata
- Link-preview metadata for social unfurls
- Embeddable DPP cards
- Caching guidance
- GS1 Digital Link resolution
A concrete example
A QR code printed on a battery leads to its public passport view. The linked passport JSON gives the shop's backend a machine-readable record alongside the human-readable page. The AT Protocol integration is intended to let a public post link back to that passport; production availability is stated separately. See the network and the AT Protocol platform page.
Further reading
Digital Product Passports, tools, the network, and international trade for the same passport once it crosses a border.