Simulate Fleet Transactions

1. A Highnote Account
2. An API Key, the API Explorer, or the Dashboard
3. A Fleet Visa Card Product, Financial Account, and Payment Card

Before starting this guide, we recommend viewing Simulate Transactions in Test.

Transactions for Fleet Card Products include several elements not found in other Products, such as enhanced data processing during clearing and settling. Highnote provides a rich set of operations that allow you to simulate Fleet Transactions and ensure your integration is ready for production.

Highnote offers two types of authorization controls for Fleet Payment Cards:

• Controls baked into the EMV chip in the Physical Fleet Payment Cards
• Controls enforced through Spend Rules and Velocity Controls

For example, Highnote’s Fleet Cards have a product restriction code encoded into the EMV chip to allow fuel purchases and other approved products. The product restriction code may also prevent purchasing non-fleet items, such as food, at fuel stops.

Merchant Category Codes

Fleet Cards may be restricted to specific purchase types. In addition, you may also restrict purchases, such as meals purchased through DoorDash, via MCC-based Spend Control Rules.

Refer to the following product restriction types for Visa and Mastercard:

Visa

• Open, No Restrictions (Fuel, Maintenance, and Non-Fuel)
• Fleet (Fuel and Maintenance Only)
• Fuel Only

Mastercard

• Open, No Restrictions (Fuel, Maintenance, and Non-Fuel)
• Fuel Only

All Fleet Cards must accept Fleet/Fuel MCCs and can optionally accept Maintenance MCCs:

Fleet/Fuel MCCs

Maintenance MCCs

Use the following query to simulate a Fleet Authorization with Visa:

Use the following query to simulate a Fleet Authorization with Mastercard:

The full transaction amount may not be known at authorization for an Automated Fuel Dispenser purchase. Instead, a $1 or estimated amount is sent for authorization, requiring Authorization Advice to be sent to confirm the total amount later. The Authorization Advice amount replaces the original Authorization amount. For example, automated fuel dispensers (AFDs) often charge a $1 Authorization at the time of purchase. A few hours after the cardholder completes fueling, Authorization Advice is sent to confirm the total transaction amount.

Simulating Authorization Advice is optional. Visa supports a Real-Time Clearing program, which does not require Authorization Advice. Skip simulating Authorization Advice in the following scenarios:

• Simulating a Real-Time Clearing event
• Simulating an in-store pre-pay transaction
• Simulating a transaction where the merchant incorrectly did not send Authorization Advice

Use the following mutation to simulate Authorization Advice with Visa in your Test Environment:

Use the following query to simulate Authorization Advice with Mastercard in your Test Environment:

Fleet transactions follow the standard authorization and clearing data flow of all card payments and include ancillary information specific to the fleet vertical via specialized clearing messages. The payment networks outline three levels of data for fleet transactions, but they provide the data at different times during the transaction lifecycle. Depending on your Card Product's payment network, your system will receive and interact with the Level 2 and Level 3 data.

Level 1

Contains standard payment network transaction data provided by merchants. This data includes:

• Merchant details
• Point of Service details
• Billing zip code
• Total purchase amount
• Purchase date

Level 1 data is the same for all transaction types and merchants. No Enhanced Data is captured or provided at this level.

Level 2

Contains Enhanced Data captured at the point of sale and sent with the transaction. Level 2 data is always sent at the time a transaction clears. Level 2 transactions have different MCCs based on whether the Payment Card is used at an Automated Fuel Dispenser or in-store:

• Automated Fuel Dispenser: 5542
• In-store: 5541

The full transaction amount may not be known at authorization when Level 2 data is sent for an Automated Fuel Dispenser purchase. Instead, a $1 or estimated amount is sent for authorization, requiring Authorization Advice to be sent to confirm the total amount later.

Refer to the API Reference for more information on Visa Level 2 Purchase Data Fields.

Visa sends Level 1 and Level 2 data together with the Clearing event. Use the following mutation to simulate Clearing with Visa in your Test Environment:

Mastercard sends Level 1 data only in the Clearing event. Use the following query to simulate a Clearing with Mastercard in your Test Environment:

Level 3 transactions have different MCCs based on whether the Payment Card is used at an Automated Fuel Dispenser or in-store:

• Automated Fuel Dispenser: 5542
• In-store: 5541

The full transaction amount may not be known at authorization when Level 3 data is sent for an Automated Fuel Dispenser purchase. Instead, a $1 or estimated amount is sent for authorization, requiring Authorization Advice to be sent to confirm the total amount at a later time.

You can set up a Notification Event to alert you when Level 3 Data has been added to a transaction.

Visa Level 3 Data contains more detailed data for a transaction and is generally used to send specifics for non-fuel products and services. The data is sent anywhere from 24-48 hours after the transaction. Merchants are not required to report enhanced data for fuel-only transactions. Level 3 Data typically follows an invoice structure with invoice summary information and invoice line item detail information.

Refer to the API Reference for more information on Visa Level 3 Enhanced Data Fields.

Use the following mutation to simulate Visa Fleet Enhanced Data:

Mastercard Level 2 and Level 3 Data contains detailed data for a transaction and is generally used to send specifics for non-fuel products and services. The data is sent at the end of the business day (EST). Level 3 Data typically follows an invoice structure with invoice summary information and invoice line item detail information.

Refer to the API Reference for more information on Mastercard Enhanced Data Fields.

Use the following mutation to simulate Mastercard Fleet Enhanced Data: