> 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/commander-fleet-enrollment.md).
# Commander Fleet Enrollment
Enroll a site in Commander Fleet, complete configuration, and prepare pumps for fleet transactions.
Use this guide to confirm site readiness with your Verifone Authorized Service Contractor (VASC), enroll in Commander Fleet, and complete setup.
Keywords
**Also called:** enroll in Commander Fleet, Commander Fleet setup, sign up for fleet cards, fleet card enrollment, activate fleet cards, turn on fleet cards, WEX enrollment, Comdata enrollment
**Keywords:** Commander Fleet, Commander Central, C-Site, CSite, CSITE, fleet card, fleet provider, fleet host, WEX, WEX OTR, Comdata, MID, merchant ID, MNSP, VASC, Commercial Fleet, diesel pumps, Config Client, Fuel Configuration, Commander Fleet license, Ineligible site, version 56.02, fleet transaction setup
***
## Before you enroll
### Start with your Verifone Authorized Service Contractor(VASC)
{% hint style="warning" %}
## **Start with your VASC.**
#### **Before beginning Commander Fleet enrollment, have a VASC:**
* Confirm the site can receive the **required Commander version.**
* Confirm the site is capable of **accepting Fleet transactions.**
* Complete this **assessment before enrollment**.
* Complete this assessment **before requesting a merchant ID (MID) from a Fleet Host.**
{% endhint %}
***
Before starting enrollment, please confirm that your site meets the following requirements:
### Information You’ll Need
* Your business name and primary contact information.
* Billing details for payment and invoicing (a credit card is required for online enrollment through Commander Central (formerly C-Site)).\
If you already have payment terms with Verifone, see the note in Step 2.
* Access to Commander Central (formerly C-Site) for configuration.
* Site information for the location you are enrolling.
### Site prerequisites
Confirm each requirement before you enroll:
| Requirement | What it means |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Commander software** | Your site runs Commander version **56.02 or later**. |
| **Commander Central access** | You can access **Commander Central (formerly C-Site)**. It is required to complete setup and download the Commander Fleet license. |
| **Network connectivity** | Your site has **active IP/network connectivity** to **DCRs/dispensers** to support fleet processing at the pump. |
| **Site hardware** | Your **site hardware supports fleet transactions**, including required key entry, such as an alphanumeric or on-screen keyboards where applicable. |
| **Fleet card setup** | You have, or are ready to obtain, **credentials from each fleet provider**. You need an MID for each provider, such as WEX or Comdata. If you have an existing MID, you must notify the service provider you intend to use Commander Fleet. |
| **MNSP connectivity** | Contact your **MNSP to ensure connectivity is enabled.** Tell them you intend to accept fleet payments through Commander. |
***
#### **Not sure your site meets these requirements?**
Contact your **VASC** or the **Verifone Help Desk** to confirm readiness before you enroll.
***
### Base 56+ and Base 57+ upgrade requirements
Before upgrading to Base 56 or later, verify the following requirements:
* **DCR communication:** **Base 56 and above** supports **IP (Ethernet) DCR communication only**. Serial DCRs are not supported.
* **Serial DCRs:** **Do not upgrade** sites with **serial DCRs** until you convert them to IP/Ethernet communication.
* **Sites without DCRs:** Sites with **no DCRs** can run **Base 56+ without impact** from this DCR communication requirement.
* **Upgrade risk for serial DCRs:** An upgrade to **Base 56 or later** at a site with **serial DCRs** may complete successfully. However, the DCRs could go offline and stop communicating.
* **Commander memory:** **Base 57 and higher** requires a Commander with a **minimum of 8 GB RAM**. Systems below this memory requirement may be unable to complete the upgrade or support the software. A VASC can install the required minimum RAM(memory).
{% hint style="warning" %}
## Recommendation:
#### **Before upgrading to Base 56 or higher, have a VASC:**
* Review and validate the **DCR connectivity type**.
* Verify the **Commander hardware specifications**.
* Always review the applicable release notes for **complete software, hardware, and compatibility** requirements.
{% endhint %}
***
## Enrollment steps
{% stepper %}
{% step %}
## Engage a VASC
Complete Fleet enrollment with a Verifone Authorized Service Contractor (VASC). Contact your VASC before you begin.
Your VASC confirms that:
* Your site's hardware supports Commander Fleet.
* Your site can receive the required Commander software version.
* Your site can accept Fleet transactions.
### Check pump and DCR software
Confirm every dispenser and DCR is on the minimum recommended software version.
1. Sign in to **Config Client** from a register or back-office computer.
2. Go to **Reporting → Site Asset Data → Dispenser Data**.
3. Select each device in the list. Record the value in **Peripheral: Device → Software Version**.
4. Compare each version with the minimum recommended version in the **Commander Software Release Notes**.
{% hint style="info" %}
Review every device listed. Upgrade devices below the recommended version before completing enrollment.
{% endhint %}
Your VASC can also help with site setup and configuration.
{% hint style="info" %}
**Contact your VASC to start the enrollment process.**
{% endhint %}
{% endstep %}
{% step %}
## Complete Your Purchase of Commander Fleet
**Before you Begin:**\
Start your enrollment in Commander Central (formerly C-Site). During enrollment, you will:
* Review options for enrollment in Commander Fleet.
* Enter your business and billing information, if applicable.
* Complete checkout and submit your enrollment.
{% hint style="info" %} **Note:**** Already have payment terms with Verifone?** Then you will not enroll in online recurring billing. Contact your sales representative directly to complete your enrollment.
{% endhint %}
**Steps to order Commander Fleet:**
1. Select **Administration**.
2. Under **Site Management**, select **Services**.
3. Select **Commander Fleet Service**.
4. Review the **Site list**.
5. Select **Sign up** next to the site you want to enroll.\
If the site shows **Ineligible**, see [My site shows "Ineligible"](#my-site-shows-ineligible) below. Otherwise, continue to **Step 6**.
My site shows "Ineligible"
This usually means the site does not have a valid address. To fix it:
1. Go to **Administration** > **Site Management** > **Sites**.
2. Open your **Site Name**.
3. Select **More** > **Edit Site**.
4. Fill in the **Address** for the location.
Then go back to the site list and **Sign up** again.
6. **Acknowledge** the Prerequisites, Site Address, and Terms & Conditions. Open the **Terms** to continue.
7. Select **Purchase Now**.
8. Enter your **Card Details** and **Billing Information**.
9. Select **Place Order**.
{% endstep %}
{% step %}
## Finish setup in Commander Central (formerly C-Site)
After you enroll, you will finish the setup in Commander Central (formerly C-Site).
**In Commander Central (formerly C-Site), you will:**
* Complete the required configuration steps
* Confirm the site-specific settings
* Get your location ready for activation
* The site/owner or an authorized VASC has to complete this step
**Commander Central (formerly C-Site) Configuration steps:**
1. Select **Payment Operations**.
2. Select **Commander Fleet**.
3. Select the applicable **Fleet Provider** tab to configure.
4. Enter the **Merchant ID** from your Host provider.
5. Enter the **IP/Host** from your MNSP.
6. Enter the **Port** from your Host provider.
{% endstep %}
{% step %}
## Turn On or Enable Commercial Fleet at the Pumps
Flag each diesel pump individually for **Commercial Fleet** in Config Client.
Go to **Forecourt** > **Fuel** > **Fuel Configuration**.
{% endstep %}
{% step %}
## Test your configuration
Confirm that Fleet card transactions are successful by testing in your live (production) retail environment.
If you do not have test cards, monitor customer activity.
{% endstep %}
{% endstepper %}
***
## Common questions
Do I need a VASC to enroll in Commander Fleet?
Yes. Fleet enrollment must be completed with a VASC. Contact yours at the start of the process so they can check your site and help with setup.
What Commander software version do I need?
Version 56.02 or higher.
Can I enroll online if I already have payment terms with Verifone?
No. If you already have payment terms, you will not enroll in online recurring billing. Contact your sales representative directly to complete your enrollment.
Do I need a merchant ID (MID) before I enroll?
You need an MID from each fleet provider before you set up the site in Step 3. If you don't have one, get your VASC's check first, then ask the fleet provider. If you already have an MID, tell the provider you plan to use Commander Fleet.
Who completes the setup in Commander Central (formerly C-Site)?
The site or owner or an authorized VASC.
How do I test Commander Fleet?
Confirm that fleet card transactions succeed in your live retail environment.\
If you do not have test cards, monitor customer activity.
***
## Need help?
Contact Verifone Help Desk for:
* Enrollment or checkout questions
* Commander Central (formerly C-Site) access or configuration help
* Commander Fleet setup and support
{% hint style="info" %}
N**eed assistance? Contact Verifone Helpdesk at anytime.**
* Use our **Chat** platform
* Or call **1.800.VERIFONE (837.4366)**
Tell us the troubleshooting steps you’ve already tried. This saves time and gets you the right support faster.
{% 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/commander-help/commander-fleet/commander-fleet-enrollment.md?ask=&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.