TC_068_CS — Stop transaction - IdTag in StopTransaction matches IdTag in StartTransaction

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 11.

Identification

Field	Value
Test case name	Stop transaction - IdTag in StopTransaction matches IdTag in StartTransaction
Test case Id	TC_068_CS
System under test	Charge Point

The Charge Point stops a transaction when a card is swiped with the same idToken as used to start the transaction.

Check whether the Charge Point is able to handle a stop transaction with same idToken.

Configuration State(s):

Memory State(s):

Reusable State(s):

Charge Point (SUT)	Central System (Tool)
[EV driver authorizes / swipes card with a different IdTag than the one used to start the transaction. This IdTag needs to be configured at the <Configured Valid IdTag 2> field.]; 1. The Charge Point does NOT send an Authorize.req and The Charge Point does NOT send a StopTransaction.req; Note: Sending a Authorize.req is valid in case the Charging Station has one rfid reader for multiple evse.
[EV driver authorizes / swipes card with the IdTag used to start the transaction]; [Step 3 and step 5 may be reversed.]; 3. The Charge Point sends a StopTransaction.req	4. The Central System responds with a StopTransaction.conf
[Step 3 and step 5 may be reversed.]; 5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf

Charge Point side:

Step 3:

(Message: StopTransaction.req) The idTag matches the idTag that was used to start the transaction.

Step 5:

(Message: StatusNotification.req) The status is Finishing

Central System side:

Charge Point side:

The Charge Point only stops the transaction when receiving the IdTag which was used to start the transaction.

Central System side: