Welcome to the Help Center - Guides to support and troubleshoot your Verifone devices
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Proprietary FEP Interface

Revision History

Date
Description

09/25/2015

Format Update.

10/29/2015

Added Commander section and updated Sapphire.

09/15/2016

Updated Format.

04/20/2026

Removed Sapphire Section.

This Feature Reference provides detailed information on how to configure and use the Proprietary Interface feature on the Verifone Commander.

This feature document contains the subsections listed below:

  • Overview - This section contains a brief description, requirements and the supported hardware configurations for the Proprietary Interface feature on Verifone Commander.

  • Configuring - This section contains information on how to configure the Proprietary Interface feature on Verifone Commander.

  • Using - This section describes how to prepare the specific Verifone Commander for the Proprietary Interface feature.

  • Reporting - This section contains a sample report with a detailed report description for the Proprietary Interface feature on the specific Verifone Commander.

Glossary of Terms

The following terms and definitions will assist the reader with understanding the content of the Feature Reference

Terms
Definitions

DCR

Dispenser Card Reader

FEP

Front End Processor

MOP

Method of Payment

POS SYSTEM

Includes the POS (Point of Sale) terminals, site controller and the Electronic Payment System (EPS).

PPU

Price Per Unit

STAN

System Traced Audit Number (Transaction ID), a unique key for the card transaction.

Feature Description

The Proprietary FEP (Front End Processor) Interface Feature Reference provides instructions for installing and configuring Proprietary Cards and the functionality within the application using a Verifone Commander.

The proprietary network option allows Commander applications to accept proprietary cards at the POS and card readers using an MX Series PINpad.

Verifone Commander records totals for proprietary card sales and reports them in the Proprietary Card Report for the period. See the Reports Reference in Report Navigator for a description of the report.

Special Considerations

  • Credit Cards that are set up as proprietary are approved through the Proprietary Network Host.

  • Proprietary Cards do not support fallback processing.

  • The Proprietary Configuration is programmed to accept a specific card.

Supported Hardware Configuration

  • Verifone Commander with C18 Point of Sale

Configuring the Proprietary FEP Interface

Hardware Setup

Connect the serial proprietary network cable to the serial port on the back of the Verifone Commander.

Configuring with Commander Configuration Client

Proprietary Fleet Configuration

From the Commander Configuration Client, go to: Payment Controller > EPS Configuration > Proprietary Fleet Configuration.

The Proprietary Fleet Configuration window displays.

The following tabs are available for selection:

FEP Tab

1

FEP Tab

Select the [FEP] tab and configure the Network Parameters.

Network
Definition

FEP Enabled

Enables the proprietary network.

Dealer ID

Merchant ID number is assigned by the Proprietary Fleet <alphanumeric, up to 11 characters>.

2

Communication Options

Configure the Communication Options.

Mode
Definition

Serial

Select [Serial] for the communication mode.

Serial Mode settings are provided by the customer, procured from their private vendor.

Communication Options

Serial Port

Determines the Serial Port.

Baud Rate

Determines the Baud Rate

Bits

Determines the bits being utilized <7 or 8>.

Parity

Determines the parity <odd, even or none>.

Stop Bit

Determines the stop bit <1, 1.5, or 2>.

3

Save Changes

Select [Save] to accept, or [Cancel] to exit without saving changes.

Log off/Log on all POS terminals after any setting modifications to allow changes to take effect.

FEP Card Tab

1

Open FEP Card Tab

From the Proprietary Fleet Configuration window, select the [FEP Card] tab.

The FEP Card window displays.

2

Add and Configure a Card

Select [Add] to configure the FEP Card.

Configure the Card Information and Limits.

Card Information
Definition

Card Table Index

A unique single-digit identifier.

Card Abbreviation

Sets the abbreviated proprietary card name.

Card Name

Determines the proprietary card name.

Lower ISO

Sets the card range that identifies the proprietary card.

