Fleet Cards
Companies that maintain fleets of vehicles need a reliable way to track and control expenses for their vehicles, such as fuel and repairs.
Mastercard offers specialized fleet-card BINs that provide enhanced authorization, clearing and reporting capabilities. Fleet-card issuers can receive data such as driver ID or vehicle ID both at the time of authorization and at settlement. Galileo parses the fleet data that Mastercard provides and then passes it to you so that you can perform detailed expense analysis.
There are two kinds of fleet cards:
-
Driver-issued cards — Your customer is a delivery service with a fleet of trucks. They would like to issue fleet cards to individual drivers to buy fuel and maintenance. Depending on the driver's profile, the card can be used for some purchases but not others. For example, some drivers can use their cards at all fuel merchants, repair shops, and parts stores. Other drivers can additionally use their cards for travel expenses such as lodging and meals. Different spending controls can be imposed so that some drivers can spend more than others, depending on their responsibilities.
Your customer needs detailed reporting on how funds are spent, such as knowing exactly what portion of a gas-station purchase went toward fuel and how much was spent on accessories. With this data, your customer can better manage their costs and plan for future expansion.
-
Vehicle-issued cards — You are a private security firm with a fleet of armored vehicles and highly trained personnel. You need to bill your clients for fuel and maintenance costs based on mileage. The fleet card remains with the vehicle rather than being issued to individual drivers so that you can track the vehicle's lifecycle and expenses and then bill your clients accordingly.
Fleet card data
The fleet-card information is divided into levels 2 and 3.
Galileo is compliant with the fleet card standards set by Mastercard that align with new industry standards. Galileo provides you with legacy and enhanced fleet data.
Level 2 data
Provided at authorization and settlement.
- Vehicle ID
- Driver ID
To receive level 2 data at the time of authorization, you must consume the Auth API.
Level 3 data
Provided at settlement.
The following includes both legacy and enhanced fleet data.
Legacy
- Oil company brand name
- Purchase time
- Motor fuel service type
- Product code
- Item description
- Item quantity
- Item quantity
- Item exponent
- Item unit price
- Item unit price
- Item unit price exponent
- Item unit of measure
- Extended item amount
- Extended amount
- Extended amount exponent
- Extended amount sign
- Debit or credit indicator
- Motor fuel information
- Motor fuel product code
- Motor fuel unit price
- Motor fuel unit of measure
- Motor fuel quantity
- Motor fuel quantity exponent
- Motor fuel sale amount
- Odometer reading
- Vehicle number
- Driver ID
- Product type code
- Card acceptor type
- Card acceptor tax ID
Enhanced
- Fleet spend control enforced
- Fleet fuel information
- Fleet fuel product code
- Fleet fuel unit price
- Fleet fuel unit of measure
- Fleet fuel quantity
- Fleet fuel quantity exponent
- Fleet fuel sale amount
- Fleet prompted data 1
- Prompt code 1
- Driver related data 1
- Fleet prompted data 2
- Prompt code 2
- Driver related data 2
- Fleet prompted data 3
- Prompt code 3
- Driver related data 3
- Fleet prompted data 4
- Prompt code 4
- Driver related data 4
- Fleet prompted data 5
- Prompt code 5
- Driver related data 5
- Fleet product code
- Fleet item description
- Fleet item quantity
- Fleet item quantity
- Fleet item quantity exponent
- Fleet item unit of measure
- Fleet extended item amount
- Fleet extended item amount
- Fleet extended item amount exponent
- Fleet extended item amount sign
Viewing fleet data
You get level 2 and level 3 data through these means:
- Auth API
fleet_info
objectfleet_card_driver_number
fleet_card_vehicle_number
fleet_prompt_data
merchant_override_indicator
control_override_items
fuel_info
non_fuel_info
BAUT: auth
/AAAU: auth
event messagesfleet_card_driver_number
fleet_card_vehicle_number
- Fleet Data RDF, which is expanded settlement data that includes level 2 and 3 data
MCC restrictions
When you set up your fleet card product, you will determine which MCCs to block and allow. You can determine whether to allow only the fuel-related MCCs or whether to include maintenance MCCs as well. For vehicle-assigned cards, only fuel and maintenance MCCs are allowed.
For example, the default product-level settings for a driver-assigned card could include fuel and maintenance, as well as impose per-week spending limits. Then for selected drivers you could add support for lodging and food plus higher spending limits on a per-account basis. See Account-Level Authorization Controls for more information.
Fuel
- 4468 — Marinas, marine service/supplies
- 5499 — Miscellaneous food stores: convenience stores, markets, and specialty stores
- 5541 — Service stations, with or without ancillary services
- 5542 — Fuel dispenser, automated
- 5983 — Fuel dealers: coal, fuel oil, liquefied petroleum, wood
Maintenance
- 5013 — Motor vehicle supplies and new parts
- 5511 — Automobile and truck dealers: sales, service, repairs, parts and leasing
- 5531 — Auto store, home supply stores
- 5532 — Automotive tire stores
- 5533 — Automotive parts, accessories stores
- 5599 — Miscellaneous automotive, aircraft, and farm equipment dealers, not elsewhere classified
- 7531 — Automotive body repair shops
- 7534 — Tire retreading and repair shops
- 7535 — Automotive paint shops
- 7538 — Automotive service shops
- 7542 — Car washes
- 7549 — Towing services
- 7692 — Welding repair
- 7699 — Miscellaneous repair shops and related services
Updated 8 days ago