> 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-mudflap-support.md).

# Fleet Cards  - Mudflap Support

## Revision History

| Date          | Description  |
| ------------- | ------------ |
| July 31, 2026 | Intial Draft |

## Overview

Mudflap Commercial Fleet Support enables Verifone Commander sites to accept Mudflap fuel codes as a method of payment, extending the Commander Fleet offering with direct acceptance of the Mudflap commercial fleet network alongside Comdata and WEX-OTR.

Mudflap is a fuel payment service used by owner-operators and small trucking fleets. Instead of presenting a physical fleet card, the driver receives a numeric fuel code through the Mudflap mobile app and presents that code at the point of sale at the register for inside purchases, or at the fuel dispenser for outside fueling.

With Mudflap Commercial Fleet Support, the Verifone Commander accepts these fuel codes and authorizes them directly with Mudflap in real time. Mudflap operates as a commercial fleet payment provider on the Commander, side by side with the existing Comdata and WEX-OTR offerings, and uses the same configuration surfaces, licensing, and reporting as the rest of the Commander Fleet family.

The driver pays Mudflap through the app , the site never charges the driver's card directly and Mudflap emails the driver an IFTA-friendly receipt after fueling. A paper receipt is also available at the site.

### Business Value

* Attracts Mudflap's nationwide network of independent drivers and small fleets to the site. The driver pays through the app, and the site is paid through its normal fleet settlement.
* Direct integration on the Commander -- no separate terminal or standalone hardware is needed to accept Mudflap.
* Consistent with the existing fleet offering -- the same commercial fleet license, the same Commander Central configuration area, and the same standard fleet reports.

### Feature Behaviour

<table><thead><tr><th width="278.4443359375">Situation</th><th>Behaviour</th></tr></thead><tbody><tr><td>Customer pays inside with a fleet code</td><td>The cashier selects the Fleet Code method of payment; the customer is prompted to enter the fuel code from the Mudflap app. The transaction is authorized by Mudflap in real time.</td></tr><tr><td>Driver fuels outside at the dispenser</td><td>The driver enters the mobile/fuel code at the dispenser. Fueling is authorized up to the lower of the amount approved by Mudflap and the site's pump limit.</td></tr><tr><td>Inside prepay</td><td>The pump stops at the authorized amount (or the site's maximum fuel limit, whichever is lower), including when multiple fuel products are selected.</td></tr><tr><td>Connection to Mudflap</td><td>The Commander checks the connection to the Mudflap host about once every minute and reflects the result in the provider's online status.</td></tr></tbody></table>

### Supported Platforms & Prerequisites

<table><thead><tr><th width="302.888916015625">Requirement</th><th>Details</th></tr></thead><tbody><tr><td>Commander software</td><td>Base057.01.00 or later</td></tr><tr><td>Commander Central (formerly C-Site Management)</td><td>PCS v1.26.0 or later, for site configuration</td></tr><tr><td>License</td><td>Commercial Fleet Direct (CFD) license -- the same license used for Comdata and WEX-OTR. All commercial fleet providers on the site enable together and expire together with this license. Mudflap specifically requires the Direct license type; see Feature Restrictions.</td></tr><tr><td>Mudflap enrollment</td><td>The site must be enrolled with Mudflap and have its Mudflap merchant credentials (Merchant ID and access token) available for configuration.</td></tr></tbody></table>

### Feature Restrictions

* Refunds are not supported for Mudflap tenders. Refund attempts with the Fleet Code method of payment are declined at the point of sale.
* Stand-in (offline) processing is not supported. If the Mudflap host cannot be reached, new Mudflap transactions are declined rather than approved locally.
* Partial approval is not supported for inside sales. If the amount Mudflap approves is less than the ticket total, the transaction is declined; the customer can retender with fewer items or a different payment method.
* Mudflap is available only with Commercial Fleet Direct licensing. On sites licensed as Commercial Fleet Primary, Comdata and WEX-OTR cards continue to process through the site's primary payment processor, but Mudflap fuel codes are not accepted at all -- Mudflap has no primary-processor fallback.

### Interaction with Other Features

* **Comdata and WEX-OTR:** Mudflap coexists with both. Unlike those providers, Mudflap fuel codes are accepted at both commercial and retail register positions; Comdata and WEX-OTR fleet codes entered at a retail position are still declined.
* **Idle-screen softkeys:** The mobile-code softkey can appear on register positions independently of the commercial fleet license state. Sites add or remove the softkey per register or dispenser position based on their own requirements.
* **Product codes:** Items are sent to Mudflap using standard NACS product codes -- no special product mapping is required at the site.

## Configuring Mudflap Commercial Fleet Support

Mudflap is enabled through the commercial fleet (Direct) license. When the license is present on the site, the Mudflap provider becomes available; when the license is absent or expires, the provider is disabled along with the other commercial fleet providers.

### Configuration from Commander Central

Mudflap is configured from Commander Central in the same configuration area as the other commercial fleet providers. The configuration is sent from Commander Central to the site's Commander, and it is retained across software upgrades.

Configure Mudflap configuration in Commander Central from **Payment Operations > Commander Fleet > Providers > Mudflap**

![](/files/45065823d96be9d772b92c364c54c78b5affa1cd)

<table><thead><tr><th width="237.3333740234375">Setting</th><th>Description</th></tr></thead><tbody><tr><td>Access token</td><td>The site's Mudflap access credential. The value is masked on screen, stored encrypted, and visible only to administrators (merchant and merchant organization) and Verifone support personnel.</td></tr><tr><td>Merchant ID (MID)</td><td>The site's Mudflap merchant identifier.</td></tr><tr><td>Host URL</td><td>The address of the Mudflap service. A default value is supplied; change it only if directed.</td></tr></tbody></table>

### Point-of-Sale Configuration

For inside acceptance, the site adds a Code entry to the register as a softkey that acts like like a manual entry MOP, which triggers the customer prompt for the fuel code. For outside acceptance, the mobile-code softkey is added to the desired dispenser positions.

{% stepper %}
{% step %}
In Commander Central, open the Commander’s configuration and select **Forecourt > DCR > DCR Settings**

<figure><img src="/files/Nc32vnstq2FQAUd16HGF" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Go to the Idle Screen tab.
{% endstep %}

{% step %}
Click an empty softkey slot and choose **CODE** from the Softkey Type list, then save.

<figure><img src="/files/vla5QFHNcHMt7EJLzJ6w" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
On the site, refresh the Config Client and confirm the CODE key appears on the DCR Idle screen layout.
{% endstep %}

{% step %}
Perform a full Fuel and DCR initialization to apply the change to the dispensers.

<figure><img src="/files/90ezHRgTENBo36vmdAjr" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Good to know:** The CODE option appears in Commander Central only for Commanders on Base057.01.00 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 %}

## Using Mudflap Commercial Fleet Support

### Inside Sales

{% stepper %}
{% step %}

## Ring up the customer's items

Ring up the customer's items as usual.
{% endstep %}

{% step %}

## Select Code soft key

At tender, select the Fleet Code method of payment.
{% endstep %}

{% step %}

## Enter the fuel code

The customer is prompted to enter the fuel code from their Mudflap app.
{% endstep %}

{% step %}

## Authorize the transaction

The Commander sends the code to Mudflap for authorization.
{% endstep %}

{% step %}

## Complete or retender the sale

If approved, the sale completes and the receipt prints. If declined, the message returned by Mudflap is displayed -- the customer can retender with another payment method.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The approval must cover the full ticket amount. If Mudflap approves less than the ticket total, the sale is declined; ask the customer to remove items or use another payment method for the difference.
{% endhint %}

### Prepay Fueling

For an inside prepay, fueling stops at the authorized amount or the site's maximum fuel limit, whichever is lower. This holds when the customer selects multiple fuel products within the same prepay -- the combined dispensed amount cannot exceed the authorized total.

### Outside Fueling at the Dispenser

{% stepper %}
{% step %}

## Select the code option

The driver selects the mobile/fuel code option at the dispenser.
{% endstep %}

{% step %}

## Enter the fuel code

The driver enters the fuel code from the Mudflap app.
{% endstep %}

{% step %}

## Begin fueling

