How can a fleet card automatically restrict usage to EV charging stations only?
A fleet card can automatically restrict usage to EV charging stations by embedding controls directly into the payment flow and by combining advanced spend controls, real-time authorisation rules, and API-driven configuration. This allows issuers to approve eligible EV charging transactions while blocking other types of unauthorised spend.
What does restricting a fleet card actually mean?
Fleet cards are no longer limited to fuel payments. Businesses increasingly want one payment method that can support EV charging, parking, tolls, and wider mobility expenses. The challenge is balancing wider acceptance with tighter control.
Restricting a fleet card means controlling:
- Where the card can be used
- What the card can be used for
- When transactions are allowed
- How payments are made
- How much can be spent
These rules can be applied at the individual card, card group, or portfolio level. When more than one rule applies, the strictest one is enforced automatically, so fleet-wide controls and a vehicle-specific limit can coexist without conflict.
These controls are enforced through advanced spend controls and real-time authorisation logic, giving issuers the flexibility to define exactly how cards can be used.
Issuers can either:
- Start with broad acceptance and apply restrictions
- Begin with a tightly controlled setup and selectively allow services
These controls can be updated instantly without replacing cards. This gives fleet managers ongoing flexibility as operational needs evolve.
Why restrict a fleet card to EV charging only?
EV-only fleet cards help businesses maintain control while simplifying fleet payments.
Key benefits include:
- Preventing misuse and fraud
- Reducing non-business spend
- Supporting EV transition strategies
- Avoiding multiple cards for different services
- Improving visibility into mobility spend
- Lowering administrative overhead
- Expanding acceptance without losing control
Drivers benefit from a simpler payment experience, while fleet managers retain detailed oversight.
EV-only is one valid configuration, typically chosen by mobility providers, EV charging networks, or employers issuing dedicated EV cards. The same advanced spend control capabilities also let issuers support EV charging alongside fuel, tolls, and other mobility spend on a single card, with rules applied per category.
How EV-only fleet card restrictions work
EV-only controls typically combine several layers of payment logic.
| Control Type | What It Does | Example |
| Merchant category controls | Restricts transactions by merchant type | Eligible EV charging approved, retail declined |
| Geolocation controls | Limits usage by country, region, or continent | Charging only allowed in the UK |
| Time-based controls | Restricts usage to approved hours | Charging only during work hours |
| Per-transaction limits | Limit the value of individual transactions. | £100 charging limit per transaction |
| Cumulative limits | Limit total spend or transaction count over time. | £750 daily fuel spend limit |
| Acceptance method controls | Restricts payment method | App payments allowed, physical card blocked |
1. Merchant category restrictions
Every merchant is assigned a Merchant Category Code (MCC), which identifies the type of business processing the transaction.
Issuers can use MCC filtering to approve EV charging transactions while declining other activity.
For EV charging in particular, MCC classifications are still evolving across schemes and regions, which is why most issuers layer MCC with other controls rather than relying on it alone.
For example:
- Eligible EV charging transaction → approved
- Fuel purchase → declined
- Retail purchase → declined
Many issuers also combine MCC filtering with additional controls such as merchant whitelisting, geography restrictions, or transaction thresholds for greater accuracy.
2. Real-time authorisation controls
Every card transaction is evaluated against issuer-defined rules at the moment of authorisation, not after the fact. This is what separates advanced spend controls from basic card limits: rules are applied instantly, so off-rule transactions are declined before they ever reach the cardholder’s statement.
During authorisation, the platform checks whether the transaction matches the rules assigned to the card. Transactions outside those rules are declined immediately.
An EV-only setup could include rules such as:
- Eligible EV charging transaction → approved
- Fuel station purchase → declined
- Transaction outside approved countries → declined
Because these controls operate in real time, policies can be adjusted instantly without disrupting drivers or reissuing cards.
3. Advanced spend controls
MCC filtering alone is rarely enough. More advanced controls create tighter and more reliable restrictions.
a) Geolocation controls
Allow charging only within approved countries or regions.
b) Time-based rules
Restrict charging to operational hours or approved usage windows.
c) Transaction limits
Set maximum spend values per transaction, per day, or per driver.
d) Cumulative limits
Cap total spend or transaction volume over a fixed or rolling period, such as £100 per week on EV charging, or a maximum of 5 charging sessions in 24 hours.
Limits can reset on a fixed schedule (daily, weekly, monthly, quarterly, yearly) or on a rolling basis (counted from the last transaction). When multiple limits apply, the strictest one is always enforced.
Refunds and reversals don’t free up the limit, so the control reflects actual usage.
e) Combined rules
Multiple conditions can work together, such as:
- MCC + country
- MCC + transaction amount
- MCC + time of day
This layered approach reduces misuse risk while maintaining operational flexibility.
4. Tokenisation and acceptance method controls
Restrictions can also apply to how payments are initiated.
Controls can be enforced across:
- Physical cards
- Virtual cards
- Mobile wallets
- In-app payments
- Tokenised transactions
This is particularly important because many EV charging payments are initiated through mobile applications rather than traditional payment terminals.
Issuers can also block specific transaction types, for example, blocking magstripe transactions while allowing tokenised app payments, which is especially relevant for EV use cases where most payments are initiated in-app.
5. API-driven configuration
Behind the scenes, issuer platforms and APIs manage these controls dynamically.
This enables issuers to:
- Configure rules at card, group, or fleet level
- Update restrictions in real time
- Move cards between groups without reissuing
- Apply bulk policy changes across fleets
- Centrally manage and update rules across thousands of cards instantly
Since you can manage many cards at once and update multiple cards simultaneously in real time, this means no engineering tickets and no card reissuing because changes go live instantly.
As fleet requirements evolve, payment policies can evolve with them.
Limitations and considerations of EV-only restrictions
MCC filtering is essential but rarely sufficient on its own.
While fuel card transactions have long carried enriched Level 2/Level 3 data (e.g., fuel type, volume, VAT, tax breakdowns), EV charging via card networks doesn’t yet consistently support the same depth. Standard authorisation messages typically don’t include session-level detail such as:
- kWh usage
- Tariff data
- Detailed VAT and tax information, where available from the Charge Point Operators (CPOs)
- Charging duration
Deeper session-level visibility depends on additional data from charging point operators, acquirers, terminals, or payment networks, and many CPOs come from outside the fleet payments ecosystem, so long-standing fuel card data standards don’t always carry over..
Market maturity also varies between countries. Open-loop EV charging payments are improving rapidly, supported by regulations like AFIR pushing toward more standardised, card-accessible charging infrastructure across Europe and the UK. But implementation consistency is not yet universal.
This is why layered, flexible controls, combining MCC with geography, time period, transaction limits, and acceptance method, are becoming increasingly important for fleet and mobility programmes.
How Enfuce supports EV-only fleet card controls
Enfuce is a dual-licensed EMI (EU and UK) and principal member of Visa and Mastercard. Our card issuing and processing platform enables issuers to configure detailed spend controls and real-time authorisation management for fleet and mobility programmes. This allows issuers to combine broad open-loop acceptance with closed-loop-like control.
With Enfuce, you can apply controls based on:
- Merchant category
- Geography
- Transaction amount
- Time restrictions
- Acceptance method
These controls work across:
- Physical cards
- Virtual cards
- Tokenised and wallet-based payments
Through API-driven configuration, issuers can:
- Manage policies dynamically
- Create fleet and card hierarchies
- Update controls instantly without reissuing cards
- Combine broad acceptance with tightly controlled usage rules
Enfuce gives fleet providers the flexibility to support EV charging while maintaining strong oversight of mobility spend.
From spend control to strategic fleet payments
Restricting a fleet card to EV charging is only one example of what programmable payments enable. By embedding spend rules directly into the authorisation process, issuers can adapt payment products to changing fleet requirements without reissuing cards or redesigning programmes.
Fleet and mobility providers increasingly need payment products that can adapt to:
- Changing vehicle mixes
- Regional regulations
- New mobility services
- Multi-service transport ecosystems
In this environment, spend controls are no longer only a fraud-prevention feature. They are becoming a strategic tool for building scalable fleet and mobility payment solutions.
FAQs
Can an open-loop fleet card be restricted to EV charging only?
Yes. Open-loop fleet cards can use MCC filtering, real-time authorisation rules, and spend controls to approve EV charging transactions while declining other purchases. These same controls can also support EV alongside fuel and other mobility-related spending on a single card.
What happens if a driver tries to use the card at a fuel station?
If fuel purchases are outside the configured rules, the transaction is declined during authorisation.
Can EV fleet card restrictions be updated without replacing cards?
Yes. API-driven issuer platforms allow restrictions to be updated in real time without reissuing physical cards.
Do EV charging controls work with mobile apps and digital wallets?
Yes. Controls can also apply to tokenised transactions, in-app payments, and mobile wallet usage.
Are MCC restrictions enough on their own?
Not always. MCC classifications can vary across regions and payment providers. Many issuers combine MCC filtering with geography, transaction limits, and merchant controls for greater accuracy.
What’s the difference between per-transaction limits and cumulative limits?
Per-transaction limits cap the amount of a single transaction (e.g., max £50 per charging session). Cumulative limits cap total spend or transaction count over a chosen time period (e.g., £100 per week, or max 5 sessions per day). Cumulative limits can reset on a fixed schedule or operate on a rolling basis. When both are in place, the strictest limit applies.