EV Charging & OCPP

EV Charging Software and OCPP Integration

Digiton designs, builds, and migrates OCPP charging management platforms for charge point operators, installers, and fleet operators, timed against the AFIR deadlines now landing across the EU.

Digiton builds and migrates EV charging management platforms: OCPP 1.6 to 2.0.1 migration, ISO 15118 plug and charge, DATEX II reporting, and fixed-scope platform builds for small and mid-size charge point operators, installers, and fleet operators. Email contact@digiton.ai to scope a project.

Charge point operators across Europe are running two clocks at once. One is commercial: more chargers, more sessions, more revenue per site. The other is regulatory: the Alternative Fuels Infrastructure Regulation (AFIR) is landing a sequence of dated technical obligations on every public charger, and the software behind most charging networks was not built to meet them. Digiton designs, builds, and migrates the platforms that sit behind the chargers: the OCPP central system, the operator dashboard, the billing and session layer, and the integrations that connect them to hardware, payment rails, and national reporting systems.

Why charge point operators are moving now

Three AFIR obligations apply on fixed dates, not on a rolling schedule set by the operator.

DateObligationApplies to
8 Jan 2026ISO 15118-2 support requiredNew and renovated public AC chargers
14 Apr 2026DATEX II data reporting mandatoryPublic charging point operators
2027Card payment readers requiredChargers rated 50kW and above

None of these are optional line items. A charger that cannot negotiate ISO 15118-2, a network that cannot publish DATEX II data, or a fast charger without a card reader is a charger that falls out of compliance, and increasingly out of the national registries and roaming networks other operators and drivers rely on. For the full breakdown, see our AFIR compliance guide.

OCPP 1.6 to 2.0.1: the migration underneath the deadlines

Most of the installed base in Europe still runs OCPP 1.6. It works, but it was not designed for certificate-based security, structured device management, or native ISO 15118 support. OCPP 2.0.1 is the first version of the protocol built with ISO 15118 in mind, which makes it the practical path to plug and charge and to the AFIR deadlines above. For a small or mid-size CPO, a full migration (central system, firmware, testing, phased rollout) typically runs 6 to 12 months. We cover the full breakdown, phase by phase, in our OCPP migration guide.

What we build

Proof: a production platform on Zaptec hardware

Digiton designed and shipped a production OCPP charging management platform on Zaptec hardware for a European EV charging operator: OCPP backend integration, session and billing logic, and an operator dashboard, taken from scoping to a live deployment handling real charging sessions. That is the same discipline we bring to a migration or a new build: a fixed scope, a working system, and a team that stays accountable after go-live.

How the engagement works

  1. Audit. We map your current OCPP version, hardware fleet, firmware versions, and the specific AFIR obligations that apply to your sites.
  2. Migration or build plan. A fixed-scope plan with a realistic timeline, usually 6 to 12 months for a mid-size operator, shorter for a single-site installer.
  3. Build and test. Central system work, firmware coordination, and testing against real chargers before anything touches production traffic.
  4. Phased cutover. Sites move in stages, not all at once, so a problem on one site never takes down the rest of the network.
  5. Monitoring. Once live, session data, uptime, and compliance reporting run without manual intervention.

Digiton works with small and mid-size charge point operators, installers, and fleet operators on fixed-scope OCPP migrations and platform builds. Email contact@digiton.ai with your current charger count and OCPP version, and we will scope the migration.

Frequently asked questions

What is the deadline for ISO 15118-2 on public chargers?

New and renovated public AC chargers must support ISO 15118-2 from 8 January 2026 under AFIR. This is the standard behind plug and charge, where a vehicle authorizes a session automatically without a card or app.

Do we need to migrate to OCPP 2.0.1 to comply with AFIR?

AFIR does not name OCPP by version, but ISO 15118-2 support, DATEX II reporting, and payment integration are far easier to implement on OCPP 2.0.1, the first version built with ISO 15118 in mind. Most operators treat the migration as the practical path to compliance.

How long does an OCPP migration take?

For a mid-size charge point operator, a full migration from OCPP 1.6 to 2.0.1, including central system work, firmware coordination, testing, and phased rollout, typically runs 6 to 12 months. A single-site installer can move faster.

What is DATEX II reporting?

DATEX II is the data exchange format the EU requires public charge point operators to use when reporting charger location, availability, and pricing data to national access points, mandatory from 14 April 2026 under AFIR.

Does Digiton work with our existing charger hardware?

Yes. Our platform work integrates with OCPP-compliant hardware from vendors including Zaptec, and we scope against whatever hardware mix you already have installed rather than requiring a hardware swap.

Related

OCPP 1.6 to 2.0.1 migration guideAFIR compliance deadlines 2026-2027Build vs buy: EV charging platform

Ready to put AI to work?

Book a discovery audit and we will map the highest-ROI AI agents and automations for your business.

Book a discovery audit →