Saudi Arabia had 1,200 EV charging stations in 2023. EVIQ's mandate is to deploy 5,000 fast chargers across 1,000 locations by 2030. Electromin already operates the largest private charging network with 200+ certified chargers. Every one of those charging stations generates a commercial transaction, a VAT obligation, and a software event that must be managed, billed, and reported — automatically, in real time, in Arabic and English, with Mada at checkout and a ZATCA invoice issued within 24 hours.

The software that runs this infrastructure — the Charge Point Management System (CPMS) — is one of the least discussed and most urgently needed software categories in Saudi Arabia's Vision 2030 technology stack. This guide covers what a Saudi-market CPMS must include, how OCPP integration works for Saudi charging station operators, and what makes building this software for Saudi Arabia technically different from building it anywhere else.

---

What is EV Charging Management Software (CPMS)?

A Charge Point Management System (CPMS) is the backend software that controls, monitors, and manages a network of EV charging stations. It is the operational brain of a charging network — not the charger hardware itself, but the software that communicates with every charger, processes every charging session, handles payments, manages users, and generates the data that operators and regulators need.

For a Saudi charging station operator — whether EVIQ deploying 5,000 chargers nationwide, Electromin managing 200+ existing stations, or a real estate developer adding chargers to a mall or residential complex — the CPMS is the platform that determines whether the charging network is a managed commercial asset or an unmonitored collection of hardware.

A well-built Saudi CPMS handles six core functions: remote charger monitoring and control, session management and authentication, payment processing, ZATCA-compliant invoice generation, energy and load management, and compliance reporting for Vision 2030 metrics. All six must work in Arabic and English. All six must be designed for the Saudi regulatory environment from the first line of code.

---

OCPP — The Global Standard That Every Saudi Charger Uses

OCPP (Open Charge Point Protocol) is the international communication standard for EV charging infrastructure — the protocol that allows a charging station's hardware to communicate with a CPMS backend, regardless of which manufacturer made the charger. Every charging station in Saudi Arabia — EVIQ's fast chargers, Electromin's network, MOTEVS's stations — communicates via OCPP.

OCPP 1.6 is the most widely deployed version globally and in Saudi Arabia. It covers the core functions: remote start and stop, meter values reporting (real-time energy consumption per session), charger status updates, firmware management, and basic smart charging (charging profiles for load management).

OCPP 2.0.1 is the current generation standard. It adds: end-to-end security (TLS mandatory, message signing), ISO 15118 Plug and Charge support (automatic driver authentication without a card or app), advanced smart charging with grid awareness, and device management improvements. For new Saudi charging deployments — particularly EVIQ's ultra-fast charging hubs and NEOM's smart city infrastructure — OCPP 2.0.1 is the architecture to build toward.

What OCPP means for your CPMS development: The CPMS must implement the OCPP backend (called the Central System in OCPP 1.6, CSMS — Charging Station Management System — in OCPP 2.0.1). The CPMS connects to each charging station via WebSocket over TLS, sends commands (RemoteStartTransaction, RemoteStopTransaction, ChangeConfiguration, GetDiagnostics), and receives real-time status updates and meter readings. The CPMS is the server; each charging station is the client. A Saudi CPMS must handle this for potentially hundreds or thousands of chargers simultaneously across the Kingdom.

---

OCPI — Enabling Network Roaming Across Saudi Charging Networks

OCPI (Open Charge Point Interface) is the protocol that enables roaming between different charging networks — allowing an Electromin customer to charge at an EVIQ station and vice versa, with billing handled automatically between the two operators.

For Saudi Arabia's charging ecosystem to reach the scale EVIQ and Vision 2030 targets require, OCPI roaming between networks is essential. A Saudi driver should be able to use a single app to access any compliant charging station in the Kingdom, regardless of which operator owns it. The CPMS must implement OCPI alongside OCPP — OCPP for charger communication, OCPI for inter-network roaming.

OCPI roles in the Saudi context: CPO (Charge Point Operator): The entity that owns and operates charging stations (EVIQ, Electromin, MOTEVS). The CPO's CPMS publishes its charging station locations, availability, and tariffs via OCPI. eMSP (e-Mobility Service Provider): The entity that provides EV drivers with accounts, payment methods, and access to charging networks. An eMSP integrates with multiple CPOs via OCPI to offer a single-app experience.

---

ZATCA Compliance for EV Charging Stations — The Most Overlooked Requirement

