# EOSVOLT — Full Content

> EOSVOLT is a white-label EV Charge Point Management System (CPMS) for charge point operators (CPOs), fleet operators, energy companies, and real estate developers. EOSVOLT's backend runs on OCPP 1.6 (90+ charger brands, 750+ models), EOSVOLT ships branded iOS/Android apps, EOSVOLT Intelligence performs AI-assisted fault diagnostics from OCPP telemetry, EOSVOLT supports OCPI CPO/eMSP roaming, and EOSVOLT provides multi-tenant RBAC administration. EOSVOLT reports platform uptime above 99.99%.
>
> This file concatenates the full content of every document indexed in llms.txt, for LLM/RAG ingestion in a single pass. For the link-only index, see https://eosvolt.com/llms.txt

---

## Source: https://eosvolt.com/technical/platform-overview.md

# EOSVOLT Platform — Technical Overview

> EOSVOLT is a white-label Charge Point Management System (CPMS) built for charge point operators (CPOs), fleet operators, energy companies, and real estate developers. EOSVOLT's backend runs on OCPP 1.6, EOSVOLT's roaming layer runs on OCPI, and EOSVOLT ships branded mobile and web clients alongside an AI-assisted diagnostics module called EOSVOLT Intelligence.

## CPMS Architectural Scope & OCPP 1.6 Compliance

