The session stops at authorization
The session gets as far as payment selection or authorization and no further: the charger answers Ongoing until the car gives up, or refuses the payment option or the contract. External identification against Plug and Charge, and what to look for.
What you see
- AuthorizationReq and AuthorizationRes (ContractAuthentication in DIN SPEC 70121) repeat with EVSEProcessing Ongoing, and the session ends before ChargeParameterDiscovery.
- Or a FAILED response to PaymentServiceSelection, PaymentDetails or Authorization.
- The verdict is Never charged, with Authorization not granted when the loop was still Ongoing at the end, or FAILED response when a code refused the step.
Two ways to authorize
| External identification (EIM) | Plug and Charge (PnC) | |
|---|---|---|
| Who identifies the customer | Something outside the V2G link: an RFID card, an app, a remote start from the backend, or free charging | The car, with a contract certificate and its private key |
| Payment option | ExternalPayment | Contract |
| TLS | Optional in ISO 15118-2; DIN SPEC 70121 sessions normally run without | Required |
| Messages in ISO 15118-2 | PaymentServiceSelection, then AuthorizationReq without a challenge, repeated | PaymentServiceSelection, PaymentDetails with the contract chain, then a signed AuthorizationReq that echoes the challenge |
| What the charger waits for | The customer, and its backend | Its backend, or a local check, to accept the contract |
| ISO 15118-20 | AuthorizationSetupRes lists the services; AuthorizationReq selects EIM | The same with PnC: the challenge comes in AuthorizationSetupRes, the contract chain in AuthorizationReq |
Either way the charger may answer Ongoing while it waits, and the car repeats its request. ISO 15118-2 and ISO 15118-20 also have Ongoing_WaitingForCustomerInteraction for a charger that waits for the customer, for example to present a card. The car keeps repeating until V2G_EVCC_Ongoing_Timeout, 60 s in the profile, and then ends the session. TIM-02 measures the loop.
Likely causes
| Cause | Who | How to confirm |
|---|---|---|
| Nobody presented a card or started the session in the app before the car gave up | User or EVSE | An Ongoing loop that runs until the car closes the connection; no Authorize in the OCPP log before that moment |
| The backend is slow or unreachable, so the charger cannot confirm the card | EVSE | An Authorize in the OCPP log without an answer, or with one that came after the car left |
| The charger expects the card at another moment, for example before the plug goes in | EVSE | An Authorize in the OCPP log outside the window of the Authorization loop |
| The car selected Contract, but the charger did not offer it | EV | SQ-07 and the PaymentOptionList of ServiceDiscoveryRes; FAILED_PaymentSelectionInvalid |
| The contract certificate is missing, expired, or its chain leads to a root the charger or backend does not know | EV or backend | FAILED_CertChainError, FAILED_CertificateExpired or FAILED_NoCertificateAvailable in the responses |
| The contract was revoked or cancelled | Backend | FAILED_CertificateRevoked, FAILED_ContractCanceled |
| The signature over AuthorizationReq or the echoed challenge does not match | EV | FAILED_SignatureError, FAILED_ChallengeInvalid |
| The charger offers Contract, but its backend cannot validate contracts | EVSE | Plug and Charge cars stay Ongoing until the timeout, while EIM sessions at the same charger pass |
What to check in this tool
- Message tab of ServiceDiscoveryRes: the PaymentOptionList, and whether a certificate service is offered.
- PaymentServiceSelectionReq: which option the car chose. SQ-07 flags a choice that was not on offer.
- Timers tool and TIM-02: how long the Authorization loop ran, against its limit.
- OCPP tab, with the charger's OCPP log loaded: Authorize, the start of the transaction and the connector status on the same timeline as the loop. OCPP 2.0.1 can carry the data of a Plug and Charge contract in Authorize; OCPP 1.6 needs an extension for it.
- TLS tab for Plug and Charge: the contract messages travel inside TLS, so load the key log to see them.
Fixes that usually work
- For EIM, present the card before or right after plugging in, and check the charger's configuration for the order it expects.
- Check the backend connection and how fast Authorize is answered. A backend that answers after the car has given up is as good as none.
- Let the charger offer only the payment options it can complete: no Contract without a backend that validates contracts.
- For Plug and Charge, check that the contract chain and the trust store of charger and backend belong to the same PKI (test or production), and that the contract is valid on the day of the test. See Plug and Charge and its PKI and Certificate lifecycle: validity, renewal and revocation.
V2G_EVCC_Ongoing_Timeout (tim.ongoingTimeoutS, 60 s) is flagged for verification in the limit profile.
The verdict Authorization not granted is chosen when the last AuthorizationRes still reads Ongoing or Ongoing_WaitingForCustomerInteraction and no ChargeParameterDiscoveryReq followed; for the second, the verdict says that the charger was waiting for the customer. TIM-02 measures how long either loop lasted.
Sources
- ISO 15118-2:2014, PaymentServiceSelection, PaymentDetails, Authorization, timing tables
- DIN SPEC 70121:2014-12, ServicePaymentSelection and ContractAuthentication
- ISO 15118-20:2022, AuthorizationSetup and Authorization
- OCPP 1.6 and 2.0.1, Authorize, Open Charge Alliance