EU AFIR and ISO 15118: What EV Charger Buyers Need to Verify in 2026

User-provided real-world scene. Used as an application illustration, not as a SINELINK customer-project claim.

1. The dates buyers should know

The dates below are a procurement checkpoint, not a substitute for checking the exact site, market, deployment date and applicable local implementation. The contract should identify the required scope instead of relying on a generic compliance claim.

2. AFIR payment requirements change the hardware scope

A public charger quotation that only includes the power cabinet may not define a compliant public-site scope. Payment capability can change the terminal, screen, communication, backend and enclosure configuration.

• Publicly accessible charging must allow ad hoc charging rather than forcing every user into a long-term contract.
• For newly deployed public points from 13 April 2024, AFIR requires widely used electronic payment options; implementation depends on charger power and deployment context.
• At public points of 50 kW or more, ad hoc pricing is based on price per kWh; an occupancy fee per minute can additionally be used under AFIR.
• A QR or internet-based secure transaction can be relevant below 50 kW, while higher-power public charging has stricter card/contactless expectations.
• The payment requirement belongs in the project specification before the supplier fixes the display, terminal and software scope.

PAYMENT SCOPE

Payment is a site specification, not an accessory added after the order.

Freeze the expected payment method, display and backend workflow before the equipment configuration is finalized. The exact AFIR application still depends on the project facts and destination market.

3. Smart charging, OCPP and ISO 15118 solve different layers

These terms are often placed in one sentence, but they answer different technical and procurement questions. A project can use one without proving the others.

For site-level power control, see dynamic load balancing for commercial EV charging. For a detailed protocol comparison, reserve the OCPP 1.6J versus OCPP 2.0.1 comparison for the point where the required URL is available.

4. Plug and Charge is an ecosystem capability, not a single checkbox

A charger can list ISO 15118 support and still fail to deliver a usable Plug and Charge service if the complete certificate chain, backend, contract-certificate handling, vehicle support or PKI integration is missing.

• Ask which ISO 15118 part and implementation version the ordered firmware supports.
• Ask whether Plug and Charge has been tested with the intended CSMS and vehicle ecosystem, not only on a bench.
• Verify how contract certificates are installed, updated, revoked and monitored.
• Confirm fallback behavior when Plug and Charge authentication fails.
• Do not assume that ISO 15118 support means bidirectional charging is approved or available.

END-TO-END TESTING

A protocol label is not proof of an operating customer journey.

Contract language should freeze the firmware baseline, intended CSMS, certificate-management responsibility, test method and fallback behavior for the ordered configuration.

5. ISO 15118-20 matters because the standard is still evolving

ISO 15118-20:2022 is published and has a 2026 Amendment 1. At the same time, ISO 15118-2:2014 remains current while a second edition is still under development. Procurement language should name the exact standard edition and function set rather than saying only "ISO 15118 compliant".

Illustrative timeline. Confirm the applicable regulation, implementation date, and exact standards scope with the destination-market legal and technical team.

6. A 2026 EU public-charging RFQ should ask these questions

• Is the site publicly accessible under the applicable national implementation and AFIR context?
• What is each charging point's rated power and deployment date?
• What ad hoc payment hardware is included in the quoted configuration?
• How is price per kWh and any occupancy fee displayed before charging?
• Is the charger digitally connected and capable of smart recharging?
• Which OCPP version and certification profiles are supported by the ordered firmware?
• Which ISO 15118 functions are supported, and which are actually tested end-to-end?
• What certificate-management / PKI responsibilities sit with the charger supplier, CSMS and CPO?
• What data/API scope is provided for operational status, availability, and price?
• What country-specific electrical, metering and accessibility rules still need local review?

RFQ DISCIPLINE

Quote the exact public-site scope, not an abstract charger feature list.

The model, payment option, display, communications, firmware, and protocol functions should be identified together. A compliance statement without the configuration is too broad for a purchase order.

7. What SINELINK buyers should separate before ordering

Use the EV charging product hub to shortlist hardware and the project-solution overview for application context. Then request a compliance and protocol matrix for the exact model, destination and software configuration before placing the PO.

Separate conformity and certification-document checks from AFIR project obligations. Separate uptime and service obligations from a charger's technical feature list. The equipment, software and contract scope must be reviewed together.

MODEL-SPECIFIC REVIEW

The public-site scope must be frozen before the purchase order.

Share the destination market, public/private operating model, rated power, deployment schedule, payment requirement, backend, protocol functions and acceptance-test expectations for a model-specific review.

Frequently Asked Questions

Does AFIR require ISO 15118 on every EV charger?

No. AFIR and ISO 15118 are different. AFIR creates regulatory obligations for public infrastructure, while ISO 15118 specifies EV-to-EVSE communication. Check the exact AFIR requirement and the project interoperability needs separately.

Does AFIR require card payment at every public charger?

The payment method depends on charger power, deployment date and location. Higher-power public charging has stricter card/contactless requirements; buyers should verify Article 5 against the exact project.

Is Plug and Charge the same as OCPP?

No. Plug and Charge is primarily an EV-to-EVSE and certificate-ecosystem function associated with ISO 15118. OCPP connects charging stations to central management systems.

Does ISO 15118-20 automatically mean bidirectional charging is ready?

No. The standard defines relevant communication messages, but actual bidirectional operation also needs compatible hardware, vehicle support, grid rules, controls and approvals.

Is ISO 15118-2:2014 obsolete?

No. ISO states that the 2014 edition remains current, although a second edition is under development.

What changed in ISO 15118-20 in 2026?

Amendment 1 was published in July 2026 and adds content for AC DER service, MCS service and an improved security concept.

Should an importer accept "ISO 15118 supported" on a datasheet?

Not by itself. Ask which part, edition, functions, firmware and end-to-end tests are included.

What should be frozen in the purchase contract?

Freeze the exact model, hardware options, payment scope, protocol versions, certified profiles, ISO 15118 functions, firmware baseline, test evidence and responsibility matrix.