Skip to main content

Release notes V1.17

An overview of the new and updated product features

Written by Ksenia Vardzelova

Focus on winning customers while Trust Tiers protect your revenue

  • Are you scaling MSP operations?

  • Seeing fraud or suspicious activity on the platform?

  • Dealing with failed invoices from incorrect customer data?

  • Need a frictionless way to verify new accounts at volume?

Trust Tiers validates every new account with identity verification before it can reach higher spending limits, automatically assigns new sign-ups to a configured tier, and upgrades accounts only as they pass verification, so operators cap their financial exposure.

What changes from the setup you have today

Account verification on the platform currently runs on a common baseline: fixed logic, fixed caps of 5,000 euros for individuals and 30,000 euros for organisations, a fixed bundle of email, SMS and bank checks, and a support request needed to move an account above tier 2.

Trust Tiers replaces all of that with your own configuration. You design the tiers, you set the caps, you choose which checks gate which level, and progression runs automatically all the way up. If you would rather not customise anything, the baseline stays available and nothing changes for you.

How it works

New accounts land in a defined tier automatically. As the account completes the verification steps the operator has chosen, it progresses to higher tiers and higher monthly caps. Limits are monthly and fixed per tier by the operator, up to a maximum cap of €100k per month.

What an operator can configure today

  • Up to four tiers per account type, fully self-service from the dashboard.

  • Monthly caps that you set yourself, in euro by default and in other currencies where you need them.

  • Verification via email, SMS, bank verification (NL, BG), and VAT, which is optional to skip but validated against the registered company name in real time if a number is entered.

  • Automatic progression across every tier, with no support request needed at any point.

Split an account limit across its users

An account admin can divide the account's monthly limit across the individual users on it, so no single user drains the shared budget. Each user limit is either manual, with a fixed monthly amount reserved for them, or auto, taking an automatically calculated share of whatever is left after the manual allocations.

What this means for you:

  • Block fraudulent accounts before they reach credit, stopping revenue leakage from day one

  • Automated progression removes manual reviews and back-office overhead

  • Centralised dashboard with full visibility into every account's tier, status and limit

What this means for your end-customers:

  • Quick, low-friction sign-up with progressive verification steps

  • A clear path to higher limits by completing simple verification

  • Secure verification protects against misuse of their account

  • Account admins can distribute the account's monthly limit across their own users, reserving budget for the people who need it most

  • No single user can drain the shared account budget

What it costs

Trust Tiers is free to enable and use. No set-up costs, no per-use verification costs.

Please contact your Customer Success Manager to enable Trust Tiers.

Offer card holders a better price on operators' own network

Until now, giving an operator's own drivers a different price meant setting up access group(s) for each charger. Now it is a single setting on the profile the operator already uses.

This is built for providers that act as CPO and MSP and want to give their own card holders a lower price. It suits semi-public networks too, where employees, residents or members should pay less than passing drivers.

How it works

A special price for a card billing plan is added to a Tariff Profile, alongside the standard tariff. When a driver starts a session, the platform checks which billing plan the card is on. If that plan has a special price, it applies. If not, the standard tariff applies. The selected price is recorded on the session, so the CDR, the driver's receipt and the invoice all reflect the special rate.

What this means for you:

Loyalty pricing without extra structure. One Tariff Profile serves both the operator's own card holders and the public, with no separate access groups to maintain.

Self set up. Operator configures everything in the tariff profile settings, so there is no request to raise and no waiting.

Predictable for roaming. The standard tariff stays the price published to roaming partners. Only cards on the operator's own billing plans get the special price.

Granular per plan. Each billing plan can have its own rate, so operator can build tiers such as staff, member and public on a single profile.

Learn how to set a special pricing on the Tariff Profiles here.

Billing exports now say exactly what each line bills

Billable item exports of CPO usage and MSP usage invoices now say exactly what each line bills: a stable fee type, a label, the IDs of the session, token or billing plan behind it, and the quantity, rate or percentage that produced the amount. The same export is available through new public Invoices endpoints, per invoice or for a whole billing period, so a provider that runs its own billing can feed it straight into an ERP or accounting tool.

What's changed

  • CPO Usage and MSP usage invoices get a new export model for invoice billable items.

    • Each billable item now carries a type and a label. Those uniquely identify what is being billed. Be it session costs, session fees, subscription costs or one-off costs.

    • Every main entity has an ID. Sessions, tokens, billing plans - anything that can help a customer uniquely identify what is being billed.

    • Anything that is "Session" related now carries as much information about the session as possible. That includes information about the location, the charger, the token, the start and end time and the kWh charged.

    • Every item shows how its amount was calculated (quantity, rate, percentage). MSP session costs also show the CPO price and the exchange rate applied (when applicable).

  • The Download Invoice Billable Items (CSV) and Download Invoice Billable Items (Excel) buttons have merged into a single menu item. Everywhere, for account admins and provider admins.

  • The extended export is also available through a brand new public API, so providers doing their own billing can feed it into their own ERP or accounting tools without the dashboard.

With Map SDK v3 operators can easily see connector statuses and drivers - available chargers

In the new release of Map SDK you find new pins, availability counted per charge point rather than per location, a status breakdown, and prices on the map API.


​What's in it for CPOs:

  • Individual pins at city scale rather than clusters, up to 1000 locations in view.

  • Red ring for a faulted connector, amber for one taken out of service, blue for a session running. The digits keep showing how many connectors are still free.

  • The status pill totals connectors by the status the station itself reports over OCPP, and clicking a status filters the map to it, so an operator can pull up every faulted connector in a city.

  • An "EVSE Status | Roaming Status" switch under the pill compares what the stations report with what roaming partners see for the same sites.

What's in it for drivers:

  • Free charge points at a glance, without opening the location.

  • Green ring when every charge point is free, amber when a session is running, and the digits say how many are still free.

  • The status pill totals charge points by the roaming status Road publishes to partners.

  • Note the colours differ from CPO maps: amber is "in use" here and "out of service" there.

Discuss integration with your Customer Success Manager.

Scan2Pay: one debit per charging session

Drivers who pay with Scan2Pay now see a single debit on their bank statement for each charging session.

Until now, the payment was captured in several smaller amounts while the session was running. This meant one session could show up as multiple separate debits, which some drivers read as being charged more than once.

The full amount is now captured in one go when the session ends. The total a driver pays stays the same; only the way it appears on their statement has changed.

Did this answer your question?