NotifyCustomerInformation
Delivers the customer data requested by CustomerInformation.
- Version
- OCPP 2.0.1
- Direction
- Charge Point → CSMS
- Functional block
- Diagnostics
Split across parts with seqNo and tbc like the other Notify messages. The payload is free-form text — the spec does not define its structure.
Request
| Field | Type | Required | Description |
|---|---|---|---|
data | string | Required | The customer data. Up to 512 characters per part. |
seqNo | integer | Required | Part number. |
generatedAt | dateTime | Required | When this part was generated. |
requestId | integer | Required | Matches the CustomerInformation request. |
tbc | boolean | Optional | True when more parts follow. |
json
[2, "19223201", "NotifyCustomerInformation", {
"requestId": 1101,
"seqNo": 0,
"generatedAt": "2026-09-09T11:00:00Z",
"data": "idToken 04A1B2C3D4E580: 3 cached authorizations, 2 stored transactions"
}]Response
No fields — the payload is an empty object {}.
json
[3, "19223201", {}]Implementation notes
512 characters per part means any real answer arrives in several messages. Concatenate in seqNo order until tbc is false.
The format is vendor-defined. Do not expect to parse it consistently across manufacturers.