Knowledge Portal
Knowledge Portal
Breadcrumbs

New releases: 12.10.2026

This release lets Express show drivers the right local payment methods in every country you operate in, by setting a country on each price and a default country for your organisation. Payment terminals can now cover individual sockets instead of whole chargers, new chargers get one EVSE per socket by default, and driver self-onboarding now supports Zaptec chargers. A set of fixes makes charger searches faster for large organisations and shows the correct power on ongoing sessions.

Country codes for Express prices

Set a country per price and a default country, so drivers see the payment methods used in their country.

When a driver starts an Express payment, we send a country code to the payment provider. The provider uses it to decide which local payment methods the driver sees, for example MobilePay in Denmark and Finland or Vipps in Norway. Until now the country could only be set by us, and only once for the whole organisation. If you have chargers in more than one country, you can now set it yourself in Connect:

  • Express → Branding: a new Default country field. It is used for every price that has no country of its own. Connect shows a warning while it is empty, because Express payments can't be created without a country.

  • Express → Pricing → Add price: a new optional Country field. Leave it empty to use the default country.

  • The price list has a new Country column, and the price dropdown on a charger's Express card shows the country next to each price.

A price's country is set when the price is created. To change it, create a new price.

In the API, POST /v2/express/prices accepts an optional countryCode, and GET/PUT /v2/express/settings carry defaultCountryCode. Both take an ISO 3166-1 alpha-2 code such as FI or NO. countryCode is also returned on prices and on each socket's price in the Express charger responses.

Choose which sockets of a charger a payment terminal covers.

A payment terminal linked through a roaming integration used to cover every socket of each linked charger. You can now pick individual sockets. Open the terminal under Integrations → Payment terminals:

  • When you add a charger that has more than one socket, Connect lists its sockets with all of them selected. Untick the ones the terminal should not cover.

  • A new Sockets column shows what each linked charger covers. Use the edit button in that column to change the sockets later.

  • If all sockets are selected, the terminal also covers sockets added to the charger later.

Socket selection is available on chargers that show one EVSE per socket. Other chargers are always linked as a whole.

API change: PUT /v2/payment-terminals/{terminalId}/integrations/{integrationId} and PATCH .../chargers now take chargers: [{ chargerId, socketIds }] instead of chargerIds. Send socketIds: null to cover all sockets. A PUT that leaves out chargers keeps the existing links. If your integration manages terminal links through the API, update those requests.

New chargers get one EVSE per socket by default

New chargers now show each socket as its own EVSE in roaming.

Chargers created through the API, the Excel import or self-onboarding now have Split EVSE by socket turned on unless you turn it off. In roaming, each socket of a new charger is published as its own EVSE, so a remote start from a roaming partner always reaches the right socket.

  • Existing chargers are not changed.

  • The EVSE ID of a new single-socket charger ends in 01, for example CHARGER123 becomes CHARGER12301.

  • If you add chargers with POST /v2/chargers and need the old behaviour, send splitEvseBySocket: false.

Zaptec & Easee chargers in self-onboarding

Drivers can now move their own Zaptec and Easee home charger to your network.

Self-onboarding of home chargers now supports Zaptec and Easee. The driver gives consent on Zaptec's own page, and the charger is moved to your network from your Zaptec service account. Contact us to set up Zaptec self-onboarding for your organisation.

Other features released

  • Connect now says ID token instead of RFID, because a token can also come from roaming or a remote start. The driver import Excel template keeps its column names.

  • Pulse automation details show when the automation was created, and when it was last activated or deactivated.

  • Searching chargers, and listing chargers for many sites at once with GET /v2/chargers?siteIds=, is much faster. For large organisations these requests could time out, and Connect then showed an existing charger as not found.

  • The power shown on ongoing sessions is now the total over all phases. For chargers that report power per phase, it previously showed a single phase.

  • API responses are compressed (Brotli or gzip) when your client sends an Accept-Encoding header.

  • Fixed the Run at time of scheduled Pulse automations being shifted by the time zone.

  • Fixed the Suspended by charger option in the charger list socket status filter.

  • Fixed site tariffs and site invoicing not showing correctly.

  • Fixed Express not displaying payment card types correctly.

  • Other small bug fixes.

If you have any questions regarding these changes, feel free to contact us at our Service Desk or at support@emabler.com