Your drivers can now charge at Tesla Supercharger network
We've connected 20,000+ Superchargers across 1,500+ European locations to our roaming offering. For your white-label MSP card holders who drive Tesla or use the white label app, we handle billing alongside all their other sessions.
For Tesla app users
Tesla drivers can add their charge card as a payment method in the Tesla app. Card registration is verified by email: the card stays pending until the driver confirms via the verification link, then it activates as a payment method in the Tesla app.
Once the card is activated in the app, Tesla drivers can plug&charge. The session bills automatically.
During a session: Tesla applies dynamic pricing, including congestion and idle fees. The app proactively notifies drivers about imminent fees. The congestion fee encourages drivers to charge only as much as is needed for their trip, rather than all the way to 100%. This increases the availability of Superchargers so that everyone has access when they need it.
For white-label app users
Any EV driver can open the app and find a Supercharger (the map filters to supported sites).
They can start and stop the session from the app. The session bills automatically.
During a session: Tesla applies dynamic pricing, including congestion and idle fees. The white-label app proactively notifies drivers about imminent fees.The congestion fee encourages drivers to charge only as much as is needed for their trip, rather than all the way to 100%. This increases the availability of Superchargers so that everyone has access when they need it.
Are you our new customer and would like to enable access to Tesla Supercharger network?
Reach out to your Customer success manager to initiate the process and share your brand logo. Road and Tesla will work together. Once the application work is completed, your brand will appear in the provider list in the Tesla app. Now your drivers can charge at Tesla Superchargers!
FAQ
Which EV vehicles can charge at the Tesla Supercharger network?
Any EV vehicle with a CCS2 connector can charge at an open Supercharger. Tesla vehicles can additionally plug in and charge automatically. Please note that the Type 2 (Mennekes) connector is not compatible with Tesla Superchargers.
Do drivers need an adapter?
No. If your vehicle has a CCS2 connector, you will be able to charge at Tesla Superchargers in Europe.Why can't a driver charge at a particular Supercharger?
If that happens, this site is not open to non-Tesla vehicles. Open sites show in the Tesla app and in the white label app.Can drivers charge with their MSP card connected to the Tesla or white label app at any Tesla charger?
Drivers can charge at Tesla Superchargers, a fast DC charging network.
Tesla Destination Chargers, which are AC wall connectors that you can sometimes find at hotels, restaurants, and shopping centers, are not part of the current roaming offering.
Can drivers pay with white label MSP card (plastic RFID card)?
Drivers can use a white label app or register their charge card in the Tesla app. An increasing number of sites are equipped with RFID readers.
How are drivers billed?
The session runs on MSP charge card alongside other charging. No separate payment is required.What is a congestion fee and how drivers can avoid it?
When a Supercharger site is busy and the vehicle has passed 80% battery charge, Tesla applies a per-minute congestion fee to free up stalls. This increases the availability of Superchargers so that everyone has access when they need it. Both Tesla and our white label app notify the driver when this is about to apply so they can unplug in time (drivers need to have notifications enabled).
Clearer overview of CPO reimbursements
We're making it easier to understand your session data and reconcile your payouts with confidence.
Until now, sessions that didn't appear on your reimbursement invoice were simply labelled "excluded" - leaving you to dig deeper to understand why. We're updating the single catch-all data field "Session Validation" with two clear, distinct categories: "Invalid" and "Excluded from reimbursement":
Invalid - A session that was not billable due to a technical issue, such as a duplicate record or a zero usage. These sessions are not charged to the end user and are not included in any billing run.
Excluded from reimbursement - A valid charging session where the payment was collected by another party, and therefore falls outside Road's reimbursement flow.
What this means for you:
Smarter filtering. You'll be able to filter your session list by "Invalid", "Excluded from reimbursement", or fully reimbursed sessions, making it easier to analyse your billing data.
Better data exports. Your session exports will include the new categories and reasons, so you can reconcile invoices in your own systems with accurate, up-to-date information.
Faster dispute resolution. With more descriptive exclusion reasons, support team can resolve billing queries more quickly.
This update is designed to build greater trust in the billing process. The overall look of your session overview stays familiar - the new labels simply slot in where the old "excluded" tag used to be.
Credit Sessions for MSP session corrections
When an MSP session needs to be corrected or taken out of billing, either because a roaming partner has withdrawn a CDR it delivered earlier or because Road has applied a manual correction after a data quality dispute, that correction is now recorded as a Credit Session.
Each Credit Session is its own record, linked to the session it corrects, holding the amount before the correction, the amount after, and the difference to apply. The original session stays exactly as it was delivered, so you keep a full history of what was charged, what changed, and by how much.
What this means for you:
If you run your own billing, corrections reach you as discrete records you can process and credit against invoices you have already issued, including corrections that arrive long after the session itself.
If Road runs billing for you, no action is required. Corrections are held separately from the sessions they apply to, which keeps your session data straightforward to reconcile and audit.
Note: the excluded flag on MSP sessions is being phased out for corrections and exclusions. This is a gradual transition, not an abrupt removal. Existing excluded sessions stay in place and continue to behave as they do today, and any removal will be announced with notice. New corrections will increasingly appear as Credit Sessions.
Guide: Credit Sessions
API reference: MSP Credit Sessions
Provider role scoping
As part of our ongoing work to strengthen platform security, roles are now scoped to the provider that owns them: your users see and assign the roles belonging to their own provider. The same scoping applies everywhere a role can change hands, including editing a user, sending an invite, automatic provisioning through SSO, and role management itself.
No action is required. Existing role assignments are unchanged and nothing was revoked.