POS Integrations

The POS Integration sections show how to integrate a POS Terminal provider.

Topics in this document:

POS Provider using Tridens OCPI node as a gateway to OCPI CPO

POS provider communicates with OCPI Tridens node, which forwards the request to any OCPI CPO charger for the session control.

POS provider

POS provider eMSP

Configuration and Integration Guidelines

Roaming Integration Configuration Steps

  1. Configure Business/Site environment of POS provider integrations (configured by Tridens).

    a. Configure Operator for a specific POS integration provider.

  2. Conifgure environment of POS provider (configured by POS provider).

    a. Configure Operator’s Roaming Profile of OCPI, representing POS provider settings.

    b. Configure Operator’s Roaming Platform of OCPI for CPO client.

    c. Generate platform’s registration token to use for credentials exchange.

  3. Configure environment of EVC client (configured by CPO client).

    a. Configure Roaming Profile of OCPI, representing the settings of CPO.

    b. Configure Roaming Platform of OCPI with reference to POS integration provider.

    c. Use POS provider’s registration token (of Roaming Platform).

    d. Initialize credentials exchange.

Session Initiation from POS Provider to Tridens EV Charge

Operations by which the POS Provider can request EV Charge to start and stop the charging session on the charging infrastructure.

Resulting and intermediate charging session actions are forwarded back to the POS Provider by API, as configured and specified in section Tridens EV Charge Reporting Session Progress To POS Provider.

Request Identifiers Disambiguation​
Roaming Platform IdentifierPOS provider’s roaming platform identifier in Tridens EV Charge.

Configured by Tridens.
Roaming Partner IdentifierCPO provider’s roaming identifier in scope of Roaming Platform.

Configured by Tridens.
Roaming Partner’s Connector IdentifierCPO provider’s charging infrastructure’s composite identifier, consisting of OCPI’s {location-id}.{evse-id}.{connector-id}.​ Composite identifier is generated by OCPI CPO platform you are integrating with. ​

In scope of CPO’s in Tridens EV Charge, it reflects {area-id}.{charger-id}.{connector-id}, so it can be determined in that way as well.​

POS provider can determine the Area, Charger, Connector structure, by requesting the API and using id/code attributes to construct the identifier. To obtain this, follow API guidelines of Read Charging Infrastructure of Roaming CPO.

Table: Request identifiers

Read Charging Infrastructure of Roaming CPO

API request:

Below is the API response containing paginated list of Areas with nested Charging Stations, Chargers and Connectors

1. Request Charging Session to Start

API Reference:

For authentication and authorization details, refer to the Tridens EV Charge API Reference.

2. Request Charging Session to Stop

API Reference:

For authentication and authorization details, refer to the Tridens EV Charge API Reference.

Tridens EV Charge Reporting Session Progress To POS Provider

Configure Notification Rules for actions of charging session start, meter value reports and session stop. Provide a filter over Roaming Platform and assign publishing by REST call out. POS provider needs to provide API endpoints to which the reports will be published.

Notification Rule Configuration in System Operations of POS Provider Operator:

  1. Add Notification Rule and determine name.

  2. Assign Publisher of URL action.

    a. Assign headers which are attached to the URL request. Here you can specify the access token.

    b. Assign URL to which the call will be executed. Select Base type and enter URL.

  3. Select Charging Sessions scope of notification. Create a Notification Rule for scopes of:

    a. Session started

    b. Meter values reported

    c. Session ended

  4. Add filter to limit notifications for this specific Site’s Operator.

    a. Select logical operator of Equal to (==), with value of contents.session.roaming_platform.id

  5. Set notification rule as enabled.

Below is an example of how to configure notification rule: