> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/fleet-cards-commander-fleet.md). # Fleet Cards - Commander Fleet ### Revision History

Date	Description
03/09/2026	Initial Release
03/17/2026	Updated Requirements section.
07/04/2026	Commander Fleet - Self-Enrollment
07/29/2026	Added MNSP details

## Overview ### Feature Description This feature implements a Verifone direct connection to WEX and Comdata allowing Verifone Commander to process Commercial Fleet transactions directly with WEX and Comdata. {% hint style="info" %} *For this feature to work, the Verifone Commander should be on-boarded to* Commander Central *and a license should be bought from Verifone.* {% endhint %} {% hint style="info" %} ***Very Important**: Refer to the F*[*leet Cards General Fuel Configuration & Usage Reference*](/feature-references/features-and-products-references/fleet-cards-general-fuel-configuration-and-usage.md) *for more information on the general fuel configuration to implement commercial fleet cards for all FEPs. Fuel configuration should be set up first before configuring this feature, for the feature to work.* {% endhint %} *The Fleet Cards General Fuel Configuration & Usage Reference also has examples of how the fleet cards work at commercial sites.* ### Supported Hardware Requirements * Commander Site Controller with C18 * Commander Site Controller base version 56.02 and higher. * Payment PIN pad(s) * Wayne DCRs need updated firmware to display the new secure prompts. * Gilbarco DCRs may need updated firmware to support the SPOT protocol. * Bennett and Invenco DCRs may need updated firmware. * Any IP enabled DCR with graphic keys or onscreen keyboard is supported. If no graphic keypads are present on the DCR, the customer will be sent inside to complete the sale. ### Comdata Cards | | **Comdata MC** | **Comdata On Road** | **Comdata Proprietary Fuel Card** | | -------------------- | ----------------- | ------------------- | --------------------------------- | | **Bin Range** | 556735 | 556736 | 560017 | | **Multi-Purpose** | Comdata/ MC | Comdata/ MC | Comdata only | | **Fueling position** | Retail/Commercial | Retail/Commercial | Commercial | | **Type** | MSR | EMV | MSR | ### WEX HeavyFleet Cards | **Card Type** | **Bin** | **FD Card Type / Check Svc Provider** | | ---------------------- | ---------- | ------------------------------------- | | TCH Fuel | 708305 | WEXOTR | | T-Check Fuel | 600296 | WEXOTR | | EFS-TS | 589355 | WEXOTR | | EFS LLC Fuel | 707152 | WEXOTR | | EFS MasterCard | 556748 | WEXOTR | | EFS MasterCard Payroll | 530757 | WEXOTR | | Fleet One | 501486 | WEXOTR | | Cross Road | 6900460456 | WEXOTR | | Paper Check | N/A | MONEYCODE | ### Comdata Fuel Codes to NACS Code Mapping The following fuel products can be configured in the fuel products form from **Configuration Client > Forecourt > Fuel > Fuel Config > Fuel Products** to be used with Comdata cards. NACS Code are converted to the following Comdata codes. {% hint style="info" %} Refer to the *Fleet Cards General Fuel Configuration & Usage Reference.* {% endhint %}


Comdata Code	NACS Code
#1 Diesel 019	021, 063, 300, 305
#2 Diesel 053	019, 020, 045-056, 060, 061, 067, 068, 069, 070, 231, 324, 339, 342
Reefer 056	032, 033, 034, 306, 307, 311-320, 333-338
DEF 819	062

### Comdata Non Fuel Codes to NACS Code Mapping The following non fuel products can be configured in the PLU form from **Configuration Client > Store Operations > PLUs**to be used with Comdata cards. NACS Code are converted to the following Comdata codes.

Comdata Code	NACS Code
Comdata Code	NACS Code	Description
00	138\|603
01	132\|652
02	116\|117
03	101\|104\|128\|137
04	109
06	133
07	119\|130\|131\|140	Parts
10	102\|136\|655\|654\|660	VEHICLE (TRUCK) WASH
11	650	SCALES
12	135	Truck Parking
13	653	Hotel
14	no NACS code	Regulatory


15	115	Labor
16	420\|421\|422\|423\|424\|425\|426\|427\|428\|429\|430\|431\|43 2\|433\|434\|435\|436\|437\|438\|439\|440\|441\|442\|443\|444\| 445\|446\|447\|448\|449\|450\|451\|452\|453\|454\|455\|456\|45 7\|458\|459\|460\|461\|462\|463\|464\|465\|466\|467\|468\|469 \|470\|471\|472\|473\|474\|475\|478\|479	Grocery
17	651	Shower
18	149	Trip Scan
19	659	TOLLS
20	186\|187\|188	Aviation
21	120	Vehicle Maintenance
22	180	Aviation Maintenance
23	105	Setup fee
24	600	DEF Package
25	107	Wiper Fluid
26	no NACS code	EReceipt
27	650	CAT Scale
28	175	Storage Fee
29	101\|104\|128\|137	Retail Lubricant
32	106	Coolant/Anti Freeze
33	605	Bottled Propane
CADV	955\|956

### WEX Fuel Codes to NACS Code Mapping The following fuel products can be configured in the fuel products form from **Configuration Client > Forecourt > Fuel > Fuel Config > Fuel Products**to be used with WEX cards. NACS Code are converted to the following Comdata codes.

NACS Code	WEX Code
021 \| 063	1
032 \| 317 \| 319	1
001 \| 011 \| 026 \| 042	4
325	4
345	4
344	4
002 \| 012 \| 015 \| 039 \| 043	8
326	8
003 \| 013 \| 040 \| 044	16
327	16
023	32
346	32
347	32
300 \| 305 \| 306 \| 307	64
348	128
304	128
045 \| 046 \| 047 \| 048 \| 049 \| 050 \| 051 \| 052 \| 055 \| 056	256
311 \| 312 \| 313 \| 314 \| 315 \| 316 \| 333 \| 334 \| 335 \| 336 \| 337 \| 338	256
358	1024
064 \| 065 \| 066 \| 322	2048
303	4096
019 \| 020 \| 053 \| 054 \| 324	8192
033 \| 318 \| 320	8192
351	8192
151	16384

NACS Code	WEX Code
302	2097152
062	4194304
022	8388608
024	16777216
331	134217728
332	268435456
032 \| 033 \| 304 \| 317 \| 318 \| 319 \| 320 \| 311 \| 312 \| 313 \| 314 \| 315 \| 316 \| 333 \| 334 \| 335 \| 336 \| 337 \| 338	RFR

### WEX Non Fuel Codes to NACS Code Mapping The following non fuel products can be configured in the PLU form from **Configuration Client > Store Operations > PLUs** to be used with WEX cards. NACS Code are converted to the following Comdata codes.

NACS Code	WEX Code
100 \| 110 \| 111 \| 112 \| 121 \| 127 \| 129 \| 134 \| 139 \| 143 \| 144 \| 145 \| 146 \| 147 \| 148 \| 149 \| 175 \| 176 \| 177 \| 178 \| 179 \| 180 \| 181 \| 182 \| 183 \| 184 \| 185 \| 186 \| 187 \| 188 \| 189 \| 190 \| 191 \| 192 \| 194 \| 195 \| 196 \| 197 \| 198 \| 199 \| 200 \| 203 \| 204 \| 205 \| 208 \| 209 \| 210 \| 211 \| 212 \| 213 \| 224 \| 250 \| 251 \| 252 \| 253 \| 254 \| 299 \| 308 \| 309 \| 310 \| 400 \| 401 \| 402 \| 403 \| 404 \| 405 \| 406 \| 407 \| 408 \| 409 \| 520 \| 521 \| 522 \| 523 \| 524 \| 525 \| 526 \| 527 \| 528 \| 529 \| 530 \| 531 \| 532 \| 533 \| 534 \| 535 \| 536 \| 537 \| 538 \| 539 \| 540 \| 541 \| 542 \| 543 \| 544 \| 545 \| 546 \| 547 \| 548 \| 549 \| 550 \| 551 \| 552 \| 553 \| 554 \| 555 \| 556 \| 557 \| 558 \| 559 \| 560 \| 561 \| 562 \| 563 \| 564 \| 565 \| 566 \| 568 \| 569 \| 570 \| 571 \| 572 \| 574 \| 575 \| 624 \| 656 \| 657 \| 957 \| 958 \| 959 \| 960 \| 961 \| 971 \| 972 \| 973 \| 999	MERC
118	ACCE
605	BPRP
101 \| 104 \| 128 \| 137	OIL
103	OILC
102 \| 136 \| 655	WASH
500	REST
659	TOLL
600	DEF
193	FAX

