> 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/known-behaviours-and-edge-cases.md).

# Known Behaviours & Edge Cases

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


---

# 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/known-behaviours-and-edge-cases.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.
