New releases: 29.09.2026 | Knowledge Portal

This release lets one organisation settle Express payments to more than one Adyen account holder, which is what running Express in several countries needs. It also adds the MCS (Megawatt Charging System) socket type, makes plug-in counts in the sockets API optional, tightens site access for Pulse automations, and adds session validation rules that flag implausible charging sessions.

Multiple Adyen account holders per organisation

Cost centers can settle to their own Adyen account holder, and payout reports are split to match.

If you run Express in more than one country, or otherwise settle revenue to more than one Adyen account holder, each cost center can now have its own account holder. We set the account holder on the cost center for you. A cost center without one keeps using your organisation's account holder, as every cost center did before.

Reconciliation reports follow the same split:

You get one reconciliation report per account holder instead of one merged report for the whole organisation, and you can filter the report list by account holder.
Site admins can now view and download reconciliation reports for the account holders of the sites they manage. Admins still see every report for the organisation.
Payouts in the same currency are added up in the report summary as before. If one account holder is paid out in more than one currency, the summary total is left empty rather than adding different currencies together. The individual payout lines are still listed.

The Adyen payout and transaction views open for the account holder you choose. You see only the account holders you have access to.

MCS socket type

Sockets can now be recorded as MCS (DC).

MCS (DC) is now an accepted socket type, for chargers using the Megawatt Charging System used by heavy-duty vehicles. MCS sockets are handled as DC charging. You can filter the sockets list for them with GET /v2/sockets?socketType=MCS (DC).

Plug-in counts in the sockets API are now optional

GET /v2/sockets only calculates plug-in counts when you ask for them.

As announced in Upcoming changes: Plug-in counts in the sockets API, GET /v2/sockets takes a new includePlugCounts parameter, which defaults to false.

Without the parameter, or with includePlugCounts=false, plugCount is returned as null. plugCountOffset and plugCountResetAt are returned as before.
With includePlugCounts=true, plugCount is returned as before.
The sockets Excel export is unchanged and always includes plug-in counts.

If your integration reads plugCount from GET /v2/sockets, add includePlugCounts=true to those requests. The plug-in count column in Connect is already updated.

Site access for Pulse automations

Site admins' automations must now name the sites or chargers they apply to.

When a site admin creates or edits a Pulse automation, the automation must now target at least one site or charger. Before, an automation that named neither could apply to every charger in the organisation. Admins can still create automations that cover the whole organisation.

Pulse alerts and activity logs now follow the same site access as the automations that raised them. Site admins see alerts and logs for automations on their sites, and no longer see them for sites they don't have access to.

Session validation rules

Flag charging sessions that look implausible, using limits you set.

Admins can now set session validation rules in Connect under Settings → Session validation rules. When a session breaks a rule you've turned on, it gets an issue flag in the session list and session details, next to the existing issue flags, so you can check it before invoicing. A flag doesn't stop the session or change its price.

Maximum average power (kW): average power (energy divided by duration) is above the limit. Shown as Average power too high.
Minimum duration (minutes): the session is shorter than the limit. Shown as Session too short.
Maximum energy (kWh): the session delivered more energy than the limit. Shown as Energy too high.
Zero duration (no limit to set): the session's end time is not after its start time. Shown as Zero duration.

All rules are off until you turn them on. The existing issue flags are not affected and are still checked on every session. Rule changes apply to sessions that end a few minutes after you save them. Sessions that have already ended are not checked again.

Other features released

The list of sites a driver has access to loads much faster. For large organisations it could time out in Connect.
Charger configuration changes no longer accept OCPP passwords (AuthorizationKey in OCPP 1.6, BasicAuthPassword in OCPP 2.0.1 and 2.1). Set the password through the OCPP authentication settings for the charger or the organisation instead. Setting it through a configuration change did not update the stored credentials, so the charger could be refused on its next connection.
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