NACS Code	WEX Code
567	PHON
573	IDLE
600	UREA
105	LMPR
106	ANFR
107	WWFL
604	KERO
138 \| 201 \| 206 \| 603	ADD
109	TIRE
650	SCLE
117 \| 120 \| 122 \| 123 \| 125 \| 126 \| 133 \| 141 \| 142 \| 658 \| 660 \| 661 \| 662 \| 663 \| 664 \| 665 \| 666 \| 667 \| 668 \| 669 \| 670 \| 671 \| 672 \| 673 \| 674 \| 675 \| 676 \| 677 \| 678 \| 679 \| 680 \| 681 \| 682 \| 683 \| 684 \| 685 \| 686 \| 687 \| 688 \| 689 \| 690 \| 691 \| 692 \| 693 \| 694 \| 695 \| 696 \| 697 \| 698 \| 699	REPR
119 \| 130 \| 131 \| 140 \| 202	PART
124	BRAK
132 \| 652	RECP
135	PARK
653	HOTEL
420–479 (many codes listed)	GROC
490–499	DELI
651	SHWR
115	LABR
900–909	DISC
905–909	COUP
913	SPLT
116	TRAL
950–970 (several listed)	STAX
955 \| 956	CADV

{% hint style="info" %} *Some of these NACS codes that are common for both Comdata and WEX, if configured for one and not for the other will be routed to the correct network depending on the card used.* {% endhint %} ## Configuring Fleet Cards for Direct Connect ### Configuring Fleet Cards {% hint style="info" %} **Very Important**: Refer to the [**Fleet Cards General Fuel Configuration Reference**](/feature-references/features-and-products-references/fleet-cards-general-fuel-configuration-and-usage.md) for more information on the general fuel configuration to implement commercial fleet cards for all FEPs. {% endhint %} {% hint style="warning" %} **Configurations can be done even without a license for the feature. But, for the feature to work, get a license from Verifone.** {% endhint %} ### Commander Fleet - Self-Enrollment Previously, signing up for Commander Fleet required manual coordination with Verifone support, which could take days. With this feature, you can subscribe your site to Commander Fleet yourself directly from Commander Central. The entire process — selecting your site, entering payment details, and activating the service — is completed online in a few minutes. Once your subscription is confirmed, Commander Fleet is activated on your Commander automatically. #### Before You Start Please confirm the following before beginning enrollment. You will also see these listed in the sign-up panel inside Commander Central.

Requirement	What to Check
Commander Software Version	Your site must be running Commander version 56.02 or higher.
Commander Central Access	You must have an active Commander Central account with access to the site you want to enroll.
Network Connectivity	Your site must have active IP/network connectivity between the Commander and the DCR/Dispensers.
Site Hardware	Your site hardware must support fleet transactions, including key entry via alphanumeric or on-screen keyboards where required.
Fleet Card Credentials (MID)	You need a Merchant ID (MID) from each fleet card provider you will accept (WEX, Comdata, or both). If you already have a MID, notify your provider that you intend to use Commander Fleet before activating.
MNSP Connectivity	Contact your Managed Network Service Provider (MNSP) to confirm fleet connectivity is enabled at your site before activating.

#### How to Enroll — Step by Step

Steps	Instructions
1	Log in to Commander Central Go to Commander Central and sign in with your account credentials.
2	Open Commander Fleet Select Commander Fleet from the left-hand navigation sidebar.
3	Find your site Review the list of sites. Sites that are ready to enroll will display a Sign Up button.
4	Click Sign Up Click the Sign Up button next to the site you want to enroll. If your site shows that it is not eligible for Commercial Fleet see the FAQ section to resolve.
5	Review prerequisites A panel will appear listing the prerequisites. Confirm your site meets all of them before continuing.
6	Complete payment You will be taken to a secure 2Checkout payment screen. Enter your billing and payment details. Commander Fleet billing is monthly and renews automatically.
7	Wait for activation After payment, the site status changes to Inactive. This is normal — the system is processing your subscription. This usually completes within a few minutes.
8	Activation is automatic After the subscription is confirmed, Commander Fleet is activated on your Commander with no further action needed from you.

