Technical Services for eMSP Platforms
We specialize in building and integrating custom eMobility Service Provider (eMSP) platforms for large-scale EV charging networks. Our engineering teams focus on domain-driven microservices, compliance with industry protocols, and flexible architectures to ensure stability, interoperability, and security.
What Is an eMSP Platform?
An eMSP (e-Mobility Service Provider) platform is the software that enables EV drivers to find, start, and pay for charging sessions across multiple networks using a single account. Unlike a CPO (Charge Point Operator) who owns and operates physical chargers, an eMSP focuses on the driver experience — mobile apps, payment processing, and multi-network access via roaming protocols like OCPI and OICP.
Codibly builds or extends eMSP platforms with protocol compliance, microservices architectures, and operational resilience:
Backend & Microservices Development
• Implement domain-driven microservices for charging session management, billing, and roaming
• Containerization with Docker or Kubernetes for scalable, zero-downtime deployments
• Standardized data schemas to enable consistent communication across all services
Protocol & API Integrations
• Compliance with OCPP (1.6J, 2.0) and OCPI for interoperability
• REST and WebSocket endpoints for real-time charger status updates
• Custom adapters to unify multiple vendor APIs under a single eMSP interface
Security & Data Protection
• TLS-based encryption for all external and internal service calls
• Role-based access control (RBAC) and audit trails
• Compliance with data privacy standards like GDPR for sensitive user information
Performance & Scalability
• Load balancing strategies to handle spikes in charging requests
• Asynchronous processing to manage concurrent transactions
• Comprehensive monitoring and logging for real-time performance tuning
SOFTWARE DEVELOPMENT
eMSP Software Development: Our Engineering Approach
Custom eMSP software development is about more than shipping a driver app — it is about building the backend that makes roaming, billing, session management, and multi-CPO integration work at scale. Codibly’s eMSP software development process covers domain modeling, API-first architecture design, microservices implementation, and OCPI/OICP certification. Here is how we structure a typical eMSP software development engagement:
Discovery & Domain Modeling
• Map target markets, tariffs, and CPO roaming agreements into a domain model
• Define session lifecycle, billing triggers, and driver identity boundaries
• Identify which capabilities to build, buy, or accelerate with existing modules
API-First Architecture Design
• Microservices decomposition by bounded context: sessions, tariffs, wallet, identity, roaming
• REST and GraphQL API contracts defined before implementation
• Event-driven integration patterns for CDR flow and real-time charger status
Build & Protocol Integration
• Backend services in Java, Kotlin, or Node.js depending on team fit
• OCPI 2.2.1/2.3 roaming connectors, OICP adapters, and Hubject integration
• Payment service provider integration (Stripe, Adyen, direct debit) with PCI scope isolation
QA, Certification & Launch Support
• Protocol conformance testing against OCPI test harnesses
• Load testing for charging session concurrency and PSP transaction throughput
• Production cutover, runbook handover, and post-launch observability setup
PLATFORM ARCHITECTURE
eMSP Platform Architecture: Layers That Scale From Pilot to Production
A production-grade eMSP platform is built in four layers that separate driver-facing experience from core business services, roaming integrations, and observability. This separation is what allows a platform to grow from a single-country pilot to a multi-market operation without rewriting the core. Codibly designs eMSP architectures around these four layers — each one independently deployable, observable, and replaceable as your roaming footprint expands:
Driver Experience Layer
• Mobile apps (iOS, Android) and responsive web portals for charger discovery
• RFID, QR, Autocharge, and Plug & Charge (ISO 15118) authentication flows
• Push notifications, trip history, and tariff transparency for end users
Core Business Services
• Session management, tariff engine, wallet, invoicing, and KYC services
• Customer identity and access control with role-based permissions
• Subscription and fleet contract modelling for B2B eMSP offerings
Roaming & Integration Layer
• OCPI 2.2.1/2.3 and OICP connectors for cross-network session data
• Hubject and Gireve roaming hub integration
• Payment service provider and ERP integration with idempotent event handling
Data, Observability & Security
• Event streaming (Kafka/Kinesis) for CDRs, charger state, and audit trails
• Analytics warehouse with usage, revenue, and churn dashboards
• SIEM integration, GDPR-compliant identity storage, and TLS everywhere
APIs & INTEGRATION
eMSP APIs: The Integration Surface That Makes Roaming Work
Every eMSP platform is defined by the quality of its API surface. Driver apps consume it, CPOs integrate against it through OCPI, and back-office tooling depends on it for billing, reporting, and operations. Codibly designs eMSP APIs to be versioned, documented, and independently scalable — with clear contracts between each subsystem. The API surface is built around four distinct groups, each serving a different consumer and operating at a different reliability tier:
Driver-Facing APIs
• Authentication, charger search, reservation, session start/stop, and payment
• Tariff and availability lookups optimized for sub-second mobile response
• Session history and invoice retrieval for driver self-service
Roaming APIs (OCPI / OICP)
• OCPI 2.2.1 and 2.3 endpoint implementations: Locations, Sessions, CDRs, Tariffs, Tokens
• Versioned OICP connectors for Hubject-based roaming
• Real-time charger status push and command-response flows (start, stop, reserve)
Back-Office APIs
• Admin consoles for configuration, user management, and dispute resolution
• Billing, invoicing, and revenue reporting endpoints for finance teams
• Configuration APIs for tariffs, tenants, and roaming partner onboarding
Webhooks & Event Streams
• Transaction events (session started, session ended, CDR created)
• Charger state changes and fault alerts
• Payment confirmations and refund lifecycle events
TAILORED FEATURES
What Features Does an eMSP Platform Need?
Account Management & Billing
• Real-time balance tracking for EV drivers, including subscription tiers
• Automated invoice generation based on tariff rules
• Integration with payment gateways (credit card, PayPal, direct debit)
Charger Discovery & Reservation
• RESTful or GraphQL APIs for location-based searches
• Real-time occupancy status via WebSockets
• Reservation logic with adjustable hold times and cancellation policies
Roaming & Interoperability
• OCPI-based interfaces for cross-network session data
• Automatic roaming agreements with external eMSPs or CPOs
• Unified APIs for session start, stop, and remote commands
Analytics & Reporting
• Customizable data dashboards for usage trends and revenue analysis
• Automated KPI reporting (peak hours, charger utilization, dwell time)
• Predictive intelligence modules for churn detection and capacity planning
Customer Support Tools
• Admin consoles for real-time session oversight and manual error resolution
• Ticketing system integration for issue tracking
• Proactive notifications for firmware updates or scheduled maintenance
Advanced Security Features
• Encrypted user tokens for secure driver authentication
• Role-based privileges for operators, CS agents, and super admins
• Integration with SIEM systems for real-time threat monitoring
ACCELERATOR BENEFITS
How Does Codibly’s eMSP Engine Accelerate Development?
We maintain accelerators designed for key eMSP functionalities—reducing development overhead while maintaining code quality. These modules undergo continuous updates to stay current with evolving eMobility standards.
Quick Deployment
• Up to 80% reduction in dev time for features like session management
• Pre-tested code blocks for stability in high-load scenarios
• Comprehensive unit and integration tests included
Cost Efficiency
• Up to 70% cost reduction by reusing essential infrastructure logic
• Predictable budgeting due to standardized modules
• No ongoing license fees—one-time accelerator usage for unlimited expansions
Standards Alignment
• Compliance with OCPP, OCPI, and local market-specific rules
• Extensively vetted for performance under real-world eMSP demands
• Regularly updated to align with new protocols or version increments
Customizable Extensions
• Adapt or extend modules to fit unique tariff policies, hardware variants, or brand guidelines
• Flexible architecture that allows for specialized logic without rewriting the entire codebase
• Rapid integration of value-added features (e.g., loyalty programs, advanced load management)
Codibly eMSP Engine
Own the Experience. Skip the Infrastructure
Your drivers care about the experience, not the backend “plumbing.” The Codibly eMSP Engine provides the robust, secure core you need to handle complex roaming and data logic. Your team builds the unique UX and brand features on top. Get the total freedom of a custom build without the timeline risk.
What our clients say
“Codibly was more than just a software development company; they were a capable partner who understands the EV industry and helped us push our vision forward.”
“Working closely with Codibly has been instrumental in the successful development of the test tool for OpenADR 3.0. Their expertise and commitment to quality have ensured reliability and effectiveness for the energy industry, and we look forward to continuing our collaborative efforts to advance OpenADR technology.”
Frequently Asked Questions
An eMSP (e-Mobility Service Provider) is a company that provides EV drivers with access to charging networks. eMSPs offer mobile apps, RFID cards, or other means for drivers to find, start, and pay for charging sessions across multiple charging networks, even those operated by different CPOs (Charge Point Operators).
A CPO (Charge Point Operator) owns and operates physical charging stations, managing hardware, maintenance, and grid connections. An eMSP (e-Mobility Service Provider) focuses on the driver experience — providing apps, payment processing, and access to multiple charging networks. Some companies operate as both CPO and eMSP.
eMSPs connect to CPO networks through roaming protocols, primarily OCPI (Open Charge Point Interface) and OICP. These protocols enable real-time exchange of location data, tariffs, session information, and CDRs (Charge Detail Records). Roaming hubs like Hubject (OICP) and Gireve (OCPI) simplify multi-network connectivity.
CASE STUDIES
See the success stories of our clients
Meet our Expert
As the eMobility Practice Lead at Codibly, I am responsible for driving the strategic development and growth of our electromobility division. With over 15 years of experience in the IT sector, I specialize in building strong client relationships and aligning technology solutions with business objectives. Having spent the last decade focused on the automotive and electromobility industries, I bring a wealth of expertise in delivering tailored solutions for both the public and private sectors. Prior to Codibly, I led the IT teams at Volkswagen Group Poland, where I successfully managed a range of large-scale projects and IT portfolios. Throughout my career, I have consistently focused on delivering both off-the-shelf and custom solutions that address complex business challenges.
CONTACT US
Let’s Talk EV
Find out how Codibly’s consultancy and development services can accelerate your EV business. Book a call and let’s shape the future of eMobility together.
Recommended Articles