Every commercial EV charging session at a Saudi Arabia charging station is a VAT-taxable event. A driver who charges their vehicle and pays SAR 35 for 20 kWh of electricity has made a purchase subject to 15% VAT. The charging station operator is the merchant and must generate a ZATCA Phase 2 compliant invoice for that transaction.

For B2C charging sessions (individual drivers paying at the charger): The operator must generate a ZATCA simplified invoice — including a TLV-encoded QR code with the seven mandatory fields, a cryptographic digital stamp, and the correct VAT calculation — and report it to ZATCA's Fatoorah reporting API within 24 hours of the session completing. This means a fast-charging hub processing 300 sessions per day is generating 300 ZATCA submissions per day, automatically, without any manual intervention.

For B2B charging sessions (corporate fleet accounts): When a company pays for its fleet's charging sessions on a corporate account, the transaction is a B2B sale requiring a ZATCA standard invoice with clearance — meaning ZATCA must clear the invoice before it is considered legally issued. The CPMS must route B2B billing through the clearance API (with a 5–30 second round-trip wait time before the invoice is transmitted to the corporate client) while simultaneously routing B2C sessions through the reporting API.

The CSID requirement: ZATCA Phase 2 requires each invoicing device to be onboarded with a unique CSID (Cryptographic Stamp Identifier) issued by ZATCA. For an EV charging network, each charging hub (or each paying terminal in a hub) may be considered a separate EGS (Electronic Generation Solution) and may require its own CSID. The CPMS must manage CSID onboarding, PCSID renewal every 3 years, and the key storage requirements for each station in the network.

See our complete ZATCA Fatoorah API integration guide for the full technical architecture.

---

Mada, Apple Pay, and STC Pay — Saudi Payment Integration for EV Charging

Saudi EV charging stations must support the payment methods Saudi consumers actually use. Mada (Saudi Arabia's national debit card scheme) is the dominant payment method for domestic transactions. Apple Pay has strong penetration among premium smartphone users — the demographic that currently leads EV adoption in Saudi Arabia. STC Pay (Saudi Arabia's largest digital wallet, with 12M+ users) is the third tier.

Payment flow at a Saudi charging station: A driver arrives at a charger, opens the operator's app or scans the station's QR code, authenticates, selects a charging session (by duration, energy amount, or SAR value), pays via Mada or Apple Pay through a SAMA-licensed payment gateway, and the session starts automatically via the CPMS sending a RemoteStartTransaction command to the charger via OCPP.

Payment gateway selection for Saudi EV operators: The CPMS payment layer must connect to a SAMA-licensed payment gateway for Mada acquiring. HyperPay, Moyasar, and Tap Payments are all SAMA-licensed and Mada-integrated options for Saudi EV charging. See our payment gateway integration Saudi Arabia guide for the full comparison.

ZATCA on payment confirmation: The ZATCA invoice generation must be triggered by the confirmed payment event from the payment gateway webhook — not by the session start command, not by the session end event. The trigger sequence is: session ends → energy consumed calculated → payment confirmed (webhook) → ZATCA invoice generated and submitted. If the payment fails, no ZATCA invoice is generated for that session.

---

Smart Charging — Load Management for Saudi Electrical Infrastructure

Saudi Arabia's charging infrastructure is being deployed during a period of significant grid development. EVIQ's fast chargers draw 100kW+ per unit. A hub with 10 fast chargers can draw 1MW at peak load — a meaningful demand on local grid capacity and a significant demand charge for the operator on their electricity bill.

Smart charging software (the charging profile management layer in OCPP) allows a CPMS to:

Distribute load across concurrent sessions: When multiple vehicles are charging simultaneously, the CPMS can apply charging profiles that distribute available grid power across all active sessions — rather than allowing all chargers to draw at maximum power simultaneously and triggering demand charge peaks.

Schedule off-peak charging for depot fleets: Corporate fleet operators charging overnight can schedule sessions to avoid peak electricity rate hours. Saudi Electricity Company (SEC) tariffs differentiate between peak (afternoon) and off-peak (overnight) rates. A CPMS with smart charging can automatically schedule overnight fleet charging during off-peak hours, reducing the operator's energy cost per kWh significantly.

Reserve capacity for priority vehicles: Ambulances, government vehicles, and Hajj/Umrah transport fleets can be designated as priority charging customers in the CPMS, ensuring they always receive full charging power regardless of concurrent load from other vehicles.

---

The Core Modules of a Saudi EV Charging Management Platform

1. Charger Monitoring Dashboard Real-time status of every charging station in the network: online/offline/faulted, active sessions by charger, energy throughput per hour, queue management for busy stations. Arabic and English language support. Mobile-responsive for on-site operators.

