zevOS

01Features · Drivers & partners

Tap to charge for the drivers who charge every day

Bus depots, delivery fleets and taxi operators do not want a payment flow per session; they want a card that works and one invoice at month end. zevOS handles the authorisation side of that — who may charge, where, how much, and on whose account.

RFID & fleet authorisation

  • Local + central list

    Auth

  • Per driver, per period

    Limits

  • Prepaid or post-paid

    Billing

Capabilities

What this gives you

01

ID tags and whitelists

Issue tags to drivers and vehicles, and control exactly which stations each tag may start a session on. Authorisation is answered centrally, with a local list maintained on the charger so a network blip does not strand a depot.

  • Central Authorize handling with cached local list
  • Block or expire a tag instantly across the network
  • Tag-to-driver and tag-to-vehicle mapping
02

Driver groups

Group drivers by fleet, department or site. The group carries the tariff, the station access and the spending limits, so onboarding a new driver is one assignment.

03

Limits and balances

Cap energy or spend per session, per day or per month, and check balance before authorising so a prepaid account cannot go negative.

04

Authorisation log

Every authorisation decision — accepted, blocked, expired, out of credit — is logged with its reason, which is what you need when a driver insists the card did not work.

Questions

What operators ask about this

Which RFID standards are supported?

Any tag the charger can read and present as an OCPP idTag — in practice MIFARE and compatible 13.56MHz cards, which is what nearly all Indian chargers ship with.

Can a fleet be billed monthly instead of per session?

Yes. Fleet accounts can run post-paid, with sessions accumulating to a monthly invoice, or prepaid against a balance.

See rfid & fleet authorisation working

A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.