> 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/commander-help/commander-fleet/fleet-card-acceptance-capabilities.md).

# Fleet Card Acceptance Capabilities

Check which Fleet cards Commander accepts, the required Base version, and current availability.

## Fleet card acceptance

Use this reference to confirm Card acceptance and Base version requirements.

{% hint style="info" %}
**Base version requirements are cumulative:** A site running Base 57.02 supports every capability introduced in versions 56.02 and 57.01.
{% endhint %}

***

### Acceptance by Card:

| Fleet card         | Network or family | Minimum Base version | Availability |
| ------------------ | ----------------- | -------------------- | ------------ |
| EFS/T-CHEK         | WEX               | 56.02 or higher      | Available    |
| Fleet One          | WEX               | 56.02 or higher      | Available    |
| CrossRoads Freight | WEX               | 56.02 or higher      | Available    |
| EFS MC Payroll     | WEX               | 56.02 or higher      | Available    |
| EFS MasterCard     | WEX               | 56.02 or higher      | Available    |
| EFS-TS             | WEX               | 56.02 or higher      | Available    |
| EFS FPS Card       | WEX               | 56.02 or higher      | Available    |
| EFS LLC Fuel       | WEX               | 56.02 or higher      | Available    |
| OnRoad             | Comdata           | 56.02 or higher      | Available    |
| Comdata Mastercard | Comdata           | 56.02 or higher      | Available    |
| Comdata Fleet Card | Comdata           | 56.02 or higher      | Available    |
| Comdata Comcheck   | Comdata           | 56.02 or higher      | Available    |
| Pay Codes          | Comdata           | 57.01 or higher      | Beta Only    |
| Mudflap            | Mudflap           | 57.01 or higher      | Beta Only    |
| 10-4               | WEX               | 57.01 or higher      | Beta Only    |
| OTR Cardless       | WEX               | 57.01 or higher      | Beta Only    |
| DriverDash         | WEX               | 57.01 or higher      | Beta Only    |
| QuickQ             | QuickQ            | 57.02 or higher      | Coming soon  |
| Multiservice       | Multiservice      | 57.02 or higher      | Coming soon  |

***

### Rollup by Base Version

| Base version        | Fleet Acceptance Added                                     |
| ------------------- | ---------------------------------------------------------- |
| **56.02 or higher** | WEX family, Comdata family                                 |
| **57.01 or higher** | Mudflap, 10-4, OTR Cardless, DriverDash, Comdata Pay Codes |
| **57.02 or higher** | QuickQ and Multiservice - planned                          |

### Important notes

* QuickQ and Multiservice are planned for Base 57.02 and are not yet generally available.
* Light Fleet Cards - WEX, Voyager, and Fuelman, remain accepted through primary processors.
* Open-loop Visa and Mastercard fleet cards remain accepted through primary processors.


---

# 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/commander-help/commander-fleet/fleet-card-acceptance-capabilities.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.