POS Systems

Fleet Card Acceptance at Your Station: Setup & Processing Guide

May 14, 2026|10 min read

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 in 2026.

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.

Network	Common Card Brands	Processing Network	Key Feature
WEX (Wright Express)	WEX Fleet, many private-label fleet cards	WEX Network	Largest independent fleet network; odometer + driver ID prompts
Voyager	Voyager Fleet Card, US Bank Voyager	Voyager Network (Mastercard)	Strong government and municipal fleet presence
Comdata	Comdata Fleet, Truckers Advantage	Comdata Network	Heavy trucking and OTR fleet focus
Mastercard Fleet	Various issuer-branded fleet cards	Mastercard	Runs on standard Mastercard rails with fleet data fields
Visa Fleet	Various issuer-branded fleet cards	Visa	Similar to Mastercard Fleet; Level 3 data required
FleetCor / Fuelman	Fuelman, Fleetwide	FleetCor Network	Restriction controls on product type and dollar limits

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 typically takes 5–15 business days. 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 Veeder-Root Passport POS is the most widely deployed forecourt controller in North America and has native fleet card support built in. Configuration is handled through the Passport Manager back-office interface:

Navigate to Store Operations → Payment → Fleet Card Setup
Enter your WEX Merchant ID and network endpoint (test vs. production)
Configure driver prompting sequences for each network (odometer, driver ID, vehicle number)
Set product restriction codes—these tell the network what grade of fuel or c-store items the card is authorized for
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 its Fleet Manager module. Fleet network parameters are configured under Configuration Client → Payment → Fleet Networks. Verifone’s implementation requires separate configuration of “Fleet Prompts” for each network, and odometer entry must be validated as a numeric field with a minimum digit count—typically 5 or 6 digits per WEX requirements.

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:

Driver ID — typically 4–6 digits assigned by the fleet manager
Odometer reading — must be a valid numeric entry; WEX validates that odometer readings are reasonable (not lower than a prior transaction)
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:

Driver ID or PIN
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 Voyager’s current specification document; Voyager updated their prompt specification in 2024 and some older POS versions still don’t handle exception prompts correctly.

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. Your POS must support Comdata’s “real-time authorization” model, which differs from standard EMV authorization flow. If you’re on a Gilbarco Passport, verify that your Comdata configuration uses the TCP/IP host connection, not the older dial-up fallback.

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.

Standard fuel product codes used across WEX, Voyager, and Comdata include:

001 — Regular unleaded
002 — Mid-grade unleaded
003 — Premium unleaded
019 — Diesel (on-road)
061 — DEF (diesel exhaust fluid)

If your POS transmits the wrong product code—say, it sends “001” 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

Visa Fleet and Mastercard Fleet cards require Level 3 transaction data—a richer data set than standard credit card transactions. This includes odometer, vehicle ID, driver ID, quantity of fuel, unit of measure, and product description. Transmitting Level 3 data correctly also qualifies your transactions for lower interchange rates. Without it, Visa/MC fleet transactions downgrade to a higher interchange tier, costing you margin on every transaction.

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 Encore 500 units with single-line displays may need a display board upgrade to properly render odometer entry prompts.

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—a common issue when drivers take more than 30 seconds between prompts.

Interchange Rates and Economics

What Fleet Cards Actually Cost You

Fleet card interchange is generally higher than standard consumer credit but the volume justifies it for most operators. Typical ranges in 2026:

Network	Typical Interchange Range	Notes
WEX	1.95%–2.40% + $0.05–$0.10	Varies by fleet account type
Voyager	1.75%–2.25% + flat fee	Government fleet accounts often lower
Comdata	2.00%–2.75%	Higher for trucking transactions
Visa/MC Fleet (Level 3)	1.80%–2.10%	Significant savings vs. downgrade rate of ~2.95%

Calculate your break-even by modeling your expected fleet volume against the interchange differential versus cash. At a 2.2% blended fleet interchange rate and $4.00/gallon fuel, you’re paying roughly $0.088 per gallon in processing fees. Many operators offset this with a small credit card surcharge program—check your state’s surcharging laws 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. A chargeback rate above 1% of fleet transactions should trigger an immediate POS configuration audit.

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. Outdoor EMV deadlines have passed for most networks, meaning unupgraded dispensers are fully liable for fraud losses 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

Audit your current POS and dispenser hardware — confirm Passport, Commander, or Wayne controller version and fleet card support status
Apply for WEX and Voyager merchant accounts — gather EIN, banking details, and hardware specs before applying
Obtain fleet-specific Merchant IDs from each network upon approval
Configure POS fleet card settings — enter MIDs, set up prompt sequences, map product codes to dispensers
Update dispenser firmware — verify current version supports each network’s latest prompt specification
Run test transactions using network-provided test cards before processing live fleet cards
Verify Level 3 data transmission for Visa/MC fleet cards to ensure correct interchange qualification
Confirm P2PE coverage includes fleet card data paths with your payment processor
Add your location to WEX, Voyager, and Comdata merchant locators
Set a monthly chargeback review cadence — log into merchant portals and review fleet dispute reports
Post fleet card acceptance decals at dispensers and station entrance
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—but stations that get the setup right consistently report fleet transactions becoming their highest-volume, most predictable revenue stream within the first quarter of acceptance.