Technical Onboarding - what to expect

Last updated: September 29, 2025

Overview

This document outlines the comprehensive testing process for onboarding new OCPI partners to the ENAPI charging platform. The testing ensures proper integration between Charge Point Operators (CPOs), e-Mobility Service Providers (eMSPs), and our platform.

Prerequisites

Before beginning any testing procedures, ensure the following requirements are met:

  • Functioning OCPI implementation in version 2.1.1, 2.2.1, or 2.3

Common Setup Steps

1. OCPI Handshake Process

The OCPI handshake is the foundational step that must be completed successfully before any testing can proceed.

Success Criteria: Successful exchange of authorization tokens and module endpoints.

2. Simulator Platform Connection

Upon successful handshake completion, the partner is automatically connected to our testing platforms based on their role:

  • CPO Partners: Connected to our eMSP platform

  • eMSP Partners: Connected to our CPO platform

  • Partners acting as both CPO and eMSP: Connected to both eMSP and CPO platforms

3. Test Data Availability

Our platforms provide standardized test data for comprehensive testing:

Simulated CPO Data (ES/CPO):

  • Test locations with various charging configurations

  • Sample tariff structures covering different pricing models

Simulated eMSP Data (ES/MSP):

  • Test tokens for authentication and authorization testing

  • Various token types and states for edge case testing

Session Simulation:

  • Locations are connected to our session simulator

  • Capable of generating realistic session flows and CDR data

CPO Partner Testing Process

Phase 1: Data Synchronization Verification

Inbound Data Pulls

Verify our platform can successfully retrieve partner data:

  1. Location Synchronization

    • Pull all partner locations

    • Validate location data structure and completeness

    • Confirm proper mapping of charging connectors and capabilities

  2. Tariff Synchronization

    • Pull partner tariff information

    • Verify pricing structure accuracy

    • Validate tariff-to-location associations

Outbound Data Distribution

Verify partner can retrieve data from our platform:

  1. Token Distribution

    • Confirm partner can pull token information

    • Validate token authentication data

    • Test various token states and types

Phase 2: Session Flow Testing

Session Initiation and Management

  1. Session Execution

    • Use our test tokens to initiate charging sessions at partner locations

    • Monitor session state transitions

    • Verify proper session authorization flows

  2. Session Updates (Optional)

    • Monitor for real-time session status updates from partner

    • Validate update routing and processing

  3. Session Termination and Billing

    • Execute session stop commands

    • Verify CDR (Charge Detail Record) generation and receipt

    • Confirm proper CDR routing to billing systems

eMSP Partner Testing Process

Phase 1: Data Synchronization Verification

Inbound Data Pulls

Verify our platform can successfully retrieve partner data:

  1. Token Synchronization

    • Pull partner token database

    • Validate token format and authentication data

    • Test token state management

Outbound Data Distribution

Verify partner can retrieve data from our platform:

  1. Location Distribution

    • Confirm partner can pull location information

    • Validate location data completeness and accuracy

    • Test location filtering and search capabilities

  2. Tariff Distribution

    • Verify partner can access tariff information

    • Confirm pricing data accuracy

    • Test tariff update mechanisms

Phase 2: Session Flow Testing

Session Management and Routing

  1. Session Initiation

    • Partner uses their tokens to start charging sessions

    • Alternatively, have partner initiate sessions using their own interface

    • Verify session authorization and routing

  2. Session Communication

    • Confirm our session updates are correctly routed to partner

    • Test real-time session status communication

    • Validate session state synchronization

  3. Session Termination and Billing

    • Execute session termination procedures

    • Verify CDR generation and routing to partner

    • Confirm proper billing data transfer

  4. RFID Authentication

    • RFID token authentication testing procedures, requires manual intervention from ENAPI onboarding team.

Success Criteria

A partner onboarding test is considered successful when:

  • All handshake verification points pass

  • Data synchronization operates bidirectionally without errors

  • Session flows complete end-to-end with proper CDR generation

  • All routing mechanisms function correctly

  • No critical errors remain unresolved