OCPI Server Integration / Terminal Integration

Linking charging stations

A terminal can be linked to a charging station through the OCPI connection during the creation of a terminal object in the Payments module. Afterwards, this link can be updating by updating the terminal object in question. The terminal can be linked to multiple EVSE’s or Locations. This will make all EVSE’s that are directly linked to the terminal and/or all EVSE’s that are linked to a location that is directly linked to a terminal available.

• An EVSE will only me shown on the terminal if its status is set to “AVAILABLE”.
• The value of the “reference” parameter should be set to the terminal TID.
• Make sure that the “las_updated” parameter is correctly set in order to include any changes in the next OCPI-sync.

Example:

{
  "address": "Westervoortsedijk 55",
  "city": "Arnhem",
  "location_ids": [
    "df37373d-1669-4127-a6ac-d86750095119",
    "a06dc823-3e5a-40c8-89cf-1b5b9e941412",
    "55719888-ed09-4cca-82cc-803bdb77bf26"
  ],
  "evse_uids": [
    "25a2c4ab-2251-325c-fab1-554aa1c55421"
  ],
  "reference": "12345678",
  "last_updated": "2026-03-23T17:16:15Z"
}

Charger name

The names as they appear on the payment terminal are defined in the locations module:

Example:

{
  "uid": "2421",
  "evse_id": "NL*CCV*100561003",
  "connectors": [
    {}
  ],
  "physical_reference": "Charger name",
  "last_updated": "2026-03-23T12:39:09Z"
}

Connectors

The connector names are generated automatically based on the following connector parameters:

• “power_type”
• “max_voltage”
• “max_amperage”
• “max_electric_power”

Example:

{
  "uid": "2421",
  "evse_id": "NL*CCV*100561003",
  "connectors": [
    {
      "id": "1",
      "power_type": "DC",
      "max_voltage": 920,
      "max_amperage": 400,
      "max_electric_power": 150000,
      "last_updated": "2026-03-23T08:12:01Z"
    }
  ]
}

Tariffs

Supported Tariff Components

The following tariff values will be displayed on our terminal when the user is initializing a new charging session:

• FLAT
• ENERGY
• TIME
• PARKING_TIME

Tariff Types

Tariff objects need to have the “AD_HOC_PAYMENT” tariff type in order to be applicable for the CCV Cloud Connect server. Additionally, the “REGULAR” tariff type is also supported.

Preferred:

{
  "type": "AD_HOC_PAYMENT"
}

Fallback:

{
  "type": "REGULAR"
}

Custom Tariff Text

A custom text may be shown to drivers instead of standard tariff element breakdowns. Alternatively, this custom text could also be used to give additional information to more complex tariffs. The “tariff_alt_text” field can be used for this.

Example 1:

{
  "tariff_alt_text": [
    {
      "language": "en",
      "text": "Happy Easter!\n15% discount on all charging sessions."
    }
  ]
}

Example 2:

{
  "country_code": "BE",
  "party_id": "ALL",
  "type": "AD_HOC_PAYMENT",
  "tariff_alt_text": [
    {
      "language": "en",
      "text": "Happy Easter!\n15% discount on all charging\nsessions.\nAutomatically applied."
    }
  ],
  "elements": [
    {
      "price_components": [
        {
          "type": "FLAT"
        },
        {
          "type": "ENERGY"
        },
        {
          "type": "TIME"
        },
        {
          "type": "PARKING_TIME"
        }
      ]
    }
  ],
  "last_updated": "2026-03-23T11:16:55Z"
}

Reservation

A specific amount is blocked on the EV-driver’s account to cover costs for a potential charging session.

This value must always include the VAT as well. This is the absolute maximum amount which can be booked. Any attempt to book a higher value after the session completes will be declined.

The reservation amount is set within the tariff through the “max_price.incl_vat” parameter.

{
  "country_code": "NL",
  "party_id": "ALL",
  "id": "12",
  "currency": "EUR",
  "max_price": {
    "excl_vat": 37.74,
    "incl_vat": 40.00
  },
  "type": "AD_HOC_PAYMENT",
  "elements": [
    {
      "price_components": []
    }
  ],
  "last_updated": "2026-03-23T11:16:55Z"
}