After Mudflap approves, fueling is enabled up to the lower of the approved amount and the site's pump limit.
{% endstep %}
{% endstepper %}

### Declines and Errors

When a transaction cannot be completed, a message is shown on both the cashier and customer displays. The first line states the category; where Mudflap provides a specific reason, it appears on a second line. Messages are available in English and Spanish.

| Message                                                                          | What it means                                                                                                                                                                                                                            |
| -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Insufficient Balance                                                             | Inside sale: the amount Mudflap approved is less than the ticket total. The sale is declined and any amount Mudflap had reserved is automatically released -- no funds remain held. Retender with fewer items or another payment method. |
| Location or fuel code not found. / e.g. "Fuel code is invalid or not recognized" | The fuel code is wrong or expired, or the site is not recognized by Mudflap. Ask the driver to check the code in their Mudflap app.                                                                                                      |
| Authorization failed. Contact Mudflap support.                                   | The site's Mudflap credentials are not being accepted. Check the site's Mudflap configuration or contact support.                                                                                                                        |
| Transaction declined by host. / plus the reason from Mudflap                     | Mudflap declined the transaction for another reason -- the second line gives the specific cause.                                                                                                                                         |

If the connection to Mudflap is lost after fueling has completed, the Commander automatically retries the final payment message about once per minute, up to ten times. If it still cannot reach Mudflap, the transaction is placed on the exception list and appears on the Mudflap Exception report for follow-up.

## Known Behaviours & Edge Cases

<table><thead><tr><th width="334">Scenario</th><th>Expected behaviour</th></tr></thead><tbody><tr><td>A Mudflap fuel code is entered at a retail (non-commercial) register position</td><td>The transaction processes normally. Comdata and WEX-OTR fleet codes entered at a retail position are declined.</td></tr><tr><td>The commercial fleet license has expired but the mobile-code softkey is still on screen</td><td>The softkey may still display, but fleet transactions do not process. Sites can remove the softkey from individual positions if desired.</td></tr><tr><td>Mudflap approves less than the ticket total on an inside sale</td><td>The transaction is declined with "Insufficient Balance" on both displays, and the reserved amount is automatically released. The customer can retender with fewer items.</td></tr><tr><td>Site is licensed as Commercial Fleet Primary (not Direct)</td><td>Mudflap fuel codes are not accepted at all, while Comdata and WEX-OTR cards continue to process through the site's primary payment processor.</td></tr><tr><td>Prepay with multiple fuel products</td><td>Total fueling across the products stops at the authorized amount.</td></tr><tr><td>Pump overrun conditions on a prepay</td><td>The pump stops at the authorized amount or the site's maximum fuel limit.</td></tr><tr><td>Mudflap host is unreachable</td><td>New transactions are declined -- there is no stand-in approval. The provider's online status reflects the connection state, which is checked about once per minute.</td></tr><tr><td>Completion cannot reach Mudflap after fueling</td><td>The Commander retries automatically, then places the transaction on the exception list, visible on the Exception report.</td></tr><tr><td>Software upgrade (Auto Upgrade)</td><td>Mudflap configuration, including the access token, is retained across the upgrade.</td></tr></tbody></table>

## Reporting

Mudflap uses the same standard set of terminal-side fleet reports as the other commercial fleet providers:

* **Terminal Day Summary** -- day-level totals for Mudflap activity (intended primarily for back-office use).
* **Detail** -- transaction-level detail (intended primarily for back-office use).
* **Day Exception Details** -- transactions that could not be finalized with Mudflap, with the failure result, amount, trace number (STAN), and account number, plus exception totals. This is the report to check when a completion could not reach Mudflap.

To print the Exception report at the point of sale:

{% stepper %}
{% step %}

## Open the Network Menu

From CSR Functions, open the Network Menu.
{% endstep %}

{% step %}

## Select EPS Secure Report

Select EPS Secure Report.
{% endstep %}

{% step %}

## Open the Exception Report

Select MudFlap Report, then Exception Report.
{% endstep %}
{% endstepper %}

![](/files/fbbea4506d865bdf08562310d9b7383ea79cd9aa)

*Sample Mudflap Exception report.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/feature-references/features-and-products-references/fleet-cards-mudflap-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.