Fleet Card Rules: The Data US Fuel Merchants Owe, and When

Fleet card transactions carry a data obligation that sits on the merchant, not just the acquirer. If you run service stations or unattended pumps in the US, you are already inside it. If you run EV charging, you are not, and you have until 13 April 2030.

That gap is worth stating plainly, because Visa's own Summary of Changes lists the US electric vehicle requirement without its date, which reads as though it has landed. The table it points at says otherwise.

What the merchant actually has to do#

Section 5.8.15.1 (ID# 0027525) applies in the US and names three merchant obligations for accepting a Visa Fleet Card:

• If the issuer requires it, provide the data collected by the service prompt indicator
• Pass complete and accurate prompt-input data along with the Visa Fleet Card Enhanced Data
• Comply with the Enhanced Data requirements in the Visa Fleet Card 2.0 Implementation Guide for Merchants, Acquirers, and Issuers

The prompt-input data is the part that touches your forecourt. Fleet cards prompt a driver for things a normal card never asks: odometer, vehicle number, driver ID, job number. The rule does not just require you to collect it. It requires the data you pass on to be complete and accurate, which makes a prompt your staff teach drivers to skip into a compliance problem rather than a UX choice.

The MCC table is where the dates live#

Section 7.4.9.3 (ID# 0031094) carries Table 7-8, which sets the required MCCs region by region. The US row is the one to read carefully:

So Europe already includes EV charging with no date qualifier. The US gets it in 2030. CEMEA does not get it at all in this edition.

A second detail follows the same split. The rule's footnote says enhanced data includes using Field 104, Dataset 1A in Europe, in CEMEA excluding South Africa, and, effective 13 April 2030, in the US and in AP Australia and New Zealand. The US format change and the US EV scope change land on the same date.

If you run charging under MCC 5552, the practical read is that nothing is required of you yet and the specification you will eventually build to is already published for Europe. That is a long runway, and it is unusual to get one.

The acquirer carries its own half#

The same section adds that an acquirer processing Visa Fleet Card transactions must provide both cardholder-supplied data and supplemental transaction data. So the data you capture at the pump has a second obligation attached to it downstream, which is why your acquirer will care about your prompt configuration even where you do not.

Fleet enhanced data is its own regime. It sits in Section 7.4.9.3 and defers to the Fleet guide, while commercial card data requirements sit separately in Section 7.4.10. Different sections, different rule IDs, different specifications, so the machinery you built for Level 2 and Level 3 data is not what this rule is asking for. What either one earns in interchange is a separate question the rules do not answer, because qualification criteria live in the rate qualification guide rather than in the rulebook.

On the issuing side, Section 4.22.1.1 (ID# 0004168) requires that a Visa Fleet Card is issued only as a driver-assigned card or a vehicle-specific fleet card, that the terminal captures or validates enhanced data, and in the US that the EMV chip is encoded with Visa Fleet-specific data. That last one explains why fleet acceptance is a terminal question and not only a gateway question, much like authorization holds at the pump.

There is a fuel discount program, and it runs through a Visa portal#

This is the part almost nobody writes about. Section 4.22.2.2 (ID# 0031019) governs the Visa Fleet Merchant Discount Program in Europe and the US, and it puts real administrative weight on a participating merchant. Through its acquirer, the merchant must:

• Complete a merchant enrollment form with Visa
• Comply with the Visa Rules and the Visa Fleet Card 2.0 Merchant Discount Program Implementation Guide
• Enter a legally binding agreement for each client it offers a discount to, including all discount details, before implementing the discount through the Visa discount portal
• Manage all aspects of the program, including presenting and managing the fuel discounts
• Provide enhanced data
• Register, maintain and enforce each program in the Visa discount portal, and update the details within 24 hours if a program is modified, suspended or terminated

Then the rule closes with a disclaimer worth quoting: "Visa shall not be liable for the accuracy of any information provided to Visa, incorrectly applied fuel discounts, or the failure to apply an eligible fuel discount."

Read those together. Visa provides the portal, requires you to keep it current inside 24 hours, and accepts no liability if a discount fails to apply. A per-client legally binding agreement before go-live is not a formality either. If you are offering fleet discounts to several hauliers on different terms, that is a contract per customer and a portal record per program.

The operative document is not public#

Four of the rules above defer to the Visa Fleet Card 2.0 Implementation Guide for what enhanced data actually means. Appendix A lists that guide as an enforceable requirement for CEMEA, Europe, LAC and the US, so it binds you.

Visa does not publish it openly. We could not locate a public copy, and the rules give no link. So the detail that decides whether your forecourt is compliant lives in a document you have to get from your acquirer. Ask for it by name, and ask which MCCs it applies to for your outlets. This is the same pattern as the Account Information Security Program Guide, where the rulebook sets the obligation and keeps the specification behind the acquirer.