Upper ISO

No configuration.

Pan Length

Determines the total number of digits embossed on the card.

Card Enabled

Enables the selected proprietary card.

Accept Manual Entry

Allows the account number to be entered manually instead of swiped.

Card Limits

DCR Auth Amount

Maximum credit transaction dollar amount allowed at a DCR transaction for this proprietary card.

If the amount reaches the DCR limit, the pump automatically shuts off.

3

Save Changes

Select [Save] to accept, or [Cancel] to exit without saving changes.

Log off/Log on all POS terminals after any setting modifications to allow changes to take effect.

Verifone Commander Low ISO and Pan Length Configuration

Several different track layouts have been identified. Review the examples below to configure the ISO and Pan Length for each layout.

Example
Pan and ISO Track Layout

Track2 data: 6543121234523233

Pan Length

  • The Pan is identified by all digits before the first ‘=’.

  • If Track2 does not contain a ‘=’, then the Pan is the entire Track2 data.

  • With no ‘=’ signs, the entire track data is the Pan and the length is all the digits.

•The Pan length would be 16.Low ISO

  • The ISO would be the first 1-6 digits (6543).

  • Use what is sufficient to identify the group of cards.

Example
Pan and ISO Track Layout

Track2 data: 654312=123452323 654312=123452323=8877

Pan Length

  • The PAN would be all digits left of the first ‘=’.

  • The Pan Length would be 6.

Low ISO

  • The ISO would be the first 1-6 digits (654312).

  • Use what is sufficient to identify the group of cards.

Track2 data: ==6543=123452323=8877 =6543=123452323=8877

  • The leading ‘=’ and ‘==’ would be stripped off.

  • The ISO would be 6543 and the Pan Length would be 4.

Track2 data: ==6543====887788776 =6543====887788776

  • The leading ‘=’ and ‘==’ would be stripped off. However, the following consecutive ‘=’ could cause parsing issues.

  • Leave the leading ‘=’ or ‘==’ in place when entering the data in the Low ISO field.

  • The ISO would be ==6543 with a Pan Length of 6 or =6543 with a Pan Length of 5.

Using the Proprietary FEP Interface

Sales

Proprietary Transaction

1

Start the Sale

From the POS, enter the <sale items>.

Press [TOTAL].

Press [CREDIT].

2

Complete Card Authorization

A message will prompt to “Ask customer to swipe card. Follow PINpad Instructions.”

The customer swipes their card and completes the requested information on the PINpad.

The receipt prints when authorization is received.

Manual Card Entry Transaction

In some instances, the card magstripe is unreadable and the card number and expiration date must be manually entered.

Manual Entry requires an existing Method of Payment definition using MOP Code: 25-Manual_Entry.

1

Open Other MOP

From the POS, enter the <sale items>.

Press [TOTAL].

Press [OTHER MOP].

The Other MOP window displays.

2

Manual Entry MOP

Select the Manual Entry MOP.

3

Enter Card Details

Enter the <account number>.

Press [OK].

Enter the <month> and <year> and (MMYY) of the card expiration date.

Press [OK].

The receipt prints when authorization is received.

Refunds

Refund Transactions

1

Start Refund Mode

From the POS, press [REFUND].

The word REFUND displays in the upper left corner of the POS window to indicate the POS is now in refund mode.

2

Enter Refund Items

Enter the <refund items>.

The refund items are listed in the transaction window with the Amount Due, and the total refund (credit balance).

3

Complete the Refund

Press [TOTAL].

Enter the <STAN number>.

Press [CREDIT].

Swipe the card.

Ask the customer to complete the requested information on the PIN pad.

The receipt prints when authorization is received.

Manual Card Entry Refund Transaction

In some instances, the card magstripe is unreadable and the card number and expiration date must be manually entered.

Manual Entry requires an existing Method of Payment definition using MOP Code: 25-Manual_Entry.

1

