What happens
You send the start command from the platform (or the driver pays by QR) and the charger answers Rejected, or answers Accepted but charging never starts.
Check it in two minutes
The test server has a “Start charging” button: it sends the remote start to your charger and shows you what it answers and what it does next (whether charging starts, whether it sends meter values, how it closes the session). Open the OCPP test server →
The causes, most likely first
1. The car isn't plugged in
Many chargers only accept a remote start with the cable already connected (connector in Preparing). Others accept it and wait a while for the plug.
How to fix it: Plug in first, then start.
2. It asks for confirmation on screen
Some units have an option that requires touching the screen after a remote start: the charger accepts the command and waits.
How to fix it: Turn off User confirmation required on remote start or its equivalent.
3. It authorises the card before starting
With AuthorizeRemoteTxRequests=true, the charger asks permission for the card that comes with the command. If the platform doesn't recognise it as valid, it won't start.
How to fix it: Set AuthorizeRemoteTxRequests=false, or use a registered card.
4. The connector isn't available
Connector Faulted, Unavailable or reserved for another card: the charger rightly refuses.
How to fix it: Check the connector status and free it (ChangeAvailability, cancel the reservation).
What askacharge.com does
Every command carries a tracking number (also over the API): askacharge.com tells “the charger accepted” apart from “charging really started”, and if the second doesn't arrive in time the command is marked as timed out instead of being taken as done.
Frequently asked questions
Why does RemoteStartTransaction return Rejected?
The most common causes: the connector isn't available (faulted, reserved, or with no car plugged in on some models), or the charger doesn't accept the card that comes with the command.
The charger accepts the remote start but doesn't charge, why?
It's usually waiting for the car to be plugged in or for someone to confirm on the screen. Check for a user-confirmation option on remote starts.