Fleet Card Acceptance at Your Station: Setup & Processing Guide

Why Fleet Card Acceptance Is Worth the Setup Investment

Fleet cards represent some of the most predictable, high-volume fuel transactions in the retail fuel business. Commercial fleets—delivery companies, contractors, municipalities, school districts—need consistent fueling locations, and they’ll drive past competitors to use a card their fleet manager has already authorized. Accepting WEX fleet cards, Voyager, Mastercard Fleet, Comdata, and similar products can add thousands of gallons per month to your volume without a single cent of marketing spend.

But fleet card acceptance isn’t as simple as enabling a new card type on your terminal. Each network has specific driver prompting requirements, odometer capture rules, and product restriction logic that must be configured at both the point-of-sale (POS) controller and the dispenser level. Get it wrong and you’ll face chargebacks, network fines, or disqualification from the program entirely.

This guide walks you through the enrollment process, hardware and software configuration, driver prompting sequences, and ongoing compliance obligations for the major fleet card networks operating.

Understanding Fleet Card Networks: The Major Players

Not all fleet cards are equal. They operate on different networks with different technical requirements, and your POS system must be able to communicate with each one separately.

WEX and Voyager are the two networks you’ll encounter most frequently at independent and dealer-operated stations. Getting Voyager fleet card gas station acceptance enabled—alongside WEX—covers the vast majority of commercial fleet cards your customers are likely to carry.

Step 1: Network Enrollment and Merchant Agreement

Applying Directly vs. Through Your Payment Processor

You can pursue fleet card network enrollment in two ways:

• Direct enrollment with WEX, Voyager, or Comdata as a merchant. This often yields better interchange rates but requires separate contracts with each network.
• Through your existing payment processor (e.g., Heartland, Worldpay, Elavon). Many processors have existing relationships with fleet networks and can bundle enrollment. Convenience comes at slightly higher fees.

For WEX specifically, visit the WEX Merchant Services portal and complete a Merchant Location Agreement. You’ll need your station’s EIN, banking information, and your dispenser/POS make and model to confirm compatibility before approval.

What to Expect During Underwriting

Fleet networks will review your station’s transaction history, business license, and sometimes your branded supply agreement. Approval timelines are not published and vary by network and by how complete your application is—ask each network for its current turnaround in writing. Once approved, you receive a Merchant ID (MID) specific to each fleet network—this must be programmed into your POS system separately from your standard credit card MID.

Step 2: POS System Configuration

Gilbarco Veeder-Root Passport

The Gilbarco Passport POS is a widely deployed forecourt controller in North America and supports fleet card acceptance through its payment network configuration. Configuration is handled through the Manager Workstation (MWS) back-office interface:

1. Navigate to MWS > Set Up > Network and select your payment network
2. Enter your WEX Merchant ID and network endpoint (test vs. production)
3. Configure driver prompting sequences for each network (odometer, driver ID, vehicle number)
4. Set product restriction codes—these tell the network what grade of fuel or c-store items the card is authorized for
5. Run a test transaction using WEX or Voyager’s provided test card numbers before going live

Verifone Commander

The Verifone Commander site controller supports fleet cards through Commander Fleet, an add-on to the existing Commander site controller. Verifone states that Commander Fleet currently supports WEX and Comdata — the two networks it names as the largest U.S. commercial fleet card networks — with additional networks planned; fleet network parameters and per-network prompts are configured in the Commander Configuration Client. Confirm the exact prompt field rules, including any minimum digit counts, against the current specification each network gives you, because those specifications are not published.

Dover/Wayne iX Pay and Ovation Dispensers

Wayne Ovation dispensers with iX Pay integrated terminals handle fleet prompting directly at the dispenser. Configuration is pushed from the site controller, but verify that your Wayne dispenser firmware is current—fleet card prompt changes from WEX and Voyager are frequently delivered via firmware updates. An out-of-date firmware version is a common cause of fleet card declines at the dispenser.

Step 3: Driver Prompting Requirements

This is where most fleet card setups go wrong. Each network specifies exactly what information must be captured from the driver at the pump, and missing or incorrectly formatted prompts will cause the transaction to decline or generate a chargeback.

WEX Fleet Card Prompting Sequence

Standard WEX transactions require the following prompts in this order:

1. Driver ID — assigned by the fleet manager; WEX does not publish the field length, so take it from the specification WEX gives you
2. Odometer reading — must be a valid numeric entry; WEX validates that odometer readings are reasonable (not lower than a prior transaction)
3. Vehicle number — required on some fleet accounts, optional on others

WEX uses what it calls a “prompt set” assigned per card. Some fleet managers configure cards to require all three prompts; others waive odometer. Your POS must dynamically respond to the prompt set returned by WEX’s authorization system during the pre-authorization call—this is handled automatically in properly configured Passport and Commander systems.

Voyager Prompting Sequence

Voyager fleet card transactions at a gas station typically require:

1. Driver ID or PIN
2. Odometer (required for most commercial accounts)

Voyager also supports “exception prompting”—where additional data fields are triggered based on the card’s authorization profile. Ensure your POS firmware supports the current Voyager specification; U.S. Bank issues Voyager merchant rules and specifications to enrolled merchants rather than publishing them, so request the current version from the Voyager merchant program directly.

Comdata and Trucking-Specific Cards

Comdata cards are common at truck stops and high-volume diesel sites. They add complexity because many Comdata transactions are pre-authorized remotely by fleet dispatchers. Comdata does not publish a merchant-facing specification for its authorization flow, so confirm with Comdata and with your POS vendor which Comdata transaction types your site controller is certified for and how the host connection must be configured.

Step 4: Product Restriction and Level 3 Data

Product Codes and Restriction Logic

Fleet cards can restrict purchases to specific product types. A delivery company might authorize only diesel and DEF; a landscaping fleet might allow only regular unleaded. Your POS must transmit the correct product code with every fleet transaction so the network can validate it against the card’s authorized product list.

Product code values are not standardized across networks — each network issues its own code list to accepting merchants — so map your grades from the code table the network gives you rather than from a generic list.

If your POS transmits the wrong product code—say, it reports unleaded when a customer pumped diesel—the transaction may approve but will generate a chargeback when the fleet manager audits their statement. This is a configuration issue in your dispenser-to-POS product mapping.

Level 3 Data Requirements

Enhanced fleet data — commonly called Level III — is a richer data set than a standard credit card transaction, covering fields such as odometer, vehicle ID, driver ID, fuel quantity, unit of measure and product description. It is not a Visa/Mastercard-only requirement: WEX states that it “requires Level III data transmission capability of all of its accepting merchants,” and Visa requires merchants that accept a Visa Fleet card to supply enhanced data for transactions in the covered fuel merchant category codes. Qualification matters to your cost, because transactions that fail to qualify fall to Visa’s Non-Qualified interchange program instead of the commercial fuel program — see the cost section below.

Step 5: Dispenser-Level Configuration

Fleet card configuration doesn’t end at the POS. Your dispensers must also be correctly configured to present prompts on the dispenser display and keypad. For Gilbarco Encore dispensers, fleet prompting is controlled by the Passport controller, but the dispenser’s display firmware must support multi-line prompt screens. Older dispenser display hardware may not render multi-line prompts; confirm the prompt-display capability of your specific dispenser model and display board with Gilbarco before assuming it can handle fleet prompting.

For Wayne Ovation dispensers, fleet prompts are rendered on the iX Pay terminal screen. Verify that the iX Pay terminal’s idle screen timeout doesn’t interrupt a driver mid-prompt sequence—the timeout value is set in your terminal configuration, so check yours rather than assuming a default.

Fleet Card Processing Costs

What Fleet Cards Actually Cost You

What fleet acceptance costs you depends on which network the card runs on. WEX, Voyager and Comdata are closed-loop networks: they do not publish merchant discount rates, and what you pay is set in the merchant agreement you negotiate with the network or with the processor that bundles it. Visa and Mastercard do publish their U.S. interchange schedules. On Visa’s schedule effective April 18, 2026, the Purchasing and Corporate T&E table — which Visa footnotes as including Fleet cards — shows Commercial Level II – Fuel at 2.20% + $0.10 and Non-Qualified at 2.95% + $0.10.

Because the closed-loop rates are negotiated, get the terms in writing before you sign: the discount rate or per-transaction fee and how it is calculated, whether it is a percentage, a cents-per-gallon amount or both, any monthly or per-terminal software fee, the settlement and funding schedule, and the conditions under which a transaction can be charged back. Then model your expected fleet volume against those terms. Many operators offset card costs with a credit card surcharge program—check your state’s surcharging laws and the card network rules before implementing.

Chargebacks: Common Causes and Prevention

Fleet card chargebacks are more structured than consumer card disputes. The most frequent causes:

• Missing or invalid driver prompts — transaction approved but required data wasn’t captured
• Wrong product code transmitted — mismatch between what was pumped and what was reported
• Odometer rollback — submitted odometer is lower than the card’s prior transaction record
• Exceeding velocity limits — multiple transactions on the same card within a restricted timeframe
• Authorization timeout — pump completed a transaction after the authorization window expired

