Public roaming via Zapmap and CharIN

The different roles of Zapmap consumer payment services and CharIN technical interoperability work in public EV charging.

Zapmap and CharIN both appear in discussions about public charging interoperability, but they do different jobs. Zapmap provides consumer charger discovery and payment on participating networks. CharIN is an industry association promoting technical standards and interoperability for charging systems; it is not a consumer roaming account.

Keeping those roles separate avoids a common mistake: a compatible CCS connector does not guarantee a particular payment app, and a payment app cannot make an incompatible vehicle connector fit.

What Zapmap provides

As at 22 July 2026, Zapmap lets drivers find public chargepoints and filter by connector, power, network, location and payment method. Its payment service can start and pay for sessions in the app on participating networks, and its charging card works on a participating subset.

Coverage changes with commercial integrations. The live Zapmap payment filter and symbol on the location identify the current payment route before travel.

A charger appearing on the map does not necessarily mean it accepts Zapmap payment. Mapping, live status and payment integration are separate data fields.

What CharIN provides

CharIN, the Charging Interface Initiative, brings vehicle makers, charging-equipment companies, energy businesses and other members together to promote interoperable charging standards. Its work includes CCS, the Megawatt Charging System, ISO 15118 features and interoperability testing.

CharIN does not issue the driver a UK public-charging payment card and does not operate every CCS charger. Its contribution is the common technical ecosystem that helps independently made vehicles and chargers communicate and connect.

Four kinds of interoperability

Public charging can succeed at one layer and fail at another:

Physical: the plug and vehicle inlet match.
Electrical and communication: the vehicle and charger negotiate safely.
Authentication: the app, RFID or vehicle certificate is accepted.
Commercial: the account, tariff and settlement route cover that charger.

CharIN’s work is concentrated on the technical layers and their associated standards. Zapmap’s consumer service concentrates on discovery, status and payment integrations. The Public Charge Point Regulations address access, data, pricing, reliability and roaming duties for operators.

CCS does not mean universal payment

CCS combines AC and DC charging functions around a defined connector family and communication standards. A CCS-capable car and compatible public charger can still require:

contactless payment
the operator’s own app or RFID
a supported roaming provider
a compatible Plug & Charge contract

The connector logo should never be used as evidence that a specific app or account is accepted.

Zapmap payment is one roaming route

Where supported, a driver can authorise through Zapmap rather than create the chargepoint operator’s own account. Zapmap then sits between the consumer and participating operator for payment and session information.

The pre-session screen should show the charging price and relevant terms. Compare it with direct or contactless options if price matters, since commercial routes can differ. Parking and overstay charges may be separate from the electricity transaction.

An RFID card can be valuable where phone signal is weak, but only at chargepoints that recognise that provider. Contactless bank-card payment is a separate ad-hoc route and does not require Zapmap.

CharIN, ISO 15118 and Plug & Charge

ISO 15118 can support high-level communication between compatible vehicles and chargers. Plug & Charge uses certificates so an enrolled vehicle can authenticate a contract without the driver presenting an app or RFID token.

This needs an end-to-end chain:

compatible vehicle hardware and software
compatible chargepoint
enabled backend and certificate infrastructure
a mobility contract enrolled for the vehicle

CharIN promotes and tests interoperability around this ecosystem, but membership or CCS support alone does not confirm that one public site has Plug & Charge enabled.

The UK access baseline

As at the review date, the Public Charge Point Regulations require paid public-chargepoint operators to connect to at least one external roaming provider. They also require contactless at specified new and rapid chargepoints and a standard pence-per-kWh price display.

This improves the baseline without making every provider universal. Check the actual site and payment route, especially for older low-power destination equipment.

Planning a journey without a fragile network list

Use live data for the journey rather than an article’s fixed list:

filter for the vehicle connector and a suitable power band
inspect recent status and access information
confirm the chosen payment method at that exact location
keep a second payment route where practical
check parking and site opening times
identify another suitable site before the battery becomes critically low

The live map may still lag a physical fault or site closure. The operator details on the charger remain important.

When a Zapmap session fails

Confirm that the exact connector supports Zapmap payment, not just that the location appears in the app. Check the charger identifier and connector selected, then wait for the vehicle and charger to complete their handshake.

Use the chargepoint operator’s displayed helpline for a physical or live charger fault. Use the payment provider’s support for an account, authorisation or billing issue. Record the time, connector ID, screen message and any amount reserved or charged.

Trying several payment apps in rapid succession can create multiple pending authorisations. Stop and identify which party is reporting the failure.