#### Understanding Site Statuses The Commander Fleet page displays a status for each of your sites. Here is what each status means:

Status	What It Means
Sign Up Available	This site is eligible for Commander Fleet and is ready to enroll. Click Sign Up to begin.
Inactive	Payment has been completed and the subscription is being processed. No action needed — activation will happen automatically once confirmed.
Active	Commander Fleet is enrolled and running at this site.
Ineligible	This site cannot enroll at this time. This is usually due to an incomplete billing address or no active Advanced Support & Maintenance (ASM) contract. See the FAQ section for steps to resolve.

#### Billing * Billing is handled through 2Checkout, a secure third-party payment processor. * Charges are monthly and renew automatically. * Renewal confirmation emails are sent directly from 2Checkout. Verify the monthly amount shown matches your agreed rate. * If you have questions about a charge, contact Verifone support and reference your Commander Central account and site ID. #### Frequently Asked Questions - Read Before Applying or Configuring **Can I enroll multiple sites at once?** Each site is enrolled individually by clicking the Sign Up button next to that site on the Commander Fleet page. **What happens immediately after I complete payment?** The site status changes to Inactive while Commander Central verifies your subscription with the licensing system. Once the license is confirmed — typically within a few minutes — Commander Fleet is automatically activated on the Commander at that site. You do not need to do anything further. **Do I need to configure anything on the Commander after signing up?** No. Activation is fully automatic once the subscription is confirmed. No manual steps are required on the Commander itself. **My site shows Ineligible. What should I do?** Check two things: * Make sure the site’s billing address is fully filled in under the site settings in Commander Central. * Confirm the site has an active Advanced Support & Maintenance (ASM) contract. If both are in order and the site still shows Ineligible, contact Verifone support. **Where do I get fleet card credentials (MID)?** Contact your fleet card provider directly — WEX, Comdata, or both — to obtain a Merchant ID (MID) for your site. If you already have a MID with that provider, notify them before you activate Commander Fleet so they can enable fleet processing for your account. **What is an MNSP and why do I need to contact them?** Your Managed Network Service Provider (MNSP) manages the network connection between your site and payment hosts. You need to notify them that you are enabling fleet card processing so they can confirm the correct connectivity is in place before you activate. ### Comdata Configuration Configure Comdata configuration in Commander Central from **Payment Operations > Commander Fleet > Providers > Comdata**.

