# Cash Credit Pricing

## Overview

Cash/Credit Pricing is used to allow a site to sell fuel at different fuel price levels based on whether the sale is paid by Cash or Credit (e.g. sites will often set the credit fuel price higher than the cash fuel price to offset the credit transactions fees for the site).

If the site is using different fuel prices for cash and credit, they must disable (or uncheck) the **Ignore MOP Conflict**setting in **Fuel Configuration > Site Params**.

The price level for each card type can be configured in the **Payment Controller > EPS Configuration > FEPCard**- **Cash Credit Pricing by Card Type**configuration screen.

If no configuration is done for the price level by card type, debit and prepaid cards default to cash fuel price level and all other card types default to credit fuel price level.

## Using Cash/Credit Pricing

### Prepay Transactions

**Amount Prepay**: If the transaction is tendered by cash, the customer dispenses fuel at the cash fuel price level at the pump. If the transaction is paid by credit, the customer dispenses fuel at the fuel price level configured for the card type (e.g. debit cards can either be configured at cash or credit price level).

**Volume Prepay**: For volume prepays, the cashier must select a fuel grade and a fuel price level when they ring up the fuel prepay. If the transaction is tendered by cash, the MOP entered must match the fuel price level selected by the cashier. If the transaction is paid by credit, the price level configured for the card type must match the fuel price level selected by the cashier. If there is a price level conflict, then an error message appears indicating "**MOP Conflict**".

### Postpay Transactions

When the **Ignore MOP Conflict** parameter is enabled (or checked), sales can be tendered using any MOP regardless of the original fuel price level of the sale.

When this parameter is not enabled (or not checked) and if the transaction is tendered by cash, the MOP entered must match the fuel price level. If the transaction is paid by credit, the price level configured for the card type must match the fuel price level. If there is a price level conflict then an error message appears indicating "MOP Conflict".

### DCR Transactions

Transactions initiated at the dispenser card reader are authorized at the fuel price level that has been configured for the card type that is used.

## Configuring Cash/Credit Pricing

If the site is using different fuel prices for cash and credit, disable (or uncheck) the **Ignore MOP Conflict** setting in **Forecourt > Fuel > Site Parameters**.

![](/files/120f4cce0b91c620e6ae30787e6674d684397f34)

Configure cash and credit price amount for each fuel product service levels in **Forecourt > Fuel Prices** form.

![](/files/e69bfc5bb745ce8ddc6081363b42c8a71673bda4)

Price Tier allows credit cards to be setup for cash pricing for fuel. Configure **Price Tier** in **Payment Controller > EPS Configuration > > FEPCard Type** form.

![](/files/f6f9f5414492b5cc3b5ea1f9f32072e596091adc)

| ![](/files/f244668a7725132edd255f6aab22a286cca5521c)**Note** | \_Refer to Fuel Prices\_for more information. |
| ------------------------------------------------------------ | --------------------------------------------- |

| ![](/files/f244668a7725132edd255f6aab22a286cca5521c)**Note** | *The price tier will be determined by the matching card table entry. If the card table entry does not specify a price tier, then the payment method determines the price tier. For example, Debit method of payment will map to CASH price tier.* |
| ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

### Configuring Fuel Prices for 2 Decimal Places

1. Go to **Forecourt > Fuel > Fuel Config Pending > Site Parameters**and disable “Force .9 Cents Per Gallon”.

![](/files/be5bc4944a6f909c55e09d14ad001454ae8b7a88)

1. Go to Forecourt > Fuel Prices Pending and change all existing product prices with third decimal place to 0 (eg: from $2.152 to $2.150).

![](/files/6dc92befff34fac25e695654e3d7f2a7991751e6)

1. Go to **Forecourt > Fuel > Fuel Config Pending > Site Parameters**and change “PPU Decimal Position” and “Total Decimal Position” to “2”.

![](/files/e562a73da02f253ad4d733e568cbfd0453f6f1f2)

1. Go to Forecourt > Fuel Prices Pending and change the prices of the product per gallon to the $XX.XX format for both Tier One and Two Prices.

![](/files/5aab9835c798d7b9875345e62a150d4b77eb18b0)

### Feature Limitations

* * Sites can be configured to take fuel prices with either two or three decimal places; $xx.xx or $x.xxx. Sites cannot have mixed decimal positions while using a single Verifone Commander.
  * At two decimal sites, prices that have 3 decimal places (eg. $4.299) will only be calculated at the 2 decimal amount (eg. $4.29).
  * By default, sites are configured for 3 decimal places in $x.xxx format.

## Troubleshooting

If the site is using Cash/Credit pricing and did not ensure the Ignore MOP Conflict parameter is disabled (or unchecked), customers are able to select cash price level at the pump and pay with credit MOP for postpay transactions. This would result in the customer receiving the lower cash price even though they are paying by credit.


---

# Agent Instructions: 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:

```
GET https://docs.verifone.com/commander-user-reference-guides/commander-user-references/commander-user-reference-56.02/cash-credit-pricing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.