CEN/CENELEC JTC 24 published the first six European DPP standards in May 2026 and the two security standards on 16 September 2026. Each governs one layer, and we implement all of them — rather than a format of our own.
Five identifier schemes are recognised. GS1 Digital Link is our default and every passport is a resolvable URL, but EPC, UUID, DID and MA-DPP are equally valid.
QR carrying the full URL, and GS1 DataMatrix with a proper FNC1 header, generated for every product.
Plain HTTPS with content negotiation: a phone gets HTML, a system gets JSON-LD, from the same URL.
A versioned /dpp/v1 API to search, retrieve and query passport lifecycle.
JSON-LD on schema.org plus the GS1 vocabulary and a dpp: namespace — a machine-readable semantic graph.
Passports issuable as W3C Verifiable Credentials signed with Ed25519, verifiable offline.
Group-level, independently audited, and maintained — not self-declarations. Where we are not certified, we say so.
Quality, environmental and information-security management across the Sensoneo group that operates the platform.
Independent controls assurance through our parent group, which runs EU-wide deposit-return IT at national scale.
All product data stored in the EU. EU jurisdiction, GDPR-compliant, and it does not leave.
Our resolver passes the official GS1 Digital Link Conformance Test Suite.
Ed25519 Verifiable Credentials, verified offline against a public key. No blockchain, no token, no wallet.
JSON Schema and the OpenAPI 3.1 spec are public and MIT-licensed, and everything exports as CSV and JSON-LD.
No, and neither is anyone else: EN 18216 and EN 18219–18223 were published in May 2026 and cited in the Official Journal, the two security standards EN 18239 and EN 18246 followed on 16 September 2026, and no certification scheme exists for any of them yet. We implement the same open standards the series rests on, and we would rather state that than imply a certificate nobody can currently hold.
In the European Union, in Germany. EU jurisdiction, GDPR-compliant, and it does not leave the EU. A second region in the United States serves passports quickly there; it does not move EU product data.
No. Passports can be issued as W3C Verifiable Credentials signed with Ed25519 and verified offline against our public key. That gives tamper-evidence without a chain, a token or a wallet.
Everything exports as CSV and JSON-LD, and the schemas and OpenAPI spec are MIT-licensed. Your identifiers are URLs you own. Leaving should cost a migration, not your data.
Open a fully populated battery passport — materials, substances, documents and a verifiable credential.