Keep in mind that in the demo environment, special reservation amount can be used to trigger specific testing scenarios

• Any amounts with *.01 -> *.14 decimals
• Amounts with *.50 decimals
• Amounts with *.11 will always trigger PIN entry

Invoice creation

The invoice creator is defined in the terminal object, using the “invoice_creator” parameter. The link to the invoice is configured with the “invoice_base_url” parameter. In case the “invoice_creator” is set to PTP, the “invoice_base_url” will be defaulted to the base url of the CCV invoice platform. This invoice url is shown to the user through a QR code that is available when starting a new session, stopping an ongoing session and through the invoice menu on the terminal.

{
  "terminal_id": "111ac1c1-11ab-1b1a-1baa-ac111222211a",
  "customer_reference": "CPO-Reference",
  "invoice_base_url": "https://cpo-domain.com/invoices",
  "invoice_creator": "CPO",
  "location_ids": [],
  "serial_number": "12345678",
  "last_updated": "2026-03-23T17:16:15Z"
}

The final invoice url will be the combination of the “invoice_base_url” from the terminal object and the “authorization_reference” from the session object.

Example:

• invoice_base_url: http://demo-ocpi.test.aws.ccvlabinfra.net/receipts/
• authorization_reference: 635e1234-ca12-4123-ca12-635e12345678
• full invoice url: http://demo-ocpi.test.aws.ccvlabinfra.net/receipts/635e1234-ca12-4123-ca12-635e12345678

During the charging session, the invoice will not be available yet. When the “invoice_creator” is set to PTP, CCV will then show a waiting page until the final invoice is available.

Eichrecht data (Germany specific)

Eichrecht calibration data for compliance with German law can be included with the CCV receipt by using the instructions in the OCPI specification.

See signed_data in the CDR object:

{
  "encoding_method": "OCMF",
  "encoding_method_version": 1,
  "public_key": "305a301406072a8...",
  "signed_values": {
    "nature": "Start",
    "plain_data": "OCMF ...",
    "signed_data": "20950120056322AA..."
  },
  "url": null
}

Example of a CCV receipt with Eichrecht calibration data included:

Stop charging

A charging session can be stopped in multiple ways:

• From the car (unplug cable)
• From the charging station
• From the payment terminal (“Stop charging” on the home screen)

Stop charging flow:

• To stop a charging session from the payment terminal, the user must present their payment card to the terminal for authentication.
• CCV then looks for active charging sessions for this card.
• Tapping a session will send a stop session request to the CPMS.
• After this, the user can get the link to their invoice again.

Settlement

When a charging session is stopped, the CPMS sends the CDR to CCV with the information of the charging session and the actual costs. This is the trigger for CCV to settle the final cost.

CCV then books the actual costs with the acquiring bank for this terminal and releases the remaining amount from the reservation.

To inform the CPMS of the booking of the actual costs, CCV sends a “Financial Advice Confirmation” object to the CPMS (see Payments module). The information in the CDR and the financial advice confirmation can be used by the CPMS to create a proper invoice for the end-user.

Example of a financial advice confirmation:

{
  "id": "123abc1-12ab-1a1a-1abc-ab123456789a",
  "authorization_reference": "bb-100100-112341234",
  "total_costs": {
    "excl_vat": 11.40,
    "incl_vat": 12.60
  },
  "currency": "EUR",
  "eft_data": [
    "Mastercard",
    "AID: 1234",
    "Crypto: 3456",
    "Nr: **** **** **** 1234",
    "SEQ: 00",
    "Amount: EUR 12.60"
  ],
  "capture_status_code": "SUCCESS",
  "capture_status_message": "Capture successful at PSP",
  "last_updated": "2026-03-23T17:16:15Z"
}

Payment receipt flow

• Similar to “Stop charging”, the “Payment receipt” option requires authentication
• CCV then looks for active charging sessions for this card.
• Tapping a session will send a stop session request to the CPMS.
• After this, the user can get the link to their invoice again.