> 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-exxonmobil.md).

# Fleet Cards - ExxonMobil

This document describes the specific information related to fleet cards implemented in the Buypass distribution for ExxonMobil.

## 1 Overview

### Feature Description

This document describes the specific information related to fleet cards implemented in the Buypass distribution for ExxonMobil.

Refer to the **Fleet Cards General Fuel Configuration Reference**for more information on the general fuel configuration for all FEPs for the fleet cards feature to work. The feature reference also contains examples of how the fleet cards work at commercial sites.

### Supported Hardware Requirements

* Commander Site Controller with Topaz/Ruby2/C18
* Commander Site Controller base version 53.13 and higher (base version 54.02 for Comdata cards).
* RubyCi with Topaz/Ruby2/C18
* Payment PIN pad(s)
* Wayne DCRs need updated firmware to display the new secure prompts. Refer to release notes.
* Gilbarco DCRs may need updated firmware to support the SPOT protocol. Refer to release notes.

#### Base 53 and Higher UI

The User Interface has changed for base 53 and higher. As a result, after an auto upgrade a few elements on the UI would appear out of place.

To fix this refer to:

* “Configuring POS User Interface Using Configuration Client”
* “Items can be moved in the panel by selecting the item and dragging and dropping to the desired position”
* “Select a panel and click Move Up or Move Down to move the panel.”

#### Note

Parameter Download (PDL) and Dynamic Card Table (DCT) downloads are done from the POS after installing the feature for the first time.

PDL is a general Table Download to enable cards and DCT is a Card Table Download to let the system know how to process the transactions with the cards.

Refer to “PDL & DCT Download”.

### Comdata Cards

{% hint style="info" %}
*Comdata cards are only supported in Base 54.02 Buypass distribution for ExxonMobil.*
{% endhint %}

Comdata is a payment processor and issuer of fleet fuel cards, corporate spend cards, virtual payments, and trucking permits.

Verifone Commander enables the use of Comdata cards on Commercial pumps. Comdata card transactions are processed by adding Comdata as an acquirer to Fiserv Buypass front end processor.

#### Verifone Commander supported Comdata Cards

Verifone Commander Supports three types of Comdata cards.

| **Cards Details**    | **Comdata MC**                | **Comdata OnRoad**            | **Comdata Proprietary Fuel Card** |
| -------------------- | ----------------------------- | ----------------------------- | --------------------------------- |
| **Multi Card**       | Yes - Comdata and Master Card | Yes - Comdata and Master Card | No - Comdata only                 |
| **Fueling position** | Retail and Commercial         | Retail and Commercial         | Commercial Only                   |

* Transactions performed using Comdata proprietary Fuel cards are routed to Comdata network by Fiserv.
* Transactions performed using Comdata multi cards are routed to Comdata or Master card network depending on the product and fueling position used for the transaction. If a fueling position is configured as Commercial, then all Comdata eligible products transactions (post-pay or prepay) on that fueling position are considered as commercial transactions. If a fueling position is not configured as Commercial, then all transactions on that that fueling position are considered as retail transactions.
* If a site is blended or has both retail and commercial fueling positions, then all Comdata transactions are routed to Comdata network via Fiserv and all the retail transactions are routed to the Master Card network via Fiserv.


---

# 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://docs.verifone.com/feature-references/features-and-products-references/fleet-cards-exxonmobil.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.
