This page is also available in French. Switch to French

This page is also available in Spanish. Switch to Spanish

Card rejected: Invalid, Blocked, Expired and ConcurrentTx

A rejected card is not an OCPP error code. It is the authorization status the management system sends back: Accepted, Blocked, Expired, Invalid ("Identifier is unknown") or ConcurrentTx (OCPP 1.6, §7.2).

What it means

Blocked and Expired: the server knows the card and refuses it.

Invalid: the server does not know it. ConcurrentTx: the card is already in another transaction and multiple transactions are not allowed; it only applies when a transaction starts (OCPP 1.6, §7.2).

The charger may answer from its own memory before it asks the server: from the Local Authorization List, which the management system sends, or from the Authorization Cache of cards it has seen (OCPP 1.6, §3.5). For the same card, the local list wins over the cache (OCPP 1.6, §3.5.3).

Because the charger may have used outdated information, the server must check the card again when the transaction starts (OCPP 1.6, §4.8). If that answer is not Accepted, StopTransactionOnInvalidId decides whether the charger stops the transaction or only stops delivering energy (OCPP 1.6, §3.5.4, §9.1.24).

In OCPP 2.0.1

There are more reasons, which help support teams.

Unknown now means an unknown identifier and Invalid means an invalid one. NoCredit, NotAllowedTypeEVSE, NotAtThisLocation and NotAtThisTime each mean the identifier is valid but not allowed to charge in that case (OCPP 2.0.1, AuthorizationStatusEnumType, §3.3).

A personal message can tell the driver why they are not allowed to charge (OCPP 2.0.1 Part 0, §2.8.5).

Likely causes

The ID the charger sends is not the one stored in your user database.

OCPP 1.6 treats an ID as a case-insensitive string of up to 20 characters (OCPP 1.6, §7.28, §7.15), so upper and lower case do not matter, but every other character does.

ConcurrentTx while the server still has an open transaction for the same ID (OCPP 1.6, §7.2), for example one whose StopTransaction has not arrived yet. A charger that was offline queues its StopTransaction and sends it when the connection returns (OCPP 1.6, §3.7).

A card blocked on the server but still Accepted in an old local list on the charger. When the charger notices such a conflict it reports LocalListConflict (OCPP 1.6, §3.5.2).

First three checks

  • 1.

    Read the status in the answer. Blocked, Expired, Invalid and ConcurrentTx each point somewhere different.

  • 2.

    Compare the ID the charger sent with the one in your user database, character by character.

  • 3.

    For ConcurrentTx, look for an open transaction with the same ID.

What to do

  • Safe remote action

    Fix the record on the server, then send the local list again with SendLocalList; a Full update is the safe retry after a failed Differential one (OCPP 1.6, §5.15). RemoteStartTransaction can start the driver now, but if AuthorizeRemoteTxRequests is true the charger checks the ID first (OCPP 1.6, §5.11).

  • Dispatch when

    Never for a rejected card alone. If no card works on a charger, see ReaderFailure.

  • Do not

    Do not clear a charger's cache or list to fix one card before you know which status caused the refusal.

What to tell the customer

"Your card was refused because our system didn't recognize it.

We've corrected your account. Please try again in a minute."

A detection rule to start from

Repeated rejected authorizations on one charger across different cards, above a threshold you set: check the reader and the local list version.

One card rejected on several chargers: check that card's account.

Sources

  1. Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2 (opens in a new tab). §3.5 Local Authorization & Offline Behavior, §3.7 Transaction-related messages, §4.8 Start Transaction, §5.11 Remote Start Transaction, §5.15 Send Local List, §7.2 AuthorizationStatus, §7.15 CiString20Type, §7.28 IdToken, §9.1.24 StopTransactionOnInvalidId; accessed 2026-10-22.
  2. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 0 – Introduction (opens in a new tab). §2.8.5 Personal message; accessed 2026-10-22.
  3. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 2 – Specification (opens in a new tab). Messages, Datatypes & Enumerations §3.3 AuthorizationStatusEnumType; accessed 2026-10-22.

Talk to us about your chargers

What happens next

  1. Tell us about your network.
  2. Meet a Kinethra specialist.
  3. Get your chargers live on Kinethra.
  • 40,000+ chargers onlineOn the Kinethra platform.
  • OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
  • No commission on charging revenueKinethra takes none.
  1. 01Contact
  2. 02Business
  3. 03Request

Step 1 of 3

We use your details to answer your request. See our Privacy Policy for details.