RemoteStopTransaction

RemoteTrigger CSMS->CP

Sent by the Central System to remotely stop a charging transaction.

Quick Reference

Required Fields

transactionId integer

ID of the transaction to stop

Example Payload

{
  "transactionId": 12345
}

Example Full Frame

[
  2,
  "msg-001",
  "RemoteStopTransaction",
  {
    "transactionId": 12345
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

The RemoteStopTransaction command allows the Central System to terminate an active charging session remotely.

When Received

  • User requests charging stop via mobile app
  • Emergency stop initiated by operator
  • Transaction time limit reached
  • Payment authorization expired

Expected Response

The CP responds with:

  • status: Accepted or Rejected

What Happens After Acceptance

  1. CP stops energy flow to vehicle
  2. CP sends StopTransaction message with reason “Remote”
  3. Transaction is finalized

Usage Notes

  • transactionId must match an active transaction
  • CP may delay stopping to allow vehicle to properly disconnect
  • Final meter values sent in StopTransaction message

Best Practices

  1. Transaction validation - Verify transaction is active before sending
  2. Graceful stop - CP should allow vehicle time to disconnect safely
  3. User notification - Inform user that session was remotely stopped
  4. Billing - Ensure final meter values are captured accurately

Testing Tips

  • Test with valid active transactionId
  • Test with invalid transactionId to verify rejection
  • Test with already stopped transaction
  • Verify StopTransaction includes reason “Remote”

Common Errors

GenericError

Cause: Transaction not found or already stopped

Solution: Verify transactionId is correct and transaction is active

Related Actions

RemoteStartTransaction StopTransaction