> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/fleet-cards-wex-comdata-mobile-app-fleet-codes.md).

# Fleet Cards - WEX Comdata Mobile App Fleet Codes

## Revision History

| Date          | Description  |
| ------------- | ------------ |
| July 30, 2026 | Intial Draft |

## Overview

WEX and Comdata Mobile App Fleet Codes lets commercial drivers pay at the dispenser by entering a numeric code generated in their fleet provider's mobile app, instead of swiping a fleet card and answering prompts at the pump. It is part of the Commander Fleet offering on the Verifone Commander.

Commercial fleet providers now offer mobile apps -- WEX's 10-4 app and Comdata's equivalent -- that let a trucker fill in their trip and account details (the information normally prompted for at the pump) on their phone ahead of time. The app then issues a short numeric code. At a participating site, the driver simply presses the CODE key at the dispenser and enters that code; the provider authorizes the transaction with the usual limits and restrictions, and fueling proceeds exactly as if a fleet card had been presented.

This feature adds the code entry capability to the Commander's dispenser card readers (DCRs). It builds on the Commander's existing direct connections to WEX-OTR and Comdata for commercial fleet processing.

### Business Value

* A faster, simpler pump experience for drivers -- the lengthy prompt sequence at the dispenser is replaced by a single code entry, with the details prefilled in the app.
* Keeps sites competitive: fleet providers are actively promoting these apps, and code acceptance is already live at major truck stop chains.
* Strengthens the Commander Fleet offering -- the same capability covers WEX and Comdata, and the related Mudflap offering provides the equivalent for Mudflap drivers.

### Feature Behaviour

The dispenser accepts the following code types. Each code matches only its own provider's processing -- a code is never mistaken for another card type.

<table><thead><tr><th width="307.3333740234375">Code type</th><th>Behaviour</th></tr></thead><tbody><tr><td>WEX 10-4 app code (6 digits)</td><td>Generated in the WEX 10-4 mobile app. Entered at the dispenser; authorized by WEX with the account's limits and restrictions.</td></tr><tr><td>WEX FlowCode (7 or 8 digits)</td><td>Entered at the dispenser and authorized by WEX.</td></tr><tr><td>WEX hand-entered code (7 digits)</td><td>After the code, the dispenser prompts for additional details depending on the code: Carrier ID and Unit Number, or Carrier ID and Driver ID.</td></tr><tr><td>Comdata Pay Code</td><td>Generated in the Comdata mobile app. Entered at the dispenser; authorized by Comdata.</td></tr></tbody></table>

### Supported Platforms & Prerequisites

| Requirement                                    | Details                                                                                                                                                                                    |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Commander software                             | Base057.01.00 or later. On older Commanders the CODE key is not available and is automatically excluded from configuration.                                                                |
| Commander Central (formerly C-Site Management) | PCS v1.26.0 or later, for configuring the CODE softkey                                                                                                                                     |
| Commercial fleet processing                    | The site's WEX-OTR and/or Comdata commercial fleet direct connection must be configured and licensed -- codes are processed through the same connections as the corresponding fleet cards. |
| Dispensers                                     | Code entry is available only on fueling positions designated as commercial.                                                                                                                |

### Feature Restrictions

* Codes are accepted only at commercial fueling positions. On any other dispenser, code entry is refused with a message and the dispenser returns to the idle screen.
* Code entry is a dispenser (outdoor) capability. For inside transactions, drivers use their fleet card as before.
* Codes are never printed on receipts.

### Interaction with Other Features

* WEX-OTR and Comdata fleet card processing: unchanged. Code transactions ride on the same host connections, card tables, and licensing; existing card acceptance is unaffected.
* Mudflap: Mudflap fuel codes are a separate but similar capability with their own configuration -- see the Mudflap Commercial Fleet Support feature reference.

## Configuring the CODE Softkey

{% stepper %}
{% step %}

### Open DCR settings

In Commander Central, open the Commander's configuration and select **Forecourt > DCR > DCR Settings**.
{% endstep %}

{% step %}

### Open the Idle Screen tab

Go to the **Idle Screen** tab.
{% endstep %}

{% step %}

### Add the CODE softkey

Click an empty softkey slot and choose **CODE** from the **Softkey Type** list, then save.

![](/files/3970c2d9d29fc6b7d291cd65c182867df0789235)

*Selecting the CODE softkey type on the DCR idle screen in Commander Central.*
{% endstep %}

{% step %}

### Refresh the Config Client

On the site, refresh the Config Client and confirm the CODE key appears on the DCR Idle screen layout.
{% endstep %}

{% step %}

### Initialize Fuel and DCR

Perform a full Fuel and DCR initialization to apply the change to the dispensers.

![](/files/28e2d9d328c437c43c156dab7573dd20b5d0fc42)

<p align="center"><em>The CODE key on the DCR idle screen layout after the update.</em></p>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The CODE option appears in Commander Central only for Commanders on Base057.01.00 or later. If a site's DCR configuration is copied to a Commander on an older version, the CODE key is automatically left out (the slot shows NA).
{% endhint %}

## Using Fleet Codes at the Dispenser

{% stepper %}
{% step %}

### Generate a code

The driver generates a code in their fleet provider's mobile app (for example, WEX 10-4).
{% endstep %}

{% step %}

### Press CODE

At the dispenser idle screen, the driver presses CODE. No card swipe is needed.
{% endstep %}

{% step %}

### Enter the code

The dispenser immediately prompts for the code; the driver enters it on the keypad.
{% endstep %}

{% step %}

### Enter remaining details for WEX hand-entered codes

For 7-digit WEX hand-entered codes, the dispenser then prompts for the remaining details (Carrier ID and Unit Number, or Carrier ID and Driver ID, depending on the code).
{% endstep %}

{% step %}

### Receive authorization

The provider authorizes the transaction and returns the account's limits and restrictions, and fueling proceeds as with a fleet card.
{% endstep %}

{% step %}

### Print the receipt

The receipt prints as normal; the code itself never appears on it.
{% endstep %}
{% endstepper %}

### Entry Errors

* If the entered code is too short or too long, the dispenser shows "ENTER A VALID CODE" and prompts the driver to try again.
* If the CODE key is pressed on a fueling position that is not designated commercial, the dispenser shows a message that codes are not accepted at that position and returns to the idle screen.

## Known Behaviours & Edge Cases

<table><thead><tr><th width="345.111083984375">Scenario</th><th>Expected behaviour</th></tr></thead><tbody><tr><td>CODE pressed on a non-commercial fueling position</td><td>Code entry is refused with a message and the dispenser returns to the idle screen.</td></tr><tr><td>Code entered with an invalid length</td><td>"ENTER A VALID CODE" is shown and the driver can re-enter the code.</td></tr><tr><td>Any code type entered</td><td>The code matches only its intended provider processing -- it is never matched to another card type on the site.</td></tr><tr><td>Receipt printing</td><td>Fleet codes are never printed on receipts.</td></tr><tr><td>DCR configuration copied from a Base057.01.00 Commander to an older Commander</td><td>The configuration is copied without the CODE key -- the softkey slot arrives as NA on the older Commander.</td></tr><tr><td>Commander on a version older than Base057.01.00 onboarded to Commander Central</td><td>The CODE softkey type is not offered in the DCR idle screen configuration.</td></tr></tbody></table>


---

# 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://docs.verifone.com/feature-references/features-and-products-references/fleet-cards-wex-comdata-mobile-app-fleet-codes.md?ask=<question>&goal=<endgoal>
```

`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.