Home / Issuing / Control Authorizations
Highnote provides fleet-specific data from Visa and Mastercard during authorization requests, which can be used to enhance your collaborative authorization decision-making process. For an overview of the collaborative authorization feature, see Collaborative Authorization.
This guide provides an overview of each card network's fleet-specific data, examples of request bodies, and resources to simulate fleet transactions in your test environment.
When a cardholder initiates a transaction, Highnote sends a collaborative authorization request to your endpoint that contains transaction data. Fleet collaborative authorization requests contain a field called mastercardFleetData
or visaFleetData
depending on the network. You can configure your collaborative authorization flow to use this data in decisioning.
Note the following about fleet-specific collaborative authorization data:
null
if the payment card is not configured to prompt the cardholder or POS did not return fleet information in the authorization message.Note: For an overview of Visa product codes, see the Visa Fleet 2.0 Global Implementation Guide V1.2.
The following data is available for Visa fleet card products:
Field | Description | Possible values |
---|---|---|
visaFleetData.purchasetype | Indicates whether fuel or non-fuel items are included in the transaction | FUEL_PURCHASE , NON_FUEL_PURCHASE , MIXED , NOT_SPECIFIED |
visaFleetData.servicetype | Indicates whether the transactions took place at a self-service or full-service station | FULL_SERVICE , SELF_SERVICE , NOT_SPECIFIED |
visaFleetData.purchaseIdFormat | Indicates whether visaFleetData.purchaseId is an order or invoice number | |
visaFleetData.purchaseId | An alphanumeric value representing an order or invoice number provided by the cardholder | |
visaFleetData.fleetId | An alphanumeric value representing either a vehicle, driver, or generic ID provided by the cardholder | |
visaFleetData.odometer | The odometer value provided by the cardholder | |
visaFleetData.employeeNumber | An alphanumeric value representing the employee’s ID number | |
visaFleetData.trailerNumber | An alphanumeric value representing the trailer’s ID number | |
visaFleetData.customPrompt1 | An alphanumeric value representing the answer to a custom prompt | |
visaFleetData.customPrompt2 | An alphanumeric value representing the answer to a custom prompt | |
visaFleetData.nonFuelProductCodes | A list of non-fuel product codes for the products purchased | |
visaFleetData.purchaseRestrictonsFlag | Indicates whether the POS supports host-based restriction processing |
Note: For an overview of Mastercard prompt values and product codes, see the Mastercard Fleet Implementation Guide v4.
The following data is available for Mastercard fleet card products:
Field | Description |
---|---|
mastercardFleetData.driverId | An alphanumeric value representing a driver ID provided by the cardholder |
mastercardFleetData.vehicleId | An alphanumeric value representing a vehicle ID provided by the cardholder |
mastercardFleetData.prompts | A list of prompt codes and cardholder-entered values |
mastercardFleetData.fuelProducts | A list of fuel products purchased |
mastercardFleetData.nonFuelProducts | A list of non-fuel products purchased |
mastercardFleetData.spendControlOverrideFlag | Indicates whether the POS supports overriding the fleet spend controls on the card |
When you receive a collaborative authorization request for a fleet card product, the request body contains fleet-specific data you can use in decisioning. Each request body has network-specific visaFleetData
or mastercardFleetData
.
Note, some fields in a fleet collaborative authorization request body may be null
in the following scenarios:
The following payload is an example of a Visa fleet collaborative authorization request body:
The following payload is an example of a Mastercard fleet collaborative authorization request body:
To simulate collaborative authorization fleet data, you can use the fleet transaction simulator to simulate transactions in the test environment. For more information, see Simulate Fleet Transactions.