We're bringing Ocean's release notes out from behind the login screen. Starting this month, we'll spotlight the most impactful updates shipped across the platform, for charge point operators and e-mobility service providers building more efficient, secure, and reliable networks, and for the drivers who rely on them every day.

July was no exception. This month's release touched both the Operator Portal and the native mobile apps, with updates spanning fleet and location management, payment security, and app reliability. Here's what shipped.

‍

Operator Portal

Added parking data now aligned with AFIR & OCPI 2.3

Locations in the Operator Portal now have a dedicated way to describe the parking situation at a charging site: dimensions, usage restrictions, and which connectors sit in which spot. That's more than a nice-to-have for drivers navigating a site, it's increasingly what regulators expect too.

Regulators across Europe, through the Alternative Fuels Infrastructure Regulation (AFIR) and the OCPI 2.3 standard, increasingly expect charge point operators to publish structured, accurate location data to national access points. With this update, Ocean is AFIR compliant for this data, and it's sent automatically via OCPI 2.3, already supported for transmission to national access points.By capturing parking details directly in Ocean, operators have that data ready to share with roaming partners and regulators alike, without extra manual work down the line.

Multiple named user accounts for the Fleet Portal

Fleet customers have historically shared a single login across their whole team, which made it hard to know who did what, and painful to manage access whenever someone joined or left. Now, fleet accounts can  have multiple named user logins under one company, each with its own credentials.

Every action ties back to the person who took it, and access is managed centrally from the back office, so bringing a new team member on board, or cutting one off, no longer means passing around a shared password.

Equal share -a new load management strategy for cluster mode

Charging sites with many chargers on one shared grid connection constantly have to make tradeoffs about how to divide available power. Ocean's load management already offered a few ways to do that, including "As fast as possible" and "As slow as possible", avaialble for every location.

Now there's a fourth, built on an entirely fresh algorithm: "Equal Share" mode splits available power evenly across every active session, regardless of arrival time, departure time, or vehicle type. It's a simpler, more predictable option for busy, high-traffic sites, depots, and hubs with a lot of chargers or sub clusters to manage, where fairness between drivers matters more than optimizing any single session. For sites juggling a lot of simultaneous sessions, it's often the easier mode to reason about and support.

Payter cloud solution now recognizes RFID cards

Some chargers are installed without their own dedicated RFID reader and instead rely on the reader built into their payment terminal. Previously, tapping an RFID card at one of these terminals didn't work as expected, since the system tried to process it the same way it would a bank card. That gap is now closed for chargers using a Payter cloud integration: registered local users can tap their RFID card directly on the terminal and get authorized through their Ocean account, no separate reader required.

Alongside these, this release also shipped a long list of smaller improvements and fixes across roaming, billing, and the API, the kind of steady, behind-the-scenes work that keeps the platform reliable as it grows. Roaming connections gained stronger safeguards when they're blocked or migrated between partners, so identifications can't be misused mid-transition and sessions keep billing correctly throughout. Several endpoints continued their move to the newer version of Ocean's API, improving consistency for the integrators building on top of it. And a handful of smaller display and data-accuracy issues, in location photos, business partner logos, invoice sorting, and tariff handling, were cleaned up along the way.

‍

Mobile Apps

Mobile app Force update to minimum version defined by operator

Outdated app versions are one of the most common, and most avoidable, sources of support tickets. Ocean's native apps can now enforce a minimum supported version, prompting drivers running an outdated build to update before continuing, rather than running into issues caused by a mismatch with the current backend. Drivers on slightly older but still-supported versions get a softer touch instead: a recommended update prompt they can act on or dismiss, so adoption keeps moving without interrupting anyone mid-session.

Stronger fraud protection, and a small fix that matters

Card payments in the app are now backed by Braintree's Premium Fraud Management Tools, adding device-level fraud detection to every in-app transaction. It's a quiet upgrade, one drivers will likely never notice directly, but it adds a meaningful layer of protection behind the scenes as in-app payment volume keeps growing across the network. On a smaller note, drivers using imperial units now see distances and ranges displayed correctly in miles throughout the app, matching the polish that was already in place for metric users. Small as it sounds, it's the kind of detail that quietly shapes how much a white-label app feels finished.

‍

Also in this Release

Beyond the highlights above, July's release included plenty more under the hood. The Operator Portal picked up 16 additional improvements and features, including stronger safeguards for roaming connections, continued migration to a newer version of Ocean's API, more detailed connector and roaming data for integrators, and a new option to restrict roaming location visibility to a single country. It also cleared 13 bug fixes spanning invoicing accuracy, business partner data, location photos, and tariff handling.

On mobile, iOS and Android together shipped 16 additional bug fixes this release, plus a number of smaller, client-specific fixes that didn't make this list.

‍

Catch your next wave

This is the first of what will now be a regular monthly update. We'll keep highlighting the changes that matter most, whether you're operating a charging network on Ocean or just keeping an eye on where the platform is headed. See you next month. 🌊

‍