Registry integration built to the Commission's API and battery schemas of 30 October 2026; Acceptance testing comes nextEU DPP Registry: live since 20 July 2026

Built for the EU DPP Registry
— Acceptance testing next

The EU DPP Registry has been live since 20 July 2026, and the Commission published its API and battery data model on 30 October 2026. PassportLab builds each battery's registry document against those schemas, with hash-chained audit records and W3C VC proofs. Production registrations start once Acceptance testing and the operator verification steps are complete.

Last updated: November 2026

The Commission's verification tool is coming. Ours works today.

The EU DPP Registry framework foresees an official verification platform, operated by the Commission, that market surveillance authorities and customs can use to check passports. That platform has not launched and has no public preview date.

Until it does, passportlab.io/verify runs checks along the same lines: GS1 Digital Link resolution, W3C VC proof verification, ESPR schema conformance, and SHACL shape validation against the CIRPASS-2 data model. Its passports are published on open, signed endpoints that any verification tool can read.

DPP verification checksPASS
✓GS1 Digital Link resolution · ISO/IEC 18975
✓W3C VC 2.0 proof · Ed25519 signature
✓ESPR data schema conformance · EU 2024/1781
✓SHACL shape validation · CIRPASS-2 profile
✓EPCIS 2.0 event log export
✓Stakeholder role-based field visibility
Planned
Commission verification platform in the registry framework
Today
passportlab.io/verify available to any operator, zero setup
No date
Commission platform launch — no public timeline

Registry downtime doesn't break your compliance record.

If the central registry is unreachable, downstream verification fails — and Art. 15 of Implementing Regulation (EU) 2026/1778 lets the Commission suspend the registry without notice during an incident.

PassportLab's PassportAuditLog is a hash-chained, append-only record — every field change is cryptographically linked to the previous entry. MariaDB triggers enforce DB-level immutability; no application-layer delete or update can silently remove an entry. This is the record that survives a registry outage.

PassportAuditLog — hash chain verificationSHA-256
entry[n].prevHash  =  SHA-256(entry[n-1])
entry[n].hash      =  SHA-256(entry[n] + prevHash)
integrity          =  chain unbroken since genesis
db trigger         =  DELETE / UPDATE → rejected
Block 1
DPP created
a3f8…c120
Block 2
Material data updated
7d2e…b459
Block 3
VC proof issued
f19a…0d83

Built for the live registry.

PassportLab builds each battery's registry document against the Commission's published schemas and sends it to POST /api/v1/dpp/submission in batches, with status tracking per product, automatic retries and a clear list of any data gaps. It is built to the Commission's 30 October 2026 contract; testing in the Registry's Acceptance environment comes next.

The EU DPP Registry has been live since 20 July 2026, with a public testing environment and API. The Commission's API guides and battery data model followed on 30 October 2026. Once a passport is registered, we track its registration status and store its Registry identifier with it. Art. 77/78 delegated acts governing the full battery passport data model are still pending — our schema is versioned to absorb those changes without a migration project.

POST /api/v1/dpp/submissionEU DPP Registry
{
  "productGroup": "BATTERIES",
  "productSubGroup": "LMT",
  "submissionItems": [{
    "uniqueProductIdentifier": "https://www.passportlab.io/api/v1/public/eu/dpp/…",
    "granularity": "item",
    "modelIdentifier": "…"
  }]
}
Commission battery document
Checked against the published JSON Schemas before sending
GS1 Digital Link / UPI normalization
GTIN + serial → UPI per CIRPASS-2 spec
Backup URL + deactivation flag
Art. 15 continuity fields wired to product model
Content negotiation · JSON-LD + AAS
Accept: application/ld+json → UNTP/CIRPASS-2 @context
EU DPP Registry endpoint
Live since 20 July 2026 — Acceptance testing next, then production registrations after operator verification

What's done. What's pending on the EU side.

PassportLab's registry integration is not a roadmap item: it is built to the Commission's published API and battery schemas, and Acceptance testing comes next. Production registration needs the operator's organisation verified in the Registry with a Service Account, PassportLab's third-party verification (Art. 5) and the operator's authorisation of PassportLab (Art. 19(4)) under Implementing Regulation (EU) 2026/1778.

Commission Registry API
POST /api/v1/dpp/submission in batches, with task tracking and per-product results. Built to the contract of 30 October 2026.
GS1 Digital Link / UPI normalization
Every DPP resolves via /01//21/ per GS1 Digital Link ISO/IEC 18975. GCP 42700054032 registered with GS1 Germany.
Hash-chained audit log · cryptographic integrity
PassportAuditLog is append-only, SHA-256 hash-chained, with DB-level immutability enforced by MariaDB triggers.
W3C VC 2.0 + Ed25519 proofs
Every passport ships a W3C Verifiable Credential with Ed25519 signature and DID:Web identity. SD-JWT credentials can be generated to share selected fields with a specific party.
Service Account keys per operator
Each operator registers with its own Service Account key, created in the Registry and held encrypted by PassportLab. PassportLab never registers under its own credentials in an operator's place.
EPCIS 2.0 event repository
Full supply-chain event log per EPCIS 2.0 spec, exportable as EPCIS Document. Operator chain with transfer endpoint live.
EU DPP Registry endpoint
Live since 20 July 2026 with a public testing environment and API. The Commission published the API guides and the battery data model on 30 October 2026. Our integration is built to them; Acceptance testing comes next, and first production registrations follow the operator verification steps above.

Understand your registry position before your competitors do.

Book a 30-minute call. We'll map your products to the Registry's battery document, show you which data is still missing, and walk you through what a registry submission looks like end-to-end on your actual data.

Standards notice: EN 18216:2026–EN 18223:2026 — including the data-carrier standard EN 18220, the data-persistence standard EN 18221 and the interface/API standard EN 18222 — are cited in the Official Journal of the EU for ESPR products (Commission Decision 2026/1736). Battery passports fall under Regulation (EU) 2023/1542, where these standards confer no presumption of conformity; our battery work is designed with reference to them. EN 18239 (access rights) and EN 18246 (data authentication) were ratified in August 2026 and are not cited. ESPR (EU 2024/1781) delegated acts and per-category Annex I requirements are still being finalised. CBAM Reg. 2023/956 obligations continue to evolve under Commission guidance. Results are a readiness indication based on the latest available standards and drafts, and do not constitute legal advice.