Are EV payment declines really a card problem, or a payment flow problem?

• A “failed payment” at the charger is often a flow or configuration issue, not a simple card or issuer problem.
• Fragmented EV estates make it hard to see whether declines are driven by hardware, authentication, acquirers, or customer behavior.
• Better visibility should point to concrete fixes (clearer prompts, smarter retries, stronger fallbacks), not just higher‑level decline dashboards.
• An orchestration layer can improve EV acceptance (by roughly 10% in some cases) across existing chargers and terminals, without replacing the whole estate.

Don't have time to read more now? Sign up to our newsletter to get the latest insights directly in your inbox. 

...Your EV is running low on battery, so you pull into the nearest charger. You plug in, tap to pay - and nothing. The screen throws an error. 

Another attempt, same outcome.

From the driver's point of view, it's simple: the charger didn't work. But it's rarely that simple from the operator's point of view. 

The failure could sit anywhere across the payment flow: the card, terminal, charger, acquirer, authentication process, pre-authorization rules, or somewhere else in the payment journey entirely.

In complex, multi-market charging estates, a payment decline is often the end of a chain of small decisions and configurations - not a hard no from an issuer.

That changes what success should be measured against. Instead of looking at headline failure rates, the more useful question is visibility: can you actually see where in the payment journey things are breaking down, and which part of the stack is responsible when they do?

That’s what we’ll be exploring today.

EV charging hasn’t developed in the same way as fuel payments. Forecourt transactions evolved over decades into a stable, predictable model, whereas EV has had to scale fast, across a fragmented and inconsistent infrastructure.

The hardware stack also differs, from integrated terminals to standalone devices or fully app-based virtual terminals.

Add in cross-border differences - scheme rules, SCA requirements, acquirer behavior, local payment method expectations - and each part of the estate can behave quite differently from the next.

At that point, “failed payments” becomes a blunt metric that hides more than it reveals. Unless you can separate those failures by charger type, payment flow, market and decline reason, all you’ll know is that acceptance is dropping - without ever knowing what to fix.

Not every decline is a true rejection

This is where it gets interesting, and where a lot of the value is being left on the table.

Some failures are genuine issuer decisions - blocked cards and fraud flags will always exist. But many sit elsewhere in the payment journey.

The failures that aren't genuine rejections tend to fall into a few categories:

• Session and pre-auth rules - amounts or expiry logic that create confusion, especially on longer charges
• Journey misreads - drivers switching between app and card, or between consumer and fleet, and hitting a flow that doesn't behave as expected
• Operational configuration - terminals set up inconsistently across charger types, fallback logic that breaks when a connection drops, routing rules that push certain transactions down unreliable paths

If a meaningful share of declines comes from PIN handling, SCA flows, and configuration issues, then a lot of those transactions were likely recoverable from the start. At the scale of a major charging network, that’s a significant amount of lost revenue.

Fragmented estates can hide the real cause of acceptance loss

Most operators know when payments are failing. The harder question is whether you can tell which failures were recoverable, which were behavioral, and which were operational.

That gap is where the revenue goes. Getting past a headline decline rate means knowing which questions to ask - then having the data to answer them.

For a network running thousands of charge points across multiple countries, those questions can't be answered by a single dashboard. You need visibility that's granular enough to separate a network-level pattern from a site-level issue - and structured enough to tell teams what to do next, not just what went wrong.

“Here’s the decline rate” isn’t enough on its own - the point is to get to a short list of fixable causes and specific next actions.

Better visibility has to change what happens at the charger

Data is only useful if it helps you change what happens at the charger.

Decline pattern visibility should translate directly into better recovery journeys. That might mean clearer prompts at the point of payment, so drivers know when they need to insert a PIN or complete an extra step instead of silently timing out.

It should also show where recovery can happen before the journey breaks. A soft decline may need another attempt, while repeated failures on the same acquirer path may point to a routing issue. If SCA is causing customers to drop out, the answer may be to redesign how that step appears in the charging journey, rather than treating the failed transaction as unavoidable.

Consistency across the EV estate matters too - drivers shouldn’t have to relearn the payment journey every time the charger setup changes.

A failed payment at the charger feels like a failed charge. The driver doesn’t know if the problem was the card, the terminal, the authentication step, or the acquirer. They just know they couldn’t start - and next time they might choose a different network.

For operators investing heavily in building that network, trust is won or lost at the point of charge.

When acceptance across your EV payment estate starts to suffer, the natural instinct is often to talk about replacing hardware or rebuilding integrations. But for a network of any real scale, that's rarely the right answer - it's slow, expensive, and often recreates the same fragmentation in a new setup.

The more practical route is an orchestration layer that works across the estate already in place. Sitting between chargers, terminals, software stacks and acquirers, it gives operators a clearer point of control for routing, authentication rules, fallbacks and reporting without forcing every site or market into the same setup.

It also creates room to bring consumer and fleet journeys closer together on the same devices and flows, so operators aren’t forced to run parallel B2C and B2B stacks just to keep different card types and controls alive.

For larger operators, the key value is visibility. Instead of chasing issues one charger at a time, you can look at payment performance across different environments on a like-for-like basis, see where acceptance is being lost, and understand which fixes are likely to make the biggest difference first.

In unattended and EV environments, better routing, clearer journeys, and improved visibility through our orchestration platform have helped operators lift acceptance rates by around 10% by recovering transactions that were failing for preventable, in-journey reasons.

And this isn’t just an EV story. When fuel, EV, and in‑store payments all sit on top of the same orchestration layer, operators can see and improve acceptance across the whole mobility and retail estate, rather than solving the same problems three times in different parts of the stack.

EV payment acceptance comes down to understanding what sits behind approvals and declines, and how payment journeys behave across the charging network.

For operators running large, mixed charging estates, a single performance number only tells part of the story. To get the real picture, you have to ask what the data is actually showing:

• Which failures are genuine rejections?
• Which are recoverable? 
• Which are caused by authentication, configuration or flow design? 
• And which fixes would have the biggest impact first?

That is the difference between counting declined payments and knowing what to fix next.

Want to understand where acceptance is being lost across your EV payment estate? Speak to Aevi about improving EV payment performance without replacing everything underneath.