evion

Electric vehicle charging network operations platform

Admin panel, driver app and device communication in a single hub.

OCPP 1.6 · 2.0.1EPDK · GİB EŞÜMulti-tenantAndroid · iOS

How it works

Three parties, one hub

Devices in the field, the operations team and drivers all connect to the same hub; they do not communicate directly with one another. Decisions, pricing, records and payment collection all stay in one place.

Admin panel

Opens in the browser, no installation required.

  • Live monitoring and remote commands
  • Field inventory, tariffs, promotions
  • Customers, wallets, revenue report
  • The menu narrows to match the user's permissions

Central server

Identity, wallet and reservation checks · price freezing · payment collection · queue and retry

EPDKGİB EŞÜERPPayment institution

Driver app

A single app for Android and iOS.

  • Map, stations, favorites
  • Charging via QR code, live tracking
  • Wallet, card, invoice details
  • Reservations and notifications

Chargers

Every brand that speaks OCPP 1.6 and 2.0.1. They report status, meter readings and events, and carry out commands.

Admin panel

The entire network at a glance at the start of a shift

All stations on a map; connected and disconnected devices, connector occupancy distribution, the total power being drawn at that moment and daily revenue, all on the same screen.

  • Devices needing attentionDevices that report a fault and devices that are not sending a signal are in a separate list; fault detection does not depend on customer complaints.
  • Intervene from the markerSelect a device on the map and its connectors open up; with the right permission, charging can be started or stopped from here.
  • Latest charging transactionsCustomer, station, energy, amount and the channel that started the session; open the transaction details from the row.

Live monitoring

Remote intervention leaves field visits for physical problems only

A full-screen map and a side panel for the selected device: connection status, connectors, meter, live power.

  • Device commandsRestart, unlock cable, disable connector, set power limit, read/write settings, update software, request diagnostics file.
  • The result is recordedThe command sent, the device's response and the result are in the communication logs; if the device is not connected, the commands are closed.
  • Connector-level managementWhen one connector fails on a dual-connector charger, only that connector is shut down and the other keeps serving.

Field inventory

No brand restriction when choosing devices

In procurement there is only one verifiable question: does the device support OCPP 1.6 or 2.0.1? Different brands and versions appear on the same map, under the same tariff structure, in the same transaction list.

  • All device information in a single listBrand, model, current type, power, protocol, connectors, regulatory IDs, revenue share and maintenance status.
  • Bulk operations with ExcelTemplate-based import, one-click export; bulk updating of regulatory IDs.
  • Gradual renewalThe charger fleet is not replaced all at once; a new device is defined, its connectors are entered, its tariff is applied and it is put into service.

Transaction record

The price is frozen the moment charging starts

The tariff, discount and partner operator's share are written to the record of that charging session. Even if the tariff is updated later or a promotion ends, ongoing and completed sessions are not affected.

  • Amount breakdownEnergy × frozen tariff − discount; the revenue share is calculated at the same time. Refunds and extra charges are handled from this screen, with a separate permission.
  • Interruptions never create unbilled energyOn a device that loses its connection, the charging session is closed at the last meter value and billed.
  • Step-by-step timelineQR code, checks, command, device response, EPDK (Energy Market Regulatory Authority) notification and closing tasks on a single timeline.

Pricing

Tariff, promotion and final price calculator

Price per kilowatt-hour by current type, date and priority; different prices for different locations in the same network.

  • Targeted promotionA percentage discount for all drivers or selected groups; a notification is sent the moment it is saved.
  • Corporate agreements without changing the tariffDrivers are added to a group, the discount is linked to the group and takes effect the same day; when the contract ends, the link is removed.
  • See first, then changeBase price, discount and final price for the selected station and customer; used when planning a tariff.

Driver app

The driver never uses the charger's interface

One app for Android and iOS. Sign-in with a phone number and a one-time password; if registration is left unfinished, it resumes where it left off.

  • Map and searchClustered markers; filtering by current type, power and free connector; distance, arrival time and price.
  • Station pageConnector power, type, price and live status; photos, ratings, operating hours; adding to favorites.
  • Different device, same experienceWhatever the brand, charging starts and ends with the same steps.

Charging flow

From QR code to payment collection, in the driver's hands

The cable is plugged in and the connector's code is scanned; the hub checks the balance, connector and reservation, freezes the tariff and sends the start command to the device.

  • Live trackingCharge level, duration, energy delivered, amount and live power; notification at the chosen charge level; stop from the app.
  • If the code cannot be readThe connector's short code is entered manually. If the phone is off, the call center starts the session on behalf of the customer.
  • In the background when charging endsThe amount is calculated and deducted from the wallet, the EPDK end notification and the invoice request are queued, and a notification is sent to the driver.

Payment model

Wallet first, then charging

The balance is topped up in advance by card; the charging fee is deducted from the balance at the end. Because the deduction does not depend on an external system, it completes under all conditions.

  • At most one open charging feeNo new charging session is opened and no new top-up is processed until the negative balance is cleared; the rule applies in all three channels.
  • Card details are not stored on the platformThey are stored at the payment institution; every transaction goes through the bank's 3D Secure verification. Only the last four digits are visible in the admin panel.
  • ReservationReserving a connector by date, time and vehicle; a reminder 15 minutes in advance; the connector is released automatically when the reservation expires.

Regulatory processes and accounting

Three official flows, zero separate data entry

The EPDK notification, the GİB (Turkish Revenue Administration) charging unit registration and the invoice request are triggered by the charging event. A request that cannot be delivered stays in the queue and is retried; a second request for the same charge is blocked.

  • EPDKThe start and end of charging, the energy delivered and connector status changes are transmitted instantly; price information is synchronized with the authority.
  • GİB charging unit registrationNew registration, update, taxpayer status, transfer and closure; for a single device or in bulk.
  • Period closeThe time, content and response of every exchange are recorded; whether any record remains unsent is visible at a glance.

Charging network management

Partner operators, tenants and permission-based authorization

A shopping mall, hotel, fuel station or public institution is defined as an operator; its locations are linked, and the revenue share is written to the record at the start of each charge.

  • Sees their own locationOperator users see only their own devices; periodic settlement is carried out from the revenue-sharing report.
  • New tenant = independent setupA second brand or a separate network is opened on the same infrastructure, with its own stations, tariffs and users.
  • Roles are built from permissionsThe menu narrows to match the user's permissions; phone, ID, tax and card fields are masked for users without permission.

A system that runs in the field and whose workload does not grow with scale

As the number of devices and customers grows, the work of defining prices, registration, payment collection and notification does not grow at the same rate; this work runs centrally and automatically.

HubASP.NET Core · ABP Framework · OCPP 1.6 / 2.0.1 WebSocket server · background services
ApplicationsAdmin panel (browser) · Android and iOS driver app · RESTful mobile API
IntegrationsEPDK ŞEBİS · GİB EŞÜ · ERP invoice transfer · 3D Secure payment institution · push notification infrastructure

Evion was developed by Karatsoft Teknoloji.

1 / 13