Create an account
Give drivers one place for identity, vehicles and charging history.
iVoltia Smart OS
Software visibility for availability, sessions, energy, power and diagnostics.
TWO EXPERIENCES, ONE CHARGING OPERATION
The mobile app serves the person charging. The operator platform serves the organization running the network. We connect both to charging hardware and a defined support process.
From account creation to payment and charging history.
Give drivers one place for identity, vehicles and charging history.
Show eligible stations and start a session by scanning the charger code where enabled.
Add supported payment methods and review price information before charging.
See session progress, energy and past charging activity in the app.
Monitor, diagnose and improve a single station or a multi-site network.
Review availability, active sessions and site-level performance in one place.
Compare energy, utilization, session volume and trends to guide expansion.
Use device-level alerts and richer native telemetry to identify issues faster.
Configure user groups, tariffs and billing workflows within the licensed scope.
Connect iVoltia devices deeply and evaluate third-party chargers through OCPP.
Turn alerts into assigned actions, record resolution and track recurring issues across sites within the agreed software scope.
WHY AN INTEGRATED STACK
With iVoltia hardware, the platform can use deeper equipment diagnostics than a basic third-party protocol connection. This helps teams distinguish a vehicle, charger, network or site-power issue. Available signals and remote actions depend on model and software scope.
Product functions, payment providers, data fields, OCPP commands and service levels are confirmed for each destination and contract.
YOUR QUESTIONS, ANSWERED
Practical answers about Software. No guesswork.
Ask about your project8 questions
The app is for charging users: accounts, station access, session start, payment and history. The operator platform is for teams managing sites, devices, sessions, alerts and performance.
A scan-to-start flow can be configured. Confirm the code format, user authorization, network behavior, charger interface and exception handling for the project.
Methods, currencies, taxes, settlement and refunds depend on the destination market and payment provider. These integrations must be scoped and tested.
Depending on configuration, operators can review device status, sessions, power, energy and faults. Data fields, refresh rate, retention and export rights are agreed in the software scope.
OCPP-based integration can be evaluated. Commands and diagnostic depth depend on the third-party model, firmware, protocol version and joint testing.
Native hardware and software integration can provide richer equipment telemetry and a clearer diagnostic path. Exact data and remote actions depend on the selected model and license.
Offline authorization, session storage, synchronization and manual recovery must be specified for the device and operation, then tested during acceptance.
Purchase, subscription and integration models can be discussed. Supported devices, features, service levels and fees are defined in the proposal.
No matching question. Try another word or contact our team.
YOUR NEXT PROJECT
Your vehicles. Your site. Your operating goals. Start a conversation around the system you actually need.