AFIR Compliant DC Fast Charger Procurement for European Corridors

An AFIR compliant DC fast charger for a European corridor must satisfy more than a power rating. The project has to align the charger with the applicable TEN-T pool target, CCS2 interoperability, fixed-cable rules, ad hoc card payment, price display, digital connectivity, smart charging, open data, accessibility, and long-term operations.

This procurement guide is written for corridor CPOs, motorway service areas, petrol station operators, EPC contractors, public authorities, and equipment importers. Luxman Energy publishes several DC power and payment-capable configurations, but the final compliance position depends on the ordered model and the complete station system deployed in the target Member State.

Treat corridor compliance as a pool design

AFIR regulates recharging points, stations, pools, and operators. A product datasheet normally describes one charger; a corridor obligation can apply to the combined power and number of points at a location.

For light-duty vehicles on the TEN-T core road network, Article 3 generally requires publicly accessible pools in each direction of travel with no more than 60 km between them. By 31 December 2025, each pool must offer at least 400 kW and include at least one point rated at 150 kW or more. By 31 December 2027, the general target increases to 600 kW with at least two points rated at 150 kW or more. The regulation includes conditions and possible derogations, so the responsible authority should confirm the route-specific position.

These targets create two separate design checks:

Design check	Procurement question
Pool output	What simultaneous power can the complete site provide under the applicable AFIR target
Individual point output	How many points meet the required minimum individual rating
Charger nameplate	Is the quoted rating per cabinet, per output, or shared across simultaneous connectors
Grid capacity	Can the connection and transformer sustain the required pool output, not merely installed nameplate capacity
Availability	Can the pool retain adequate service when one charger, terminal, or feeder is unavailable
Direction of travel	Does the site design and road access satisfy the applicable corridor treatment in each direction

A 160 kW charger can satisfy an individual 150 kW rating test when its ordered configuration and operating conditions support that output, but one cabinet does not automatically satisfy a 400 kW or 600 kW pool requirement. Confirm how power sharing, temperature, vehicle voltage, simultaneous sessions, cable limits, and upstream capacity affect usable output.

Heavy-duty corridor infrastructure requires a separate Article 4 assessment. Do not reuse a light-duty site model for electric trucks without checking the higher pool and individual-point requirements, vehicle circulation, trailer geometry, cable handling, and charging interface roadmap.

Apply the 50 kW payment threshold correctly

The current consolidated AFIR text uses a threshold of power output equal to or more than 50 kW for several payment and pricing provisions. A 50 kW point is therefore inside the higher-power category for these rules.

At publicly accessible points deployed from 13 April 2024, ad hoc payment must be possible through widely used electronic payment instruments. For points at 50 kW or more, the accepted route must include a payment card reader or a contactless device at least able to read payment cards. A QR-only route available to sub-50 kW points is not the equivalent procurement answer for a new corridor fast charger.

From 1 January 2027, the same card-reader or contactless requirement reaches older publicly accessible points rated at least 50 kW when they are along the TEN-T road network or at a safe and secure parking area. AFIR defines a charging station as along TEN-T when it is on the network or within 3 km driving distance of the nearest exit. Buyers planning a retrofit should verify the exact site classification rather than relying on a map screenshot or straight-line distance.

Use an asset-level register for every point:

• Installation and commissioning date

• Exact location and TEN-T relationship

• Rated output and any shared-power arrangement

• Existing payment method and terminal location

• Hardware, software, civil, and communications changes required

• Planned outage and recommissioning date

• Evidence owner and final acceptance status

This register turns the 2027 deadline into an executable retrofit programme instead of a late fleet-wide hardware order.

Choose dedicated or shared terminals around availability

AFIR allows one payment terminal or device to serve several publicly accessible points within one charging pool. A shared terminal can reduce hardware count, acquiring administration, and maintenance visits. It also creates a station-wide dependency.

Compare the architectures against peak use:

Terminal design	Main advantage	Main risk	Control to specify
Terminal on each charger	Direct physical relationship and distributed capacity	Higher hardware and lifecycle cost	Standard terminal build, remote management, spare strategy
One shared terminal	Lower terminal count and centralized user flow	One failure can block ad hoc access across the pool	Redundancy, clear connector selection, rapid replacement
Two shared terminals	Capacity and fault tolerance for a larger hub	More mapping and site-layout work	Common identifier register and tested failover
Shop-counter POS	Staff assistance and existing payment estate	Depends on opening hours and correct charger selection	Documented public availability and integrated workflow

Model terminal throughput with realistic user behavior. Include connector selection, tariff review, card presentation, authorization, start confirmation, receipt choice, declines, retries, and users who abandon the flow. The number of chargers is not a sufficient terminal-capacity calculation.

The system must prevent a driver from paying for an occupied, reserved, faulted, or unreachable connector. If payment is approved and charging cannot start, the responsible component should query the final state and reverse or release the authorization according to a tested rule.

Present the corridor price before the session

For a publicly accessible point rated at least 50 kW, AFIR requires the ad hoc price to be based on the price per kWh for electricity delivered. The operator may add an occupancy fee expressed as a price per minute. The station must show the price per kWh and any occupancy fee before the user starts charging.

The tariff path should have one controlled source and a traceable version. Define how the price moves from the commercial system to the charger screen, shared terminal, signage, app, receipt, charging data record, and settlement report. At minimum, test:

• A scheduled tariff change while chargers remain online

• A terminal that reconnects after missing an update

• Different tariffs across connectors or vehicle groups

• Occupancy-fee start and stop conditions

• A stopped session whose final meter record arrives late

• A refund after the original tariff has changed

Price transparency and correct financial capture are related but different controls. The driver-facing price can be correct while the backend calculates the wrong amount, or the calculation can be correct while the station displays stale information. Acceptance evidence must cover both.

Specify fixed cables and current CCS2 references

AFIR required all publicly accessible DC points to have a fixed charging cable by 14 April 2025. The tender should identify cable length, reach zone, connector holster, handling force, management system, environmental exposure, impact protection, replacement time, and any liquid-cooling service requirements.

For interoperability, relevant DC points installed or renovated from 8 January 2026 must be evaluated against the updated Annex II references introduced through Commission Delegated Regulation EU 2025 656. For light-duty DC charging, the annex refers to Combo 2 for Mode 4 under EN IEC 62196-3:2022. Older points can remain under the earlier referenced edition until renovation where the transition provisions apply.

Request evidence for the exact connector and cable assembly, not only the charger family. If a cabinet can be ordered with CCS1, CHAdeMO, GB/T, or CCS2, reports for one interface do not automatically establish coverage for another.

Build digital and smart functions into the tender

Every publicly accessible point must be digitally connected. New or renovated public points within the applicable AFIR dates must also be capable of smart recharging. The corridor CPO should translate those duties into functions that can be commissioned and supported.

Specify:

• Secure charger registration and communications

• Remote status, start, stop, reset, configuration, and diagnostics

• Meter values, timestamps, stop reasons, and transaction recovery

• Site and connector power limits

• Charging profiles and safe local fallback

• Firmware and certificate lifecycle management

• Network monitoring across primary and backup communications

• Audit logs for administrative and tariff changes

The Open Charge Alliance describes OCPP as the protocol between a charging station and charging management system. OCPP 1.6 supports smart charging and charge profiles; OCPP 2.0.1 adds stronger device management, transaction handling, security, and smart-charging functions. A version label alone does not show which functions, profiles, or security settings the ordered charger and CSMS implement.

Require an implementation statement and an end-to-end test against the production CSMS. Record every proprietary extension needed for payments, power control, diagnostics, or multi-output behavior.

Keep AFIR data synchronized with operations

Article 20 requires specified static and dynamic charging data to be available through an API, with API information submitted to the relevant national access point. For a fast-charging corridor, high-value dynamic fields include operational status, current availability, and ad hoc price.

The charger, CSMS, maintenance platform, and data API should share stable station, EVSE, and connector identifiers. When field staff isolate a connector, the published status should not continue to show it available. When a tariff changes, the price visible at the site, used for the transaction, and published through the data interface should remain consistent.

Set measurable data-quality controls:

• Maximum event-to-publication delay

• Maximum age of a dynamic record

• Identifier and coordinate validation

• Detection of impossible states

• Reconciliation between commissioned assets and published assets

• Incident priority when public status or price is wrong

• Evidence retention for corrections

National access point onboarding and the applicable data profile can vary by country. Confirm the local technical route during design rather than after commissioning.

Engineer for revenue availability

A corridor site can be physically powered while commercially unavailable. Track the full successful-service path:

1. The point is visible and accurately reported.

2. The driver reaches the correct bay and cable.

3. The charger recognizes the vehicle.

4. The payment method authorizes.

5. The selected connector starts once.

6. Power is delivered at an explainable rate.

7. The session stops and produces a valid meter record.

8. The correct amount is captured and a receipt is available.

9. Settlement and reconciliation complete.

Set service levels for charger faults, terminal faults, network failures, damaged cables, payment exceptions, and incorrect public data. Define remote triage, field response, spare parts, terminal replacement, cable replacement, firmware rollback, and escalation between the hardware supplier, CSMS, payment provider, telecom operator, and EPC.

Measure connector availability separately from successful charging and payment. A charger that reports available but repeatedly fails after payment is not delivering the intended corridor service.

Review the Luxman DC fast charger configuration

