Release date 

New features

Suspended status available in Tokens API
  • Affected users:
    • Users of Tokens API
  • Affected flows:
  • Description:
    We've added a Suspended status for tokens, which allows a token's subscription to continue but stops it from being accepted as valid by any station (private, public, or roaming). This means you can stop your customers from using their token when they fail to pay for their subscriptions, and resume it when they have met their payment obligation. You can change the status for both individual and multiple tokens, depending on your needs. 

API ONLY
As the first part of this release, it's only possible to suspend a token using the API. In doing so, its Suspended status appears both in the Cards list and a specific card's Overview tab. The dropdown that you would normally use to change the status of a card isn't fully developed yet for this status, and will be part of a future release. However, if the card is already suspended via the API, you can click the status opposite to its current one to resume the card as needed through the UI. It's advised to use the API if you're unsure.
Learn more about card statuses.
Don't have access to Tokens API? Contact support for more information.

Get the effective charging time using Billing API
  • Affected users:
    • Users of Billing API
  • Affected flows:
  • Description:
    We've added two additional fields to the response body of our transactions endpoint: chargingStartedAt and chargingStoppedAt. These values are communicated by the station via OCPP, and they represent the time at which the EV actually started and stopped consuming power from the station. This allows you to calculate the effective charging time for newly generated transactions. It also means you can get insight into idling times, by comparing the effective charging time with the total duration of the transaction. Roaming doesn't communicate the values needed to calculate the effective charging time yet, meaning these values only apply to stations active within your own tenant environment.

API ONLY
Don't have access to Billing API? Contact support for more information.

Changes and improvements

Drivers have access to their billing information

Billing API now available in our developer portal
  • Affected users:
    • Users of Billing API
  • Description:
    Our Billing API enables you to integrate your billing systems with your tenant. Both the specification and documentation are now available in our developer portal! Check it out here.
    Don't have access to Billing API? Contact support for more information.

Bug fixes

Sub-account owners couldn't access their billing information

Users of sub-accounts with the account owner or account admin role were unable to view or edit their account's billing information. This is solved.

Stations couldn't receive messages from SMATCH®

Outgoing messages for SMATCH® weren't received by stations. This meant that current restrictions weren't applied as they should have been. This is solved.

Activation emails couldn't be resent to customers who used self-signup

When customers signed up for their own account and forgot to complete activation using the link sent to their email, they were unable to reset their password to receive a new link. It also wasn't possible for users with the tenant admin or customer support role to resend them an activation link. This is solved.

Known issues

The CDR import tool returns an error

An error occurs when uploading CDRs to the import tool. The error states that the token isn't public or doesn't belonging to the originating tenant, and shows a different Contract ID than the one in the CDR.

Users can't change their own email address

After users edit and save a new email address, it's reverted back to the previous one. Tenant admins can change email addresses for others if needed.

Redundant site checkbox appears on location tab

Tenant users who are allowed access to station information see a redundant site checkbox and disclaimer appear on the location tab. This only happens for stations that belong to accounts without any sites. 

"OKTA" label

Bug fixes and known issues that are labeled as OKTA only apply to tenants whose user database was migrated to Okta