Start Refund Mode

From the POS, press [REFUND].

The word “REFUND”displays in the upper left corner of the POS window to indicate the POS is now in refund mode.

2

Open Other MOP

Enter the <refund items>.

Press [OTHER MOP].

The Other MOP window displays.

3

Select Manual Entry MOP

Select the Manual Entry MOP.

4

Enter Card Details

Enter the <account number>.

Press [OK].

Enter the <month> and <year> (MMYY) of the card expiration date.

Press [OK].

A receipt is printed from the POS

Reporting

The Proprietary reports can be accessed from the POS at Network Menu > EPS Network Reports > Proprietary Reports.

Proprietary Card Report

Proprietary Card Report shows sales totals by card type.

Report Details:

  • TITLE: Proprietary Card Report.

  • DLR#: Dealer identification number.

  • PRINTED: Date and time the report printed.

    • MM/DD/YY: Date in month, date year format.

    • HH:MM:SS: Time in hour, minutes, and seconds.

  • WORKSTATION ID: Workstation identification number.

  • TERMINAL BATCH: Terminal batch number.

TERMINAL BATCH OPEN: Time and date terminal batch was opened.

  • TERMINAL BATCH CLSE: Time and date terminal batch was closed.

  • CARDTYPE: Type of proprietary card used in the transaction.

    • CNT: Count of card type used.

  • SALES: Transaction amount for card type.

    • CNT: Transaction count for card type.

  • REFUNDS: Amount of refunds given for card type.

  • TOTAL: Total amounts in a batch transaction.

Proprietary Product Report

Proprietary Product Report shows sales totals by product code.

Report Details:

  • TITLE: Proprietary Product Report.

  • DLR#: Dealer identification number.

  • PRINTED: Date and time the report printed.

    • MM/DD/YY: Date in month, date year format.

    • HH:MM:SS: Time in hour, minutes, and seconds.

  • WORKSTATION ID: Workstation identification number.

  • TERMINAL BATCH: Terminal batch number.

  • TERMINAL BATCH OPEN: Time and date terminal batch was opened.

  • TERMINAL BATCH CLSE: Time and date terminal batch was closed.

  • PROD: Assigned product number.

  • DESC: Product description.

  • VOLUME: Total volume of fuel dispensed.

  • CNT: Transaction product count.

  • SALES: Transaction amount.

  • TOTAL: Total amount in a batch transaction.

Unconfirmed Transaction Report

The Unconfirmed Transaction Report displays all the declined and failed Store and Forward transactions. If a Store and Forward transaction is declined by the Host, it has to be manually settled.

This report also contains successful pre-authorized, but incomplete, transactions. This report accepts terminal batch numbers as input.

Report Details:

  • TITLE: Unconfirmed Transaction Report.

  • DLR#: Dealer identification number.

  • PRINTED: Date and time the report printed.

    • MM/DD/YY: Date in month, date year format.

    • HH:MM:SS: Time in hour, minutes, and seconds.

  • WORKSTATION ID: Workstation identification number.

  • TERMINAL BATCH: Terminal batch number.

  • TERMINAL BATCH OPEN: Time and date terminal batch was opened.

  • TERMINAL BATCH CLSE: Time and date terminal batch was closed.

  • ACCOUNT NUMBER: Account number for the proprietary card.

  • STAN: System traced audit number (Transaction ID).

  • TOTAL AMOUNT: Total amount of the card transaction.

  • TIMESTAMP: Date and time of the transaction.

    • MM/DD/YY: Date in month, date year format.

    • HH:MM:SS: Time in hour, minutes, and seconds.

  • TRANSTYPE: Proprietary card transaction detail.

  • TICKET#: Receipt number.

  • PRODDESC CODE: Description and code assigned to product.

  • QUANTITY: Amount of transaction.

  • PPU: Price per unit of transaction.

  • AMOUNT: Amount of transaction.

Last updated