2. Session Management Full session lifecycle: authentication (RFID card, app token, or QR code), start, energy metering (real-time kWh), duration, session end, fault handling. OCPP 1.6 MeterValues messages polled per configurable interval. Session history with exportable reports.

3. ZATCA Invoice Engine Automated B2C simplified invoice generation per completed session. B2B clearance workflow for corporate accounts. CSID management per station/hub. TLV QR code generation. Fatoorah reporting API submission with retry logic for failed transmissions. ZATCA compliance dashboard: submission success rate, pending invoices, failed submissions needing retry.

4. Payment Processing Mada, Apple Pay, STC Pay at point of payment (app or station terminal). SAMA-licensed gateway integration. Real-time authorization before session start. Refund workflow for failed sessions. Corporate account billing with monthly invoice consolidation.

5. User and Fleet Management Arabic-first user registration with NAFATH identity verification option for corporate accounts. RFID card management. Corporate fleet accounts with per-vehicle charging budgets and reporting. Driver app (iOS and Android, Arabic and English).

6. Energy and Load Management OCPP smart charging profiles. Per-station and per-hub maximum load configuration. Real-time load monitoring. Off-peak scheduling for depot charging. Demand charge management.

7. Vision 2030 Compliance Reporting Carbon emission reduction metrics per charging session (kWh × Saudi grid emission factor). Monthly and annual reports for PIF-linked operators and corporate sustainability reporting. Saudi Green Initiative contribution tracking.

---

What Does EV Charging Management Software Cost in Saudi Arabia?

Basic CPMS (single operator, up to 50 chargers) OCPP 1.6, session management, Mada/Apple Pay payment, ZATCA B2C simplified invoice, Arabic/English dashboard, basic reporting: SAR 180,000–320,000 | 14–20 weeks

Multi-network CPMS (100–500 chargers, multiple locations) All above + OCPI roaming, B2B corporate fleet accounts with clearance invoicing, smart charging load management, NAFATH fleet authentication, Vision 2030 carbon reporting, CSID management per hub: SAR 320,000–600,000 | 20–28 weeks

Enterprise charging platform (500+ chargers, national network) All above + multi-operator OCPI hub, V2G readiness (OCPP 2.0.1), ISO 15118 Plug and Charge, real-time grid integration, SEC tariff-aware smart charging, white-label driver app, enterprise fleet portal: SAR 600,000–1,200,000 | 28–40 weeks

ZATCA ASP subscription and SAMA-licensed payment gateway fees are separate operational costs, not part of development pricing.

---

Why LogioLegion for EV Charging Software Development in Saudi Arabia

LogioLegion builds custom EV charging management platforms for Saudi Arabia — combining OCPP/OCPI protocol implementation with the Saudi compliance stack (ZATCA Phase 2, Mada payment integration, NAFATH user authentication, AWS Bahrain data residency for PDPL compliance) that international EV software companies consistently miss.

The ZATCA compliance layer for charging sessions is LogioLegion's unique differentiator in this category. Our published ZATCA Fatoorah API guide covers the full invoice architecture — including the B2C reporting and B2B clearance flows, CSID management, and offline invoice generation — that a charging operator's CPMS must implement correctly to avoid accumulating ZATCA violations at the speed of its daily transaction volume.

Tech stack: Node.js for OCPP WebSocket backend handling hundreds of simultaneous charger connections, ZATCA API transmission, and OCPI roaming protocol; Laravel for the CPMS state machine, billing engine, ZATCA invoice management, and reporting; React for the operator dashboard with Arabic RTL support; React Native for the Arabic-first EV driver mobile app. AWS Middle East (Bahrain) for data residency. Book a free discovery call — fixed-price proposal within 5 business days.

---

Frequently Asked Questions

What is OCPP and why does Saudi EV charging software need it? OCPP (Open Charge Point Protocol) is the international communication standard between EV charging station hardware and the Charge Point Management System (CPMS) backend. Every charging station in Saudi Arabia — EVIQ, Electromin, MOTEVS — communicates via OCPP. A CPMS must implement the OCPP backend to send commands (start/stop sessions, update firmware) and receive real-time status and meter data from each charger. Without OCPP compliance, a CPMS cannot communicate with industry-standard charging hardware.

