End to end Process.

Overview

The system connects three main parties:

• Driver – the person charging the vehicle

• Payment Terminal (via PTP) – where payment happens

• eMabler backend (CPO + CSMS) – the system that manages the charger

Start of a Charging Session

1. Driver arrives at the charger
   The driver parks, connects the charging cable, and goes to the payment terminal.

2. Selects the connector
   The terminal shows available connectors or chargers. The driver selects one.

3. Displays price and terms
   The terminal asks eMabler (through the PTP system) for current prices.
   eMabler sends tariff information – including the price per kWh and maximum amount allowed.
   The terminal displays this clearly for the driver.

4. Driver confirms payment
   The driver taps a card or phone to pay. The PTP system authorizes the amount through the payment service provider (PSP).

5. Session begins
   Once payment is approved, the terminal tells eMabler to start the session.
   eMabler activates the charger, and charging begins.
   The terminal shows Session started with a optional QR Code to scan

During Charging

• The terminal can show progress such as charging time, energy used, or estimated cost. - Depends on PTP implementation.

Stopping a Charging Session

1. Driver stops charging
   The driver presses Stop on the terminal or unplugs the cable.
   Alternatively, charging stops automatically when the paid limit or vehicle battery capacity is reached.

2. Payment and settlement
   When charging ends, eMabler sends the final details — duration, energy delivered, and total cost — back to the PTP system.
   The payment is captured automatically by the PTP (or PSP).

3. Receipt and confirmation
   The terminal displays QR code and final cost for the driver.

sequenceDiagram autonumber actor Driver participant PTP participant eMabler participant Charger %% --- Price Discovery --- note over Driver,PTP: Connector selection & price display Driver->>PTP: Select connector on payment terminal PTP->>eMabler: GET /locations and /tariffs (OCPI) eMabler-->>PTP: Return Location + Tariff (max_price, alt_text) PTP-->>Driver: Display price and terms on terminal %% --- Payment Authorization --- note over PTP: Pre-authorization for max_price Driver->>PTP: Confirm payment PTP->>PTP: Process pre-authorization (via PSP) PTP-->>Driver: Payment authorized %% --- Session Start --- note over PTP,eMabler: OCPI Direct Payment session creation PTP->>eMabler: POST commands/StartSession (evse_uid, connector_id, authorization_reference) eMabler->>Charger: RemoteStart (OCPP) Charger-->>eMabler: StartTransaction confirmation eMabler-->>PTP: StartSession result (success + authorization_reference) PTP-->>Driver: Charging started message on terminal %% --- During Charging --- note over Charger,PTP: Optional live updates Charger->>eMabler: MeterValues (energy/time updates) eMabler->>PTP: PATCH /sessions (energy, duration, cost) PTP-->>Driver: Update display “Charging in progress” %% --- Stop Conditions --- note over eMabler,Charger: Session may end in multiple ways alt Driver stops via terminal Driver->>PTP: Stop request PTP->>eMabler: commands/StopSession else Max price reached eMabler->>Charger: RemoteStop (OCPP) else Vehicle or charger stops automatically Charger->>eMabler: StopTransaction end %% --- Session Finalization & Settlement --- note over eMabler,PTP: Post-session data and settlement eMabler->>PTP: PATCH /sessions (final values) eMabler->>PTP: POST /cdrs (energy, cost, authorization_reference) PTP->>PTP: Capture payment (financial advice) PTP-->>eMabler: Payment confirmation (OCPI payments) eMabler->>eMabler: Generate invoice (Send CDR with EFT data to customer) PTP-->>Driver: Show receipt link (BaseURL + authorization_reference)