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

# Configuring WEX Comdata Fleet Codes

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

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Bwl7LYvzofalCx2E07St/images/image1.jpg)

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

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ts8dAOk218HwoePOGcbs/images/image2.png)

<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 Commander Release 57.01 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 %}


---

# 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/configuring-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.
