Skip to content
Documentation Menu

Request Stop Transaction

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.45 (Messages); Use Cases F03 — Remote Stop Transaction, F04 — Remote Stop ISO 15118 Charging from CSMS (Functional Block F. RemoteControl)

Overview

The CSMS sends RequestStopTransactionRequest to ask the Charging Station to stop an ongoing transaction. The CS replies with Accepted/Rejected and, if accepted, drives the transaction to a normal stop — emitting TransactionEvent(Ended) with triggerReason = RemoteStop.

Replaces OCPP 1.6's RemoteStopTransaction.

Sequence Diagram

CSMS  ──── RequestStopTransactionRequest ────▶  Charging Station
            (transactionId)
CSMS  ◀─── RequestStopTransactionResponse ────  Charging Station
            (status, statusInfo?)
                                  (later: TransactionEventRequest(Ended) with triggerReason=RemoteStop)

Initiator

CSMS → Charging Station

Fields

Field NameField TypeCard.Description
transactionIdidentifierString [0..36]1..1Required. The id of the transaction to stop.

RequestStartStopStatusEnumType values

Accepted, Rejected.

Examples

{
  "transactionId": "tx-1234"
}

Schema

Source: schemas/RequestStopTransactionRequest.json, schemas/RequestStopTransactionResponse.json (OCPP 2.0.1 FINAL)

Request schema (JSON Schema)
Request schema (JSON Schema)