The pipeline
Four steps from data to passport.
Battery Digital Passport sits between your existing systems and the regulator. You keep your data where it lives; we turn it into a signed, scannable, compliant passport.
Model
Connect your bill of materials, supplier declarations and lab results. Battery Digital Passport ships the Annex XIII schema pre-built, so you map fields once instead of interpreting the regulation from scratch. Bulk import via CSV, ERP connector or the API.
- BOM import
- ERP connectors
- Schema validation
Verify
Carbon-footprint figures are checked against the declared study; due-diligence evidence is attached; and each declaration is cryptographically signed by the responsible economic operator — or a notified body where conformity assessment applies. Nothing ships unverified.
- CF validation
- Digital signatures
- Notified-body sign-off
Mint
A globally unique battery identifier is generated and bound to a QR data carrier, resolvable through GS1 Digital Link. Print it, laser-etch it, or embed it — the code resolves to the right passport, in the right language, on any device.
- Unique identifier
- GS1 Digital Link
- Print-ready QR
Serve
At scan time, each audience reaches its own tier — public, legitimate interest, or authority. State-of-health and status fields update over the battery’s life through connected BMS telemetry, and the passport stays resolvable even after your operator entity changes.
- Tiered access
- Live SoH updates
- Lifelong persistence
Built for engineering teams
REST + webhooks
Idempotent endpoints, event webhooks on status change, and batch operations for high-volume production lines.
Typed SDKs
First-class SDKs for TypeScript, Python and Go, with the Annex XIII schema as generated types.
Sandbox & audit log
A full sandbox environment plus an immutable, exportable audit trail of every declaration and change.
Mint your first passport this week.
Get a sandbox key and issue a live, scannable battery passport in an afternoon.