The reach-vs-control trade-off in fleet payment is going away

Every fleet payment conversation eventually comes back to the same tension. The driver wants a card that works everywhere, with as little friction as possible. The business paying the bill wants to know where that card was used, for what, by whom, and whether it was within the rules.

For most of fleet payment’s history, those two needs sat on opposite sides of a decision. Broad acceptance meant a general-purpose payment card and losing most of the control. Tight control meant a closed-loop fleet card and giving up acceptance beyond the provider’s network.

That trade-off shaped how a generation of fleet payment products got built. It also shaped what their customers put up with. This article looks at why reach and control sat apart for so long, what has changed, and what partners can do now that didn’t make commercial sense ten years ago.

Why reach and control split in the first place

The oldest payment cards (credit cards) worked everywhere because the schemes handled authorisation, acceptance and settlement in a standardised way. That standardisation gave the card its reach. The trade-off was that the data flowing back to the issuer was thin: amount, merchant, date. For fleet businesses that needed to know “was this fuel, how many litres, at what price, by which driver,” that wasn’t enough.

So the industry built a second type of card, aligned to a defined set of accepting merchants. The closed-loop fleet card. Narrower reach, but every transaction came with detail. Because the acceptance side was contractually tied in, control, data and reporting could all be set at the network level.

That gave businesses the oversight they needed. It also gave drivers a handful of fuel cards for proper coverage in Germany and a wallet of plastic to keep track of. The compromise was baked into the model.

What changed

Three things have shifted the picture in recent years.

1. Scheme-level data is catching up: the detail that closed-loop fleet cards used to be the only source of (litres, product, price, VAT) is starting to appear in open-loop too. Within connected acceptance networks it’s already available today, through system-level integrations. Visa Fleet 2.0 is set to broaden that at scheme level, though wide adoption by merchants and acquirers will take time.¹
2. Issuers can set controls programmatically: what used to require a dedicated acceptance network can now be done through the issuing layer. Service categories, spend limits, day-level rules, geographic rules. All configurable per card, per customer, per driver, without a closed network behind it. Reach is no longer the price you pay for control.
3. Regulation is nudging the market the same way: AFIR already requires regular bank cards to work at public high-power chargers above 50 kW. At lower-powered chargers it requires safe, transparent payment.² Both push payment at the pump and charger towards schemes drivers already know how to use. The direction is open-loop acceptance across more and more services.

What that means for partners

A fleet product no longer has to pick a side. A partner can offer a card that works across fuel, charging, parking, car wash and tolls where open-loop acceptance supports it, while still setting the controls a fleet business expects: who can spend what, where, on which service, under what conditions.

The driver gets one card and no new behaviour at the till. The business gets a configuration layer sitting underneath, deciding what the card does and what it doesn’t. What used to need two cards, two networks and two conversations now sits in one offer.

What stays the partner’s job

The scheme and the issuer can handle reach and the mechanical side of control. What they can’t do is decide the control logic itself. That is where the partner’s work still lives.

A logistics operator and a leasing fleet need different rules. A fuel retailer extending into charging wants different limits than a parking operator extending into fleet. The decisions about which services to open up, which rules to set, and which data to use for pricing or product development stay with the partner. The scheme delivers the capability. The partner shapes it into a product that fits a specific customer base.

Where XXImo fits

XXImo provides the stack that lets partners combine open-loop reach with closed-loop control under their own brand. The regulated base (EMI licence from De Nederlandsche Bank, Visa Principal Member, PCI DSS certified), Visa network access with Visa Fleet 2.0 certification, the Partner Portal, and APIs that let partners configure controls, consume data and shape their product the way their customers need it.

The partner keeps the brand, the customer relationship and the control decisions. XXImo keeps the stack working underneath.

Talk to an expert

Sources

¹ Visa Fleet & Mobility ecosystem launch, Visa Corporate. https://corporate.visa.com/en/sites/visa-perspectives/innovation/visa-launches-fleet-and-mobility-ecosystem.html

² Alternative Fuels Infrastructure Regulation (AFIR), (EU) 2023/1804, European Commission. https://eur-lex.europa.eu/eli/reg/2023/1804/oj/eng

‍