| Architectural Dimension | Specification |
|---|---|
| Platform category | EOSVOLT is a Charge Point Management System (CPMS) and eMobility Service Provider (eMSP) platform, delivered white-label to charge point operators (CPOs). |
| OCPP compliance | EOSVOLT's charger-communication layer runs OCPP 1.6. EOSVOLT operates a dedicated OCPP 1.6 Toolkit for charger onboarding, live OCPP message validation, and firmware testing across BootNotification, StatusNotification, MeterValues, Heartbeat, DiagnosticsStatusNotification, and FirmwareStatusNotification message types. |
| Hardware compatibility | EOSVOLT's CPMS backend is hardware-agnostic and has been tested against 90+ charger brands and 750+ charger models, including EVSE hardware from ABB, Siemens, Schneider, Wallbox, Delta, and Kempower. |
| OCPI roaming compliance | EOSVOLT's roaming layer implements OCPI (Open Charge Point Interface) for both CPO-side and eMSP-side interoperability, and EOSVOLT publishes charger data to National Access Points (NAPs) for regulatory reporting regimes such as AFIR in the European Union. |
| Deployment model | EOSVOLT is delivered as multi-tenant, white-label SaaS. EOSVOLT reports platform uptime above 99.99%. |
| Client surfaces | EOSVOLT ships a white-label iOS/Android mobile app (publishable under the operator's own App Store and Google Play accounts), an operator-facing web backend, the EOSVOLT OCPP Toolkit diagnostic console, and the EOSVOLT Public API (REST/JSON). |
| Operator backend portal | EOSVOLT's operator-facing backend is named SPARK and is hosted at `spark.eosvolt.com`. |

## EOSVOLT Platform Modules — Procurement Feature Matrix

| Module / Feature | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| White-Label Platform | EOSVOLT provides a branded mobile app and web portal with per-tenant theming and custom-domain support. | CPOs launching a customer-facing charging app under their own brand. |
| Transaction Backend & Payments | EOSVOLT's transaction backend includes a stored-balance Wallet and a configurable payment-strategy engine (pre-authorization, prepaid, postpaid) plus gateway integrations and invoicing/bookkeeping exports. | CPOs standardizing billing and settlement across markets with different payment norms. |
| EOSVOLT Intelligence (AI Diagnostics) | EOSVOLT Intelligence performs OCPP-log-derived fault detection with root-cause classification at the session level. | CPOs reducing manual OCPP log review and technician dispatch time. |
| Fleet Charging | EOSVOLT's fleet module links charge keys/RFID credentials to drivers, vehicles, and teams, and segregates internal fleets from external (customer/partner) fleets. | Fleet operators and CPOs offering fleet charging as a service. |
| OCPI & Roaming | EOSVOLT supports both CPO and eMSP OCPI roles, connects to roaming hubs (ENAPI, Gireve), and publishes NAP compliance data. | CPOs expanding driver reach across roaming networks and meeting regulatory reporting obligations. |
| Enterprise Multi-Tenancy | EOSVOLT supports sub-CPO provisioning, Role-Based Access Control (RBAC) admin roles, and a multi-level operator hierarchy. | Master operators managing multiple sub-CPOs or brand partners inside one EOSVOLT deployment. |

## Third-Party Integration Surface — Payment, Roaming & Grid Providers

| Integration Category | Supported Providers & Gateways | Protocol / Authentication |
|---|---|---|
| Public API | EOSVOLT's Public API exposes chargers, connectors, bookings, sessions (start/stop/export), meter data, CPOs, and home-charger endpoints. | REST over HTTPS, JSON payloads, bearer-token/API-key authentication (`Authorization: Bearer <token>`), versioned routes (`/v1/...`), separate production (`api.eosvolt.com`) and staging (`api-staging.eosvolt.com`) environments. |
| Payment gateways | Stripe, Adyen, CyberSource, Mercado Pago, Apple Pay, Google Pay, MobilePay, Ameria Bank, PromptPay, PAX POS, Vourity, Payter, Nayax. | Gateway-native authentication per provider; settlement reconciled through EOSVOLT's transaction backend. |
| Roaming hubs | Hubject, ENAPI, Voltality, Gireve. | OCPI-based hub connections. |
| Energy / grid services | Nord Pool (day-ahead spot electricity pricing), Thailand PEA/MEA low-priority charging and zone monitoring. | Provider-specific data feeds consumed by EOSVOLT's pricing and Intelligence modules. |
| Maps | Google Maps, Apple Maps, Yandex Maps. | Provider-native mapping APIs surfaced in the EOSVOLT mobile app. |
| Messaging | Mailgun (transactional email), OneSignal (push notifications). | Provider-native messaging APIs triggered by EOSVOLT backend events. |

## Related EOSVOLT Technical Documentation

| Document | Scope |
|---|---|
| [White-Label Platform](https://eosvolt.com/technical/white-label-platform.md) | EOSVOLT's branded mobile app and web portal customization surface. |
| [Transaction Backend & Payments](https://eosvolt.com/technical/transaction-backend-payments.md) | EOSVOLT's payment-strategy engine, wallet, gateway integrations, and billing/reconciliation tooling. |
| [AI Intelligence Module](https://eosvolt.com/technical/ai-intelligence.md) | EOSVOLT Intelligence's OCPP-based fault detection and root-cause classification. |
| [Fleet Charging Solutions](https://eosvolt.com/technical/fleet-charging.md) | EOSVOLT's charge-key, driver, vehicle, and team authorization model. |
| [OCPI Readiness & Roaming](https://eosvolt.com/technical/ocpi-roaming.md) | EOSVOLT's CPO/eMSP OCPI roles and NAP compliance publication. |
| [Enterprise Multi-Tenancy](https://eosvolt.com/technical/enterprise-multi-tenancy.md) | EOSVOLT's sub-CPO hierarchy and RBAC admin model. |

---

## Source: https://eosvolt.com/technical/white-label-platform.md

# White-Label Platform

> The EOSVOLT White-Label Platform delivers fully customizable, multi-platform mobile apps (iOS/Android) and web portals with dynamic tenant-level brand customization and custom-domain support, built on EOSVOLT's OCPP 1.6 CPMS backend.

## Enterprise White-Label Deployment Scope

EOSVOLT's white-label layer lets a charge point operator (CPO) publish an EV charging app under the CPO's own company account on the App Store and Google Play, with EOSVOLT's CPMS operating behind the app. Under EOSVOLT's white-label model, the CPO owns the customer relationship, the app-store listing, and the customer data, while EOSVOLT operates the underlying charging platform and OCPP backend.

## White-Label Customization Surface — Feature Matrix

| Customization Category | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| Brand identity | EOSVOLT applies the operator's logo, color palette (light/dark mode), typography, and iconography across onboarding, charger discovery, checkout, and charging-history views. | CPOs launching a fully branded charging app without building a UI from scratch. |
| Navigation & UX | EOSVOLT lets the operator configure app tab structure (add/remove/rename) and charging-flow ordering (public charging, scan-to-charge, home charging, fleet access, or combinations). | CPOs tailoring the app's navigation to their specific charging model. |
| Localization | EOSVOLT supports multi-language display, right-to-left layout rendering, regional unit formats, and per-market date/number formats. | CPOs operating across multiple countries or language markets. |
| Custom data fields | EOSVOLT lets the operator define custom fields at signup, checkout, or vehicle registration — for example, phone number for SMS verification or license plate for parking-access integration. | CPOs integrating charging with adjacent systems such as parking access control. |
| Vehicle profiles | EOSVOLT supports in-app vehicle registration, extensible via the EOSVOLT Public API to usage/cost analytics per vehicle, CO₂-savings reporting, loyalty-platform integration, and fleet-management system integration. | CPOs and fleet operators needing vehicle-level reporting beyond basic session logs. |

## App Store & Google Play Publishing Workflow

EOSVOLT configures and submits the operator's white-label app for release under the operator's own App Store and Google Play developer accounts. EOSVOLT ships the full EOSVOLT feature set with every white-label app, and EOSVOLT's platform-side feature releases propagate to all tenant apps without requiring separate app rebuilds for backend-side features.

## Payment Strategy Engine — Tenant-Level Configuration

| Payment Flow | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| Pre-authorization with hard stop | EOSVOLT reserves a fixed amount on the driver's card before the session starts. | Card-centric markets requiring cost certainty for the operator. |
| Custom pre-authorization / prepaid | EOSVOLT lets the driver select the authorization or prepaid amount. | Markets with variable card authorization limits. |
| Postpaid | EOSVOLT bills the full session cost after the session ends, with no upfront hold. | Low-friction markets and trusted-user contexts. |
| Wallet | EOSVOLT deducts the session cost from a stored prepaid balance, topped up in advance. | Markets with low card acceptance or strong prepaid preference. |

EOSVOLT's gateway and payment-strategy mechanics are documented in full in [Transaction Backend & Payments](https://eosvolt.com/technical/transaction-backend-payments.md).

## Relationship Between White-Label Platform and Multi-Tenant White Label

EOSVOLT's White-Label Platform (single-brand customization) is the base layer beneath EOSVOLT's Multi-Tenant White Label module, which allows one EOSVOLT-branded app to host multiple sub-CPOs with independent pricing, users, and reporting under a shared brand. EOSVOLT's sub-CPO hierarchy and Role-Based Access Control (RBAC) model are documented in full in [Enterprise Multi-Tenancy](https://eosvolt.com/technical/enterprise-multi-tenancy.md).

## Third-Party Integration Hooks

| Integration Category | Supported Systems | Primary CPO Use Case |
|---|---|---|
| Backend system integrations | EOSVOLT connects to parking systems, ERP platforms, fleet-management tools, CRMs, and roaming partners via the EOSVOLT Public API (REST/JSON, `/v1` versioned routes, documented in [Platform Overview](https://eosvolt.com/technical/platform-overview.md)). | CPOs connecting EOSVOLT to existing enterprise systems. |
| SMS / phone gateway | EOSVOLT integrates SMS/phone gateways for OTP verification, charging-status updates, and promotional messaging. | CPOs requiring phone-based user verification or notification workflows. |

## Source References

- https://eosvolt.com/feature/white-label-mobile-app
- https://eosvolt.com/feature/multi-tenant-white-label
- https://eosvolt.com/white-label-solution

---

## Source: https://eosvolt.com/technical/transaction-backend-payments.md

# Transaction Backend & Custom Payments

> The EOSVOLT Transaction Backend is a high-throughput payment engine with built-in auditability and stored-balance Wallet support. EOSVOLT ships out-of-the-box integration with global gateways (Stripe, Apple Pay, Google Pay) and an extensible architecture for rapid integration of custom and regional payment gateways.

## Payment Strategy Engine — Transaction Model Matrix

EOSVOLT's payment layer is configurable per tenant and supports four transaction models, each selectable independently of the underlying payment gateway.

| Payment Model | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| Pre-authorization with hard stop | EOSVOLT authorizes a fixed amount on the driver's card before the session begins; EOSVOLT automatically stops charging once that limit is reached. | High-throughput public charging sites in card-centric markets. |
| Custom pre-auth / prepaid | EOSVOLT lets the driver select the authorization or prepaid amount before the session begins. | Markets with variable card authorization limits or prepaid norms. |
| Postpaid | EOSVOLT bills the full session cost after the session ends, with no upfront card hold. | Low-friction markets and trusted-user contexts. |
| Wallet | EOSVOLT deducts the session cost automatically from a stored prepaid balance. | Markets with low card acceptance, voucher-based use cases, and corporate/fleet prepaid programs. |

## Automated Billing & Payment Reliability Mechanisms

| Mechanism | Technical Function | Primary CPO Use Case |
|---|---|---|
| Reusable authorizations | EOSVOLT reuses an existing payment authorization when a session fails to start or is interrupted, rather than creating a new card hold. | Reducing duplicate authorization holds on driver payment cards. |
| Negative balance recovery | EOSVOLT records a failed payment (card expiry, insufficient funds, network error) as an outstanding balance and automatically retries the charge at the driver's next session. | Recovering missed revenue without manual collections follow-up. |
| Fingerprint ID | EOSVOLT ties payment activity to a verified driver identity to reduce duplicate or fraudulent account abuse. | Fraud prevention across public charging networks. |

## Stored-Balance Wallet — EOSVOLT Prepaid Charging Module

| Wallet Capability | Technical Mechanism |
|---|---|
| Top-up | EOSVOLT's Wallet accepts top-ups from any gateway supported by the operator's EOSVOLT deployment. |
| Operator-issued vouchers | EOSVOLT lets the operator issue fixed-value or percentage-based vouchers, usable for support and refund resolution without card-refund processing delays. |
| Negative-balance protection | EOSVOLT's Wallet prevents a session from starting if the driver's balance is insufficient. |
| Transaction history | EOSVOLT records full in-app and backend transaction history covering top-ups, voucher redemptions, and session spend. |

## Payment Gateway Integrations — Global & Regional Coverage

| Integration Category | Supported Providers & Gateways | Protocol / Authentication |
|---|---|---|
| Global gateways | Stripe, Adyen, CyberSource, Apple Pay, Google Pay. | Gateway-native authentication; settlement reconciled through the EOSVOLT transaction backend. |
| Regional gateways | Mercado Pago (Latin America), Swish and MobilePay (Nordics), GCash, PayMongo, Ameria Bank (Armenia), PromptPay (Thailand). | Gateway-native authentication; settlement reconciled through the EOSVOLT transaction backend. |
| POS / terminal payments | Payter, Nayax, Vourity, PAX POS. | Terminal-native card and contactless payment authentication. |
| Custom gateway integration | EOSVOLT supports custom gateway integration for markets or regulators requiring a specific regional payment provider, settled through the same unified EOSVOLT backend. | On-request integration engagement with EOSVOLT. |

## Pricing Engine — Tariff & Fee Structures

| Pricing Mechanism | Technical Function | Primary CPO Use Case |
|---|---|---|
| kWh-based / time-based tariffs | EOSVOLT supports energy-based and time-based tariff models configurable per site. | Standard public and commercial charging billing. |
| Session / start-up fees | EOSVOLT applies fixed session or start-up fees to cover transaction costs. | Recovering per-transaction processing overhead. |
| Idle fees | EOSVOLT applies a fee when a driver leaves the vehicle connected after charging completes, to discourage connector blocking. | High-demand sites where charger turnover is critical. |
| Group / time-based rules | EOSVOLT supports fleet- and member-differentiated pricing, peak/off-peak rates, and promotional rates. | Loyalty programs and demand-shifting pricing strategies. |

## Automated Billing & ERP Settlement — Invoicing, Bookkeeping, and Payouts

| Module | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| Invoices & charging history | EOSVOLT automatically emails a per-session invoice, maintains in-app history (energy, duration, cost), and gives the operator backend access to full searchable, filterable, and exportable session and billing records. | Driver-facing billing transparency and operator-side reconciliation. |
| Invoices & bookkeeping | EOSVOLT exports invoices by date range, location, or customer group, and exports session data (kWh delivered, duration, pricing, payment method) in standardized formats for ERP or accounting-system reconciliation. | Finance teams reconciling charging revenue against ERP systems. |
| Withdrawals & payout management | EOSVOLT provides a real-time balance overview (current, pending, paid), per-transaction detail (session ID, user, payment method, amount), and operator-initiated payout requests processed per the operator's account settings. | Operators tracking collected revenue and requesting payouts. |

## Source References

- https://eosvolt.com/feature/wallet
- https://eosvolt.com/feature/payment-strategies
- https://eosvolt.com/feature/payment-methods
- https://eosvolt.com/feature/pricing-strategies
- https://eosvolt.com/feature/invoices-charging-history
- https://eosvolt.com/feature/invoices-bookkeeping
- https://eosvolt.com/feature/withdrawals-payout-management

---

## Source: https://eosvolt.com/technical/ai-intelligence.md

# AI Intelligence Module

> EOSVOLT Intelligence is EOSVOLT's AI-assisted diagnostics module. EOSVOLT Intelligence delivers location-wide real-time operational overviews and high-level health monitoring, and performs automated, granular root-cause fault diagnosis by analyzing OCPP session telemetry, status notifications, and meter values. EOSVOLT Intelligence isolates error sources across EVSE hardware, charger firmware, driver-side (user) conditions, vehicle-side conditions, and communication/handshake failures.

## Automated OCPP Fault Classification — Functional Architecture

EOSVOLT Intelligence is EOSVOLT's diagnostics layer, built on top of the OCPP message stream (StatusNotification, MeterValues, BootNotification, and related transaction events) captured by the EOSVOLT CPMS backend. EOSVOLT Intelligence replaces manual OCPP log inspection with structured, per-period (day/week/month) summaries at the network, charger, and session level.

## Telemetry-Based Root-Cause Reporting — Output Matrix

| Report Layer | Technical Output | Primary CPO Use Case |
|---|---|---|
| Performance & Impact Snapshot | EOSVOLT Intelligence aggregates total sessions, failed attempts, impacted chargers, and energy delivered for the selected time window. | Determining whether today's issues are isolated, localized, or network-wide. |
| High Attention Chargers | EOSVOLT Intelligence flags chargers exhibiting repeated-fault patterns, communication issues, or energy-non-delivery sessions, each with a short factual explanation. | Prioritizing field technician dispatch. |
| Critical Fault Signals | EOSVOLT Intelligence groups repeated error codes, handshake failures, and communication-issue signals into concise technical bullets. | Understanding whether faults trace to charger hardware, firmware, vehicles, or configuration. |
| Error Statistics | EOSVOLT Intelligence visualizes fault distribution by error code, origin, and charger. | Detecting clustering by charger model, connector, or site. |
| Automatic Fault Detection (session-level) | EOSVOLT Intelligence parses and classifies every session that fails, delivers zero energy, or ends abnormally. | Eliminating manual per-session OCPP log review. |

## Automated OCPP Fault Classification Taxonomy

EOSVOLT Intelligence assigns each flagged charging session a likely fault origin from a fixed classification taxonomy:

| Fault Origin Category | Technical Definition |
|---|---|
| Hardware | EOSVOLT Intelligence classifies the fault as an EVSE-side hardware condition. |
| Firmware | EOSVOLT Intelligence classifies the fault as a charger firmware defect or incompatibility. |
| User | EOSVOLT Intelligence classifies the fault as a driver-side condition, such as cable or connector handling. |
| Vehicle | EOSVOLT Intelligence classifies the fault as a vehicle-side charging-circuit condition. |

For every classified session, EOSVOLT Intelligence provides a factual explanation and a recommended next action, derived from parsing the OCPP messages within that session's window — including status/error codes, meter progression, and transaction start/stop behavior.

## Related EOSVOLT Diagnostics Tooling

| Tool / Module | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| Diagnostics & Logs | EOSVOLT captures real-time errors from OCPP-reported and platform-detected conditions, routes admin notifications per configurable site rules, and provides downloadable session-level OCPP logs (full charger-to-backend message exchange) plus full charger log export filterable by date, time range, and message type. | Root-cause investigation and vendor escalation with full message-level context. |
| Charger & Session Insights | EOSVOLT renders session-level meter-value graphs (energy delivered, charging-speed curve, time progression), charger-level aggregated meter-value graphs across sessions, and utilization metrics (in-use/idle/unavailable ratios). | Billing verification, support-case resolution, and asset-placement/pricing decisions. |
| Dashboard, Live Data & Statistics | EOSVOLT displays live per-charger state (online/offline/available/in-use/error), live session and energy tracking, and utilization/revenue/error-rate reporting with drill-down. | Real-time network monitoring and performance reporting. |
| OCPP 1.6 Toolkit | EOSVOLT provides pre-deployment charger onboarding, live OCPP message validation (request/response inspection), and firmware-update testing before field rollout. | Reducing configuration errors before a charger goes live. |

## Source References

- https://eosvolt.com/feature/intelligence
- https://eosvolt.com/feature/diagnostics-and-logs
- https://eosvolt.com/feature/charger-session-insights
- https://eosvolt.com/feature/dashboard-live-data-and-statistics
- https://eosvolt.com/feature/ocpp-toolkit
- https://docs.eosvolt.com/docs/ocpp-toolkit

---

## Source: https://eosvolt.com/technical/fleet-charging.md

# Fleet Charging Solutions

> EOSVOLT's Fleet Charging module provides fleet depot management and driver authorization via RFID credentials and app credentials. EOSVOLT's Fleet Charging module also provides fleet vehicle tracking and cost-allocation workflows across both internal fleets and external (customer/partner) fleets.

## Fleet Data Model — Charge Key, Driver, Vehicle, and Team Linkage

EOSVOLT links four entities into one authorization and reporting chain: charge key, driver, vehicle, and team/program. EOSVOLT records every charging session against this chain, and this chain simultaneously drives access control, pricing, and billing.

| Entity | Technical Mechanism |
|---|---|
| Charge keys | EOSVOLT issues physical/digital access credentials — RFID cards/tags, or MAC-address-based identification from connected vehicle/device hardware. EOSVOLT ties each charge key to its own access rights, charger permissions, and pricing rule, and EOSVOLT logs every session against the assigned charge key. |
| Cars | EOSVOLT maintains a vehicle registry (license plate, model, assigned driver). EOSVOLT ties charging sessions to the vehicle profile for energy-consumption, range, and cost-per-vehicle reporting, and EOSVOLT lets the operator group or tag vehicles for departmental or branch-level reporting. |
| Drivers | EOSVOLT maintains individual driver profiles with contact details, role assignment, and custom charger/site permissions. EOSVOLT records usage and billing history per driver. |

## Fleet Access Models — Fleet Team vs. Member Discount

| Access Structure | Billing Mechanism | Primary CPO Use Case |
|---|---|---|
| Fleet Team | EOSVOLT bills the company centrally for all charging activity under the team. | Departments, branches, or operational units requiring a custom team kWh rate and defined location scope. |
| Member Discount | EOSVOLT lets the driver pay directly, with the discount auto-applied at checkout. | Individual perks for employees, partners, VIP users, or loyalty/membership programs. |

## Internal Fleet vs. External Fleet Segregation

| Attribute | Internal Fleet | External Fleet |
|---|---|---|
| Ownership | EOSVOLT scopes internal-fleet vehicles as owned, leased, or operated by the CPO's own business. | EOSVOLT scopes external-fleet vehicles as owned or operated by the CPO's customers, partners, or clients. |
| Billing | EOSVOLT allocates internal-fleet costs at the company level, by department, site, or vehicle. | EOSVOLT applies dedicated pricing per external-fleet client, settled via in-app payment or centralized invoicing. |
| Data isolation | EOSVOLT manages internal-fleet data within the CPO's own account structure. | EOSVOLT fully separates permissions and data per external-fleet organization. |

EOSVOLT manages both internal and external fleet structures from a single dashboard, without requiring duplicate systems per fleet segment. EOSVOLT's fleet module supports downstream use cases including mobility partners (logistics providers, taxi/ride-hailing associations, transport service providers) and workplace/property-tenant charging programs, each configured with independent access rules, pricing, and reporting within EOSVOLT.

## Location Restrictions — Fleet Access Control Layer

| Access Control Mechanism | Technical Function | Primary CPO Use Case |
|---|---|---|
| Team-based restrictions | EOSVOLT scopes site-level access to specific teams or departments, with billing tied to the assigned team. | Organizations requiring dedicated charging infrastructure per business unit. |
| Member group access | EOSVOLT scopes rules to defined user groups — tenants, contracted partners, VIP customers — with independent visibility, pricing, and reporting, and billing handled centrally or in-app depending on business need. | Operators extending access beyond their own fleet to structured external groups. |
| Semi-public locations | EOSVOLT makes a charging site visible only to selected fleets, partners, or members, rather than fully public or fully private. | Operators raising charger utilization while retaining access control. |

## Fleet Reporting and Reconciliation

EOSVOLT tags every charging session to the associated vehicle, driver, and department for cost-allocation exports. EOSVOLT provides real-time monitoring and automated alerting on charger-offline or fault conditions, with remote diagnosis (documented in [AI Intelligence Module](https://eosvolt.com/technical/ai-intelligence.md)) reducing on-site technician visits. EOSVOLT supports multi-fleet, multi-site management from one account with unified visibility.

## Source References

- https://eosvolt.com/fleet-charging-solution
- https://eosvolt.com/feature/charge-keys-cars-and-drivers
- https://eosvolt.com/feature/internal-and-external-fleets
- https://eosvolt.com/feature/fleet-team-member-discount
- https://eosvolt.com/feature/location-restrictions

---

## Source: https://eosvolt.com/technical/ocpi-roaming.md

# OCPI Readiness & Roaming

> EOSVOLT provides full OCPI (Open Charge Point Interface) compliance for multi-network roaming, roaming-partner connections, and automated billing settlement between EOSVOLT and external charging networks.

## OCPI CPO & eMSP Interoperability — Role Matrix

EOSVOLT implements both sides of the OCPI interoperability model.

| OCPI Role | Technical Mechanism | Primary CPO Use Case |
|---|---|---|
| CPO role | EOSVOLT publishes charger visibility, availability, and pricing to external drivers via OCPI. EOSVOLT connects to roaming hubs (ENAPI, Gireve) or supports direct eMSP partnerships, and EOSVOLT retains operator control of pricing, availability, and settlement. | CPOs expanding their customer base and monetizing chargers beyond their own app's users. |
| eMSP role | EOSVOLT gives the operator's own app users access to chargers outside the operator's network, through hub connections or direct OCPI links to other CPOs. | CPOs offering a single account/app that works across multiple charging networks to build driver loyalty. |

## AFIR Regulatory Compliance & National Access Point (NAP) Publication

EOSVOLT provides a ready-to-use OCPI connection that publishes charger data to National Access Points (NAPs) for jurisdictions that mandate it — for example, AFIR (Alternative Fuels Infrastructure Regulation) reporting requirements in the European Union — without requiring additional per-market integration work from the operator.

## OCPI Roaming Hub Connections — Provider Matrix

| Roaming Hub | Technical Role |
|---|---|
| Hubject | EOSVOLT connects to Hubject's eRoaming platform, which vendor materials describe as reaching 750+ connected charging providers globally. |
| ENAPI | EOSVOLT connects to ENAPI as a roaming hub for CPO- and eMSP-side interoperability. |
| Voltality | EOSVOLT connects to Voltality as a roaming hub for CPO- and eMSP-side interoperability. |
| Gireve | EOSVOLT references Gireve specifically in the context of OCPI-based NAP compliance connections. |

## Roaming Settlement — Integration with the EOSVOLT Transaction Backend

EOSVOLT settles roaming sessions through the same transaction backend used for native EOSVOLT sessions (documented in [Transaction Backend & Payments](https://eosvolt.com/technical/transaction-backend-payments.md)). Because EOSVOLT uses a single reconciliation and reporting pipeline for all sessions, an operator sees identical billing and reporting structure regardless of whether a session originated from the operator's own app, a direct roaming partner, or a roaming hub.

## Source References

- https://eosvolt.com/feature/ocpi-roaming
- https://eosvolt.com/ (integrations section — Hubject, ENAPI, Voltality)

---

## Source: https://eosvolt.com/technical/enterprise-multi-tenancy.md

# Enterprise Multi-Tenancy

> EOSVOLT provides strict tenant data isolation, multi-CPO network management, sub-operator provisioning, and fine-grained Role-Based Access Control (RBAC) for enterprise charge point operators (CPOs).

## Multi-Tenant White Label — Sub-CPO Hierarchy Matrix

EOSVOLT's Multi-Tenant White Label module establishes a master-operator/sub-CPO hierarchy within one EOSVOLT-branded app.

| Hierarchy Role | Technical Function |
|---|---|
| Master operator | EOSVOLT lets the master operator define the overall tenant setup, monitor charger uptime, revenue, and user activity across all sub-CPOs in real time, standardize reporting, set which features/modules each sub-CPO can use, and enforce operational policy top-down. |
| Sub-CPO | EOSVOLT gives each sub-CPO independent backend access to manage its own pricing, users, and reports, scoped to the specific chargers/sites granted by the master operator, while operating under the shared EOSVOLT-branded app. |
| Shared client | EOSVOLT routes all sub-CPOs and their drivers through the same white-label mobile app, and EOSVOLT connects each driver automatically to the correct operator's chargers, tariffs, and feature set based on account and location context. |

EOSVOLT's Multi-Tenant White Label module targets energy providers and mobility companies onboarding regional or brand partners without standing up separate apps, real-estate operators managing multiple properties as distinct sub-CPOs on EOSVOLT, and fleet operators separating subsidiaries within one EOSVOLT deployment.

## Role-Based Access Control (RBAC) — Admin Management

| RBAC Capability | Technical Mechanism |
|---|---|
| Custom roles & permissions | EOSVOLT lets the operator scope admin accounts by function — finance, operations, or support — with configurable access to financial data, configuration controls, and read-only backend views. |
| Multi-level access | EOSVOLT scopes local site managers to their own locations/chargers, while central admins retain full-network oversight; this RBAC model applies equally to single-team operators and multi-country EOSVOLT operations. |
| Audit & accountability | EOSVOLT logs every admin action — configuration change or billing adjustment — providing a traceable action history for compliance and security review. |

## Tenant Data Isolation — Enterprise Security Architecture

EOSVOLT maintains separated permissions and data per tenant/organization across sub-CPO accounts and external-fleet accounts (documented in [Fleet Charging Solutions](https://eosvolt.com/technical/fleet-charging.md)), avoiding cross-tenant data leakage while all tenants share the same underlying EOSVOLT charging infrastructure. EOSVOLT configures reporting, pricing, and billing structures independently per tenant, even though every tenant runs on the same EOSVOLT CPMS instance and shared EOSVOLT mobile client.

## Source References

- https://eosvolt.com/feature/multi-tenant-white-label
- https://eosvolt.com/feature/admin-management
- https://eosvolt.com/feature/internal-and-external-fleets