Luxman’s 120 kW 160 kW and 180 kW DC charger page lists a ground-mounted unit with a 7-inch touch screen, POS payment, ISO 15118, CCS2 and other connector options, OCPP 1.6J, optional Ethernet, 4G, or Wi-Fi, an IP54 rating, and DC output listed at 200 to 1000 V.

For a European AFIR project, confirm the exact 160 kW or 180 kW configuration where an individual point of at least 150 kW is required. Also confirm simultaneous-output behavior, CCS2 assembly, fixed cable, payment terminal and acquiring combination, price presentation, firmware, OCPP functions, meter evidence, CE documentation, updated standard editions, environmental derating, and country-specific service support.

The product page lists ISO 15118, but that description does not establish every ISO 15118 part, profile, Plug and Charge function, certificate arrangement, or 2027 AFIR use case. Request a feature and standards statement tied to the ordered hardware and firmware.

Use a corridor tender evidence matrix

Add an evidence column beside every tender requirement. The final matrix should cover:

• Route, direction, distance, and pool classification

• Installed pool output and minimum individual-point output

• Grid connection, transformer, switchgear, earthing, protection, and metering

• Charger model, outputs, power-sharing logic, voltage range, and derating

• CCS2 connector, fixed cable, reach, accessibility, and spare strategy

• Ad hoc payment, terminal capacity, acquiring, receipts, reversals, and refunds

• Price display, tariff control, occupancy fee, and audit history

• Digital connectivity, OCPP functions, smart charging, and cybersecurity

• Static and dynamic data, API, national access point, and data quality

• Product conformity, installation inspection, commissioning, maintenance, and SLA

Classify evidence as design calculation, certificate, declaration, test report, protocol trace, screenshot, contract, or site measurement. A supplier response of standard feature should not close a requirement without a verifiable reference.

Run DC corridor acceptance tests

Factory testing should use the exact charger firmware, terminal, CSMS, and power-sharing configuration. Site testing should use production electrical capacity, communications, merchant setup, signage, and labels.

Test at least:

1. Rated and shared power behavior with supported vehicle or load-simulator conditions.

2. Every required card and contactless journey on each permitted connector.

3. Price display and tariff calculation before and after a controlled update.

4. Payment approval followed by start rejection, cable fault, or network timeout.

5. Remote power limits and safe behavior when the smart-charging controller is lost.

6. Primary and backup communications, queued records, and reconnection.

7. Status, availability, and ad hoc price publication through the data path.

8. Cable reach, connector handling, screen visibility, accessibility, and support instructions.

9. Meter, charging record, payment capture, receipt, settlement, and reconciliation.

10. Restart, firmware rollback, and recovery of incomplete sessions.

Define the pass criteria before testing and retain the evidence against the serial number and software versions delivered.

Frequently asked questions

Does the AFIR 50 kW threshold include a 50 kW charger?

Yes. The relevant wording is power output equal to or more than 50 kW, so a point rated exactly 50 kW is included.

Must every older DC fast charger receive a card terminal by 2027?

The 1 January 2027 retrofit rule applies to publicly accessible points rated at least 50 kW along the TEN-T road network or at safe and secure parking areas. Other sites still need a project-specific AFIR and national-law review.

Can a corridor hub use one shared payment terminal?

Yes. AFIR allows one terminal or device to serve several points in one pool. The CPO should prove connector mapping, peak capacity, accessibility, redundancy, and recovery from terminal failure.

Is QR payment enough for a new 150 kW point?

No. The secure internet or QR route in Article 5 is an option for publicly accessible points below 50 kW. A new 150 kW point needs the applicable card-reader or contactless route.

Does one 160 kW charger satisfy a TEN-T corridor target?

Not by itself. The project must check both minimum individual-point output and total pool output, as well as distance, direction, vehicle class, deadline, and any applicable conditions or derogations.

Does CE marking prove full AFIR compliance?

No. CE-related product conformity is one part of the evidence. AFIR also places requirements on payment, pricing, connectivity, smart charging, cables, technical interoperability, data, and operator processes.

AFIR compliant DC fast charger conclusion

An AFIR compliant DC fast charger should be procured as part of a corridor pool and operating service. The buyer must connect the route target, grid capacity, charger output, CCS2 cable, payment, price, smart control, open data, and maintenance evidence before awarding the contract.

For a project review, provide Luxman Energy with the Member State, TEN-T and direction-of-travel classification, vehicle type, required pool and point output, number of chargers, grid capacity, CCS2 and cable requirements, payment-terminal architecture, acquirer, tariff, CSMS and OCPP functions, data interface, environmental conditions, and acceptance plan. Luxman Energy can then confirm available DC configurations and the evidence or integrations that remain project specific.