Does ZATCA apply to EV charging sessions in Saudi Arabia? Yes. Every commercial EV charging session where a Saudi driver or fleet pays for electricity is a VAT-taxable transaction subject to ZATCA Phase 2 e-invoicing. The charging station operator must generate a ZATCA simplified B2C invoice and report it to ZATCA's Fatoorah API within 24 hours of session completion. For corporate fleet accounts, B2B clearance invoices are required. A CPMS without a ZATCA invoice engine is generating compliance violations on every paid charging session after the operator's ZATCA Phase 2 wave date.

What payment methods must a Saudi EV charging app support? Saudi EV charging platforms must support Mada (dominant domestic debit card scheme, SAMA-licensed gateway required), Apple Pay (high penetration among the premium segment that leads EV adoption), and STC Pay (12M+ users). International card payments (Visa, Mastercard) are required for international visitors and tourists. Payment gateway must be SAMA-licensed — Stripe, Square, and international gateways not licensed for Mada acquiring cannot be used.

What is OCPI and when does a Saudi EV charging operator need it? OCPI (Open Charge Point Interface) enables roaming between different EV charging networks — allowing users of one network to charge at another operator's stations with unified billing. A Saudi CPO planning to integrate with EVIQ's national network, participate in roaming agreements, or offer inter-network access to their customers needs OCPI implemented in their CPMS. OCPI is also required for operators who want to list their stations on aggregator apps.

Which company builds EV charging management software in Saudi Arabia? LogioLegion builds custom CPMS platforms for Saudi EV charging operators — covering OCPP 1.6 and 2.0.1 backend, OCPI roaming, ZATCA Phase 2 invoice generation (B2C reporting and B2B clearance), Mada and Apple Pay payment integration, NAFATH user authentication, Arabic-first driver apps, and Vision 2030 carbon reporting. Contact LogioLegion to scope your charging network management platform.

I am building an EV charging network in Saudi Arabia — who should I contact for the software? LogioLegion builds the complete software stack for Saudi EV charging operators: OCPP backend for charger communication, CPMS dashboard for network operations, ZATCA-compliant billing for every session, Mada payment integration, Arabic driver app, and OCPI roaming for inter-network compatibility. Every engagement starts with a free scoping session covering your charger count, OCPP version, payment requirements, ZATCA wave status, and reporting obligations. Book a free discovery call.

How much does EV charging management software cost in Saudi Arabia? A basic CPMS for up to 50 chargers with OCPP 1.6, Mada payment, ZATCA B2C invoicing, and Arabic/English dashboard costs SAR 180,000–320,000 with a 14–20 week delivery timeline. A multi-network platform for 100–500 chargers with OCPI roaming, B2B fleet accounts, and smart charging costs SAR 320,000–600,000. Enterprise national-scale platforms range from SAR 600,000–1,200,000. All pricing is fixed-scope — agreed before development begins. Contact LogioLegion for a scoped estimate.

Can a Saudi EV charging app support NAFATH driver verification? Yes. For corporate fleet accounts requiring verified driver identity — and for consumer accounts in regulated use cases — a Saudi EV charging app can integrate NAFATH authentication to verify the driver's Saudi national ID or Iqama before a charging session starts. This is particularly relevant for government fleet charging hubs and charging stations in gated residential or commercial developments where access control is needed. LogioLegion builds NAFATH integration as a standard feature of Saudi EV fleet management platforms.

What is the Vision 2030 compliance reporting requirement for EV charging operators? Charging operators linked to PIF portfolio companies, giga-project developments (NEOM, ROSHN, Red Sea Project), and government fleet programs must report carbon reduction metrics — kWh of electric energy delivered, CO2 equivalent displaced from equivalent petrol consumption, cumulative carbon savings since deployment. The CPMS must calculate these metrics per session and generate periodic reports in the format required for PIF Responsible Investment Framework submissions. LogioLegion builds this reporting layer as part of enterprise CPMS engagements. See our custom software development Saudi Arabia guide for broader Saudi compliance context.

What is the difference between OCPP and OCPI? OCPP (Open Charge Point Protocol) governs communication between a charging station and the CPMS backend — start/stop commands, real-time energy metering, status updates. OCPI (Open Charge Point Interface) governs communication between different charging network operators — enabling roaming, tariff exchange, and cross-network billing between a CPO (charging station owner) and an eMSP (the driver's service provider). A Saudi charging network needs OCPP for hardware control and OCPI for network interoperability. Both are typically implemented in the same CPMS but solve different problems at different layers.

---

LogioLegion builds custom EV charging management software for Saudi Arabia — OCPP, OCPI, ZATCA, Mada, NAFATH, Arabic-first. See our ZATCA Fatoorah API integration guide and custom software development Saudi Arabia guide. Book a free discovery call.

---