1. Get the MID will from Comdata. ComData MID: 5-6 digit alphanumeric, starts with the state code (e.g NY, FL, WY) and then has numbers after. 2. Reference the [MNSP Details](#mnsp-details) below for the network configuration, if details are not present for your MNSP, contact your provider. ### WEX-OTR Configuration Configure WEX-OTR configuration in Commander Central from **Payment Operations > Commander Fleet > Providers > WEX-OTR**.

1. Get the MID will from WEX-OTR. WEX Mid: 6 digit number, starts with 5, might also be listed as the TCH number. 2. Reference the [MNSP Details](#mnsp-details) below for the network configuration, if details are not present for your MNSP, contact your provider. ### MNSP Details

Fleet Cards	MNSPs
Wex and Comdata	Acumera, Mako, Cybera, Control Scan
WEX only	SageNet
Fleet Support in Progress	TNS
Not Yet Validated	11:11 Systems, AvaLan, Comcast, Hughes, Omega, WESCO, Quality Oil

#### **MNSP: Sage Net** {% columns %} {% column %} **WEX-OTR** **IP/Domain:** Contact the MNSP **Port:** Contact the MNSP **TLS:** Contact the MNSP {% endcolumn %} {% column %} **Comdata** Not Yet Supported {% endcolumn %} {% endcolumns %} #### MNSP: Control Scan {% columns %} {% column %} **WEX-OTR** **IP/Domain:** Contact the MNSP **Port:** Contact the MNSP **TLS:** Contact the MNSP {% endcolumn %} {% column %} **Comdata** **IP/Domain:** Contact the MNSP **Port:** Contact the MNSP **TLS:** Contact the MNSP {% endcolumn %} {% endcolumns %} #### MNSP: Paysafe {% columns %} {% column %} **WEX-OTR** **IP/Domain:** gw\.otr.wexinc.com **Port:** 8030 **TLS:** Enabled {% endcolumn %} {% column %} **Comdata** **IP/Domain:** cdn-east.echosat.net **Port:** 443 **TLS:** Enabled {% endcolumn %} {% endcolumns %} #### MNSP: Cybera {% columns %} {% column %} **WEX-OTR** **IP/Domain:** 208.64.196.225 **Port:** 8030 **TLS:** Enabled {% endcolumn %} {% column %} **Comdata** **IP/Domain:** 64.27.74.60 **Port:** 443 **TLS:** Enabled {% endcolumn %} {% endcolumns %} #### MNSP: Mako {% columns %} {% column %} **WEX-OTR** **IP/Domain:** 208.64.196.225 **Port:** 8030 **TLS:** Enabled {% endcolumn %} {% column %} **Comdata** **IP/Domain:** 10.1.254.200 **Port:** 5003 **TLS:** Disabled {% endcolumn %} {% endcolumns %} ### General Fleet Settings Configure Comdata configuration in Commander Central from **Payment Operations > Commercial Fleet > General Settings**.

{% stepper %} {% step %} Enable Cash Advance {% endstep %} {% step %} Enter cash advance limit. {% hint style="info" %} *There are three ways the cash advance limit is set:* • Using the Cashback Amount field in Cashback Prompt Amounts section from **Configuration Client > EPS Configuration > Buypass Configuration** • From the host response that comes during the pre-authorization response • From the DCT table. *Out of these three, the cash advance that appears to the customer is the lowest one. Cash advance is only given after fueling.* {% endhint %} {% endstep %} {% step %} Select the fuel grade for diesel that has been configured in **Configuration Client > Forecourt > Fuel > Fuel Config > Fuel Products** {% hint style="info" %} See the Fleet Cards Fuel Configuration & Usage Reference for more Fuel Configuration information. {% endhint %}

{% endstep %} {% endstepper %} ## REPORTING ### Exception Report The Exception Report shows failed transaction. It is available at **Network Manager > EPS Secure Report > TWEX-OTR and 13. Comdata Reports > Exception Report**. The EPS prompts for the terminal batch number. If zero is entered, the EPS prints the current open terminal batch.

#### Report Details • TITLE: Terminal Day Summary Report. • Agent ID: Agent who performed the transaction. • DATE / TIME: Date and time the report printed. **Result: Failure** • Amount: Failure Amount • Account Number: Masked account number. ### Back Office Reports The following are the back office reports for Comdata and WEX * ComdataNetworkBatchDetail * ComdataTerminalBatchSummary * ComdataExceptionDetails * WEX-OTRNetworkBatchDetail * WEX-OTRTerminalBatchSummary * WEX-OTRExceptionDetailsc- ## Troubleshooting If facing any issues with the feature, go through this list: {% stepper %} {% step %} The FEPTable is controlled by Verifone Commander Central and will be overwritten if the files are edited manually on commander. {% endstep %} {% step %} The Feps do not show online on Verifone EPS until after the 1st transaction is completed. {% endstep %} {% step %} Make sure commander has DNS enabled from **Configuration Client > Initial Setup> Local Area Network Settings** and that the host URL can be resolved correctly with the following command: ping google.com {% endstep %} {% step %} Acumera had an issue that was not allowing traffic to egress out from Verifone Commander to the Comdata host. Use these commands from a putty connection on commander to verify hosts are reachable. If these commands fail and timeout verify with Acumera the rule is in place to allow this traffic. **Comdata test -** Openssl s\_client -connect 10.1.254.200:5003 **WEX-OTR test -** Openssl s\_client -connect 208.64.196.225:8030 {% endstep %} {% step %} Verify site is using correct Dealer id. If dealer id is incorrect, you will get an error back from the host. {% endstep %} {% step %} Issues with the license download. If the license is sent correctly the commercialFleetRoute.prop will be set to DIRECT Verify the commercialFleetRoute.prop is set to DIRECT with the following command from putty:\ **cat /home/pmc/data/license/CommercialFleetRoute.prop commercialFleetRoute=DIRECT** {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/fleet-cards-commander-fleet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.