> 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-wex-comdata-mobile-app-fleet-codes/using-wex-comdata-fleet-codes.md).

# Using WEX Comdata Fleet Codes

{% 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 %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/fleet-cards-wex-comdata-mobile-app-fleet-codes/using-wex-comdata-fleet-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