Review your fleet card chargeback reports monthly. Both WEX and Voyager provide merchant portals with chargeback detail. The networks do not publish a chargeback-rate threshold for fleet merchants, so treat any month-over-month rise in fleet chargebacks — not a fixed percentage — as the trigger for a POS configuration audit, and ask your network what ratio puts your account at risk.

Compliance and Security Considerations

PCI DSS Scope for Fleet Cards

Fleet card transactions are in scope for PCI DSS compliance just like standard credit cards. Your annual PCI Self-Assessment Questionnaire (SAQ) must cover fleet card processing. If you’re using a Gilbarco Passport or Verifone Commander with a validated point-to-point encryption (P2PE) solution, your SAQ scope is significantly reduced—but only if fleet card data also flows through the P2PE path. Confirm this with your payment processor; some older fleet network integrations bypass P2PE and reintroduce scope.

EMV Liability for Fleet Cards

The EMV liability shift applies to fleet cards as well as consumer cards. If a fraudulent fleet card transaction occurs at a non-EMV capable dispenser, the liability falls on you as the merchant. Many WEX and Voyager cards are now chip-enabled; your dispensers must be EMV-capable and properly configured for chip reads. The automated fuel dispenser EMV liability shift took effect on April 17, 2021 for Visa (April 16, 2021 for Mastercard), so a dispenser that still cannot read chip cards carries the counterfeit-fraud liability today.

Marketing Your Fleet Card Acceptance

Once you’re live, tell the market. Post WEX, Voyager, and Comdata acceptance decals at your dispensers and entrance. Add your location to each network’s merchant locator—this is a separate step from enrollment. WEX’s merchant locator is particularly important because fleet managers use it to identify approved fueling locations for their drivers. Submit your location data (address, hours, accepted cards, diesel availability) directly through the WEX Merchant Portal. Voyager has a similar process through their network operations team.

Consider reaching out directly to local fleet managers—construction companies, delivery services, municipalities—to inform them your station accepts their card. This kind of direct outreach is how independent operators build loyal fleet volume without competing on price alone. Your loyalty and commercial account strategy should treat fleet card acceptance as a foundation, not an afterthought.

Action Items: Fleet Card Acceptance Checklist

1. Audit your current POS and dispenser hardware — confirm Passport, Commander, or Wayne controller version and fleet card support status
2. Apply for WEX and Voyager merchant accounts — gather EIN, banking details, and hardware specs before applying
3. Obtain fleet-specific Merchant IDs from each network upon approval
4. Configure POS fleet card settings — enter MIDs, set up prompt sequences, map product codes to dispensers
5. Update dispenser firmware — verify current version supports each network’s latest prompt specification
6. Run test transactions using network-provided test cards before processing live fleet cards
7. Verify Level 3 data transmission for Visa/MC fleet cards to ensure correct interchange qualification
8. Confirm P2PE coverage includes fleet card data paths with your payment processor
9. Add your location to WEX, Voyager, and Comdata merchant locators
10. Set a monthly chargeback review cadence — log into merchant portals and review fleet dispute reports
11. Post fleet card acceptance decals at dispensers and station entrance
12. Contact local fleet managers to inform them of your acceptance capability

Fleet card acceptance is one of the few initiatives in fuel retail that simultaneously increases volume, improves customer retention, and requires zero consumer marketing spend. The upfront configuration investment is real, and how much volume it returns depends on how much commercial traffic already passes your site.

Sources

Figures and citations in this article were checked against the following primary sources on 2026-09-07.

• Visa U.S.A. Interchange Reimbursement Fees, effective 18 April 2026
• Visa: U.S. Automated Fuel Dispenser EMV Liability Shift
• Visa: U.S. Fleet Program Enhancements, New Support Requirements and Visa Rules Update
• WEX: Level III data — a fleet manager's fundamental tool (merchant/partner material)
• U.S. Bank: Voyager Fleet Card / Voyager Mastercard
• U.S. Bank: Merchant Fleet Management (Voyager Network merchant program)
• Comdata (Corpay): Comdata Connect Card
• Corpay: FLEETCOR announces rebranding to Corpay (effective 25 March 2024)
• Verifone: Commander Fleet product page
• Gilbarco MDE-5550B Passport V20 Network Addendum (Manager Workstation / MWS menu paths)
• Phase 3 reviewer brief (basis for removing unsourced figures)