The real work of a fleet proposition isn’t the card

What a driver sees of a fleet card is five seconds at the pump. What a partner has to build and run behind that card is something else entirely: the rules that decide what each card can do, the data each transaction returns, the compliance, the reporting, the reconciliation.

Two parts of that behind-the-scenes layer do most of the strategic work: the service controls that shape what the card can and cannot do, and the transaction data that comes back from everything the card does.

This article looks at both. What they actually contain, why they matter more than the card itself, and how partners use them to build offerings that stand out.

Service controls: what makes a card a fleet card

A card without rules is just a card. What turns it into a fleet product is the layer of logic around it, deciding where it works, how much it works for, and what it works for.

The basic controls are familiar enough. Daily and monthly spend limits. Product categories, so a driver can buy diesel but not confectionery. Day-level rules, so the card works on business days only. Geographic rules, so a card for a Dutch fleet doesn’t suddenly surface in Spain. Vehicle-level and driver-level limits layered on top of each other.

The more interesting controls sit on top of those basics:

• Service-specific limits (a card can pay for charging up to one amount, tolls up to another)
• Per-user service access (one driver can use charging, another can’t; one gets parking, another doesn’t)

How these controls are set up is where fleet partners end up differing. A partner selling to a logistics operator will configure them differently than one selling to a knowledge-worker business. Both can run on the same payment infrastructure. What makes each offer unique is the control logic on top.

Data: what the product gives back

The second layer where the real work happens is what comes back from the system.

Every transaction has a story to tell. Who paid, where, when, for how much, for what. Properly captured and structured, that story becomes several things at once:

• A billing input (one invoice, built automatically from thousands of transactions)
• A VAT reclaim input (which only works if the data has the right granularity)
• A reporting input (fleet manager, finance, procurement each need a different view)
• A pricing input (what services does this customer actually use? What can be bundled, upsold, repackaged?)

The quality of that data defines how useful the product is beyond the moment of payment. Thin data (amount, merchant, date) gives you something close to a bank statement. Rich data (product, quantity, price, VAT) gives you the raw material to build real business value on top of.

Visa Fleet 2.0 is set to standardise this at scheme level. Still rolling out, but worth tracking: the direction is consistent structured data across issuers.¹

Where partners actually compete

Most fleet payment products in the market today look similar on the card side. Where they differ is on these two layers.

An offer tuned for a lease fleet weighs different controls (vehicle-level discipline, VAT reclaim quality) than one tuned for a logistics operator (per-shift limits, high-frequency transactions). A fuel retailer extending into charging will care about how the data lets them understand customer behaviour across both. A charging platform will care about how the controls let them manage access across different charger networks.

The card is table stakes. The way the controls and data are set up is what makes the offer yours.

What that requires

To run both layers properly, a fleet partner needs more than a card issuer:

• An infrastructure that supports flexible controls without custom development for every change
• A data pipeline that captures and structures transactions at the right level of detail
• A regulatory base that lets them operate the whole stack without building out compliance from scratch
• APIs and a Partner Portal so controls and data plug into the systems the partner already runs

Building each piece separately is possible. Doing it together, as a working stack, is where most partners get stuck.

Where XXImo fits

XXImo provides the fleet payment stack that supports both layers. The regulated base (EMI licence from De Nederlandsche Bank, Visa Principal Member, PCI DSS certified), the Visa Fleet 2.0 rails, the Partner Portal, and APIs that let partners configure their own controls and consume their own structured data.

Partners build their offer on top: their brand, their customer relationships, their control logic, their reporting. The payment stack sits behind.

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

‍