Notify Customer Information

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.34 (Messages); Use Case N09 — Get Customer Information (Functional Block N. Diagnostics)

Overview

After the CSMS sends CustomerInformationRequest (with report = true), the Charging Station replies with one or more NotifyCustomerInformationRequest messages containing the requested customer data. Because the data may not fit into a single message, it is delivered as a sequence of chunks identified by seqNo and a tbc ("to be continued") flag.

The CSMS replies to each chunk with NotifyCustomerInformationResponse (no body).

Sequence Diagram

Charging Station  ──── NotifyCustomerInformationRequest ────▶  CSMS
                       (data, tbc?, seqNo, generatedAt, requestId)
Charging Station  ◀─── NotifyCustomerInformationResponse ────  CSMS

(repeated until tbc = false)

Initiator

Charging Station → CSMS

Fields

Field Name	Field Type	Card.	Description
data	string [0..512]	1..1	Required. (Part of) the requested data. Format is unspecified — should be human readable.
tbc	boolean	0..1	Optional. "To be continued" indicator. Default `false`.
seqNo	integer	1..1	Required. Sequence number of this message. First message starts at 0.
generatedAt	dateTime	1..1	Required. Timestamp at the Charging Station when the message was generated.
requestId	integer	1..1	Required. The id from the originating `CustomerInformationRequest`.

Examples

{
  "data": "TransactionId=1234, kWh=12.5, lastSeen=2026-04-27T11:00:00Z",
  "tbc": false,
  "seqNo": 0,
  "generatedAt": "2026-04-27T12:34:56Z",
  "requestId": 77
}

{}

Schema

Source: schemas/NotifyCustomerInformationRequest.json, schemas/NotifyCustomerInformationResponse.json (OCPP 2.0.1 FINAL)

Request schema (JSON Schema)

Response schema (JSON Schema)