Wired for the registry, waiting on the door.

What the registry is.

A Commission-run identifier-to-URL index. It does not hold passport content — it holds one row per passport saying “identifier X resolves to URL Y”. Regulators, customs, and downstream operators (recyclers, refurbishers) use it to find the authoritative passport without asking every manufacturer separately.

• Legal basis: Article 13, Regulation (EU) 2024/1781 (ESPR).
• Start date: 19 July 2026 (2026-07-19).
• Format (expected): IETF LinkSet (RFC 9264) — a minimal, standards-based identifier-to-URL pointer.
• Auth scheme: not yet specified by the Commission.

Where we are.

Ready and waiting. The integration is built against the published direction of travel; what’s missing is on the Commission’s side — the API spec hasn’t been released and provider credentials haven’t been issued. We deliberately don’t POST to a half-specified endpoint: a silent partial upload to a legally-mandated register is worse than an explicit “pending”, because it creates an audit mess to unwind afterwards.

When the Commission opens the door, we finalise the payload against the published shape, go through provider onboarding, and turn it on. Nothing about your printed QRs, your dashboard, or your product changes.

What that means for a passport you publish today.

Each passport’s identifier is already stable and unique. The URL encoded into your QR is already permanent. The integrity hash Article 10 requires is already computed on every revision. When registry registration lights up, every passport you’ve published through us is registered in a single pass — retroactively, without you having to touch anything.

Standards track — CIRPASS-2.

Contenza K/S is a member of the CIRPASS-2 consortium (Horizon Europe, 2023–2026) — the Commission’s primary coordination project for DPP standardisation. CIRPASS-2 is where the field-level schemas and the registry interchange semantics get hammered out between industry, standards bodies (ISO/IEC, CEN/CENELEC), and the Commission.

Membership isn’t a compliance claim on its own — it’s a reading signal. We track the working documents the Commission will base the July 2026 release on, which is why the integration is already shaped to match.

Out of scope for v1.

• Public supply-chain lookup against the registry — that’s a separate product surface for a later release, once the registry itself is live.
• Automatic reconciliation of the registry’s state back into our database. Your passport is the source of truth; we push pointers, we don’t pull.