# ORPAK AVI/RFID Fueling ## Revision History | Date | Description | | ---------- | ----------------------------------------------- | | 02/01/2016 | Initial Release. | | 09/15/2016 | Updated Format. | | 12132016 | Updated PCI private IP addressing requirements. | ## Using this Feature Reference This Feature Reference provides detailed information on how to configure and use the ORPAK AVI/RFID Fueling feature on Verifone Commander. The Feature Reference contains the subsections listed below: * **Overview**- This section contains a brief description, requirements and the supported hardware configurations for the ORPAK AVI/RFID Fueling feature on Verifone Commander. * **Configuring**- This section contains information on how to configure the ORPAK AVI/RFID Fueling feature on Verifone Commander. * **Using**- This section describes how to prepare Verifone Commander for the ORPAK AVI/RFID Fueling feature. * **Reporting**- This section contains a sample report with a detailed report description for the ORPAK AVI/RFID Fueling feature on Verifone Commander. ## Glossary of Terms The following terms and definitions will assist the reader with understanding the content of the Feature Reference.
TermsDefinition
AVIAutomatic Vehicle Identification
CGICommon Gateway Interface
DCRDispenser Card Reader
EPSElectronic Payment System
FCCForecourt Controller
IFSFInternational Forecourt Standards Forum
MWGTMaster Wireless Gateway Terminal
NRNozzle Reader
OTIA company which produces an RFID system similar to that of ORPAK. It is currently not supported.
RFIDRadio Frequency Identification
SDKSoftware Development Kit
VIPERVerifone’s Payment Processing Software running on the Electronic Payment Server.
VIUVehicle Identification Unit
WGTWireless Gateway Terminal
## Overview ### Feature Description {% hint style="info" %} Before starting, obtain the ORPAK AVI IP address from the ORPAK AVI technician. {% endhint %} The ORPAK AVI/RFID Fueling System allows a vehicle equipped with the FuelOmat Gold Vehicle Identification Unit (VIU) devices to obtain automatic payment authorization and purchase fuel. The VIU data is obtained from the vehicle through a wireless connection to a Nozzle Reader (NR) or Wireless Gateway Terminal (WGT) as shown below in the diagram. Next, the VIU data is transferred from these devices via wireless links to the Master Wireless Gateway Terminal (MWGT). The Electronic Payment Server (EPS) periodically sends a status request to the Master WGT via a wired ethernet link. When the MWGT status indicates that VIU data is available, the EPS system will request this data, use it to gain payment approval and allow fuel to be dispensed. ### ORPAK AVI/RFID Fueling System
#### VIU Transaction Flow A VIU Transaction Flow is shown below. The interface between the MWGT and Verifone Commander is defined by the WGT SDK document. The interface between the Commander Forecourt Controller and VIPER is defined by the International Forecourt Standards Forum (IFSF) document. ![](/files/52c7d2d2d4263bb6d729721e801b5961b2454af6) #### Support Limitations * The ORPAK AVI/RFID Fueling feature supports the MWGT and additional WGT devices. * The ORPAK AVI/RFID Fueling feature supports only fleet payment types. * Since VIU track discretion data restricts the purchase to fuel only, there are no modifications to prevent the car wash prompt. * Current POP functionality is not altered. * EPS Loyalty is disabled unless it is selected at the Dispenser Card Reader (DCR) prior to an AVI/RFID fueling attempt. See the Appendix for additional detail. * For an explanation of how ***“Handle Up Calling”***will operate in conjunction with the IFSF\_AVI entry method, see the Appendix. #### Supported Hardware Configuration * Verifone Commander with Verifone C18 Point of Sale ### Configuring the ORPAK AVI/RFID #### Configuring with Verifone Commander Configuration Client {% stepper %} {% step %} **AVI IP address** Obtain the AVI IP address from the Orpak AVI technician. {% endstep %} {% step %} **Managed Modules** From the Verifone Configuration Client, go to: Tools > Managed Modules. ![](/files/14fa4a7455dea4e610d934d6de1d471bedd88460) The Managed Modules window displays. The following tabs are available for selection: * Current Configuration * Pending Configuration * System Resources
{% endstep %} {% step %} **Current Configuration** Select the **\[Current Configuration]** tab. {% endstep %} {% step %} **Fuel RFID Configuration** Select **\[Fuel RFID Configuration]**. {% endstep %} {% step %} **Parameters** Configure the Fuel RFID Configuration parameters. ![](/files/388278b31f4b907e1413e56b390dc7c61b836d0c) | Value | Description | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | **RFID** | | | **AVI enable** | Select to enable AVI. | | **AVI IP Address** | Sets the AVI IP address that must match what is programmed on the AVI controller. | | **OTI enable** | Select to enable OTI. | |

OTI is a company which produces an RFID system similar to that of ORPAK. It has been included for future interface support but is not currently used.

| | | **OTI IP Address** | IP address for OTI. | | {% endstep %} | | {% step %} **Save or Cancel** Select **\[Save]** to accept, or **\[Cancel]** to exit without saving changes. {% endstep %} {% endstepper %} {% hint style="info" %} *The MWGT will be installed on the store LAN. The store router must have a path configured between Verifone Commander and the MWGT.* {% endhint %} {% hint style="info" %} *The configured address must be within the RFC1918 defined range for private IP addresses. Addresses attempting to access the POS Zone that are not within the RFC1918 scope will be denied.* {% endhint %} ### Using the ORPAK AVI/RFID #### Normal Operation {% stepper %} {% step %} **Insert Nozzle** Insert the nozzle that has the RFID into the vehicle gas tank where the Opass RFID device is located. {% endstep %} {% step %} **Connection** The Opass RFID device mounted on the gas tank makes the connection to the RFID nozzle and approves the pump. {% endstep %} {% step %} **Select Grade** If equipped, the customer lifts the lever on the pump and selects the grade. {% endstep %} {% step %} **Dispense Fuel** The customer dispenses the fuel. {% endstep %} {% step %} **Complete Transaction** The customer hangs up the nozzle and completes the fuel transaction. {% endstep %} {% step %} **Print Receipt** A receipt is printed at the DCR. {% endstep %} {% endstepper %} #### Fueling Pause and Resume If the VIU data becomes unavailable while fuel is approved for dispensing, Verifone Commander prevents fuel from being dispensed (Fueling Pause). During a Fueling Pause, Verifone Commander displays the **“PUMP STOPPED”** message at the DCR. If the dispenser handle is lowered during a Fueling Pause, Verifone Commander will terminate the transaction. If fuel dispensing has been prevented (Fueling Pause) for an AVI/RFID transaction, Verifone Commander will prevent the cashier from reapproving the dispenser. There is a limitation in the Tokheim dispenser firmware where a stop command is ignored when it is received within three seconds after a start command is received. Verifone Commander performs a three second delay before issuing a stop command for the Tokheim system to prevent the cashier from reapproving the dispenser. This three second delay will also be observed for all Fueling Pauses with Tokheim dispensers. ### Reporting the ORPAK AVI/RFID #### AVI/RFID Transaction Receipt Verifone Commander prints the AVI/RFID DCR receipt as shown below. ![](/files/2f5d2d0171efa0efa7ec03f6dbf4503df1af6d56) ## APPENDIX ### Dispenser Display The following is information provided to show the dispenser display limitations. #### Dispenser General Limits **Gilbarco:** ***Non-graphics*** One line will display the first 20 characters and then scroll to show any additional characters up to a maximum of 100 characters (any additional characters beyond 100 will be truncated). ***Graphics*** There are eight lines of 20 characters per line. **Wayne:** ***Non-graphics*** Two lines of 16 characters per line ***Graphics*** * **2-line display**— there are two lines of 16 characters per line. * **Full Screen with 5-inch Display**— there are nine lines of 16 characters per line; it is also possible to display 12 lines of 21 characters per line in expanded character mode (only available on Full Screen graphics dispensers). {% hint style="info" %} The 21 character expanded character mode is currently only used for the idle screen. It is possible to use this mode for other screens if desired. {% endhint %} **Tokheim:** ***Non-graphics*** There are lines of 20 characters per line. ***Graphics*** There are four lines of 20 characters per line. #### Dispenser ORPAK AVI/RFID Fueling Display Sequence The following is an example of the messages displayed for a typical ORPAK AVI/RFID Fueling transaction sequence. {% stepper %} {% step %} **Remove Nozzle** The nozzle is removed from the dispenser, placed in vehicle fuel inlet, and VIU data is received by the EPS. {% endstep %} {% step %} **Display Authorization** The dispenser displays the authorizing message and the POS workstations display the fueling icons. {% endstep %} {% step %} **Prompt for Data** If VIU data does not contain the required network payment user data such as odometer, the customer may be prompted to enter it. {% endstep %} {% step %} **Authorize Fueling** After the network payment is authorized, fueling is authorized and the pre-fueling prompt is displayed. {% endstep %} {% step %} **Start Fueling** After fuel dispensing is initiated, the fueling message is displayed. {% endstep %} {% step %} **Pause on Removal** If the nozzle is removed from the vehicle fuel tank, the dispenser is de-authorized and a pause message is displayed. {% endstep %} {% step %} **Resume Fueling** If the nozzle is replaced in the vehicle fuel tank, the dispenser is re-authorized so that fueling can be resumed. A fueling message will be displayed. {% endstep %} {% step %} **Tender Transaction** When fuel dispensing is completed and the nozzle is replaced, the dispenser will tender the transaction and display the receipt prompt. {% endstep %} {% endstepper %} #### Loyalty This section describes Loyalty functionality for an AVI transaction. **Loyalty prompt presented while dispenser idle.** A Loyalty prompt is presented at the DCR requesting that customer to select either ***“Yes”***for Loyalty or ***“No”***to skip Loyalty. ***Scenario 1: Customer selects Loyalty prior to placing nozzle in fuel tank.*** {% stepper %} {% step %} **Select Yes** The customer selects **\[Yes]** at the Loyalty prompt. {% endstep %} {% step %} **Request Loyalty Information** A prompt is presented at the DCR requesting the customer to provide Loyalty information by card swipe or other method such as manual entry. {% endstep %} {% step %} **Enter Loyalty Information** The customer enters the Loyalty information. {% endstep %} {% step %} **Compute Discount** The POS uses the provided Loyalty information to compute the discount on the fuel purchase. {% endstep %} {% step %} **Display Discounted Prices** Any Loyalty generated price per gallon discount and discounted prices display at the dispenser. {% endstep %} {% step %} **Place Nozzle** The customer places the nozzle in the fuel tank. {% endstep %} {% step %} **Receive Payment Information** The POS receives payment information from the MWGT. {% endstep %} {% step %} **Approve Fueling** The POS approves the dispenser for fueling. {% endstep %} {% step %} **Fuel and Hang Up** The customer dispenses the fuel and hangs up the nozzle. {% endstep %} {% step %} **Print Loyalty Discount** The Loyalty discount is included on the receipt by the POS. {% endstep %} {% endstepper %} ***Scenario 2: Customer selects not to use Loyalty prior to placing nozzle in fuel***** tank.** {% stepper %} {% step %} **Select No** The customer selects **\[No]** at the Loyalty prompt. {% endstep %} {% step %} **Request Payment Information** A prompt is presented at the DCR requesting the customer provide payment information. {% endstep %} {% step %} **Place Nozzle** The customer places the nozzle in the fuel tank. {% endstep %} {% step %} **Receive Payment Information** The POS receives payment information from the MWGT. {% endstep %} {% step %} **Approve Fueling** The POS approves the dispenser for fueling. {% endstep %} {% step %} **Fuel and Hang Up** The customer dispenses the fuel and hangs up the nozzle. {% endstep %} {% endstepper %} ***Scenario 3: Customer does not make a Loyalty selection prior to placing nozzle***** in fuel tank.** {% stepper %} {% step %} **Place Nozzle** The customer places the nozzle in the fuel tank. {% endstep %} {% step %} **Receive Payment Information** The POS receives payment information from the MWGT. {% endstep %} {% step %} **Approve Fueling** The POS approves the dispenser for fueling. {% endstep %} {% step %} **Fuel and Hang Up** The customer dispenses the fuel and hangs up the nozzle. {% endstep %} {% endstepper %} **Loyalty prompt presented after payment information received.** A payment prompt is presented at the DCR requesting the customer to swipe a payment card and press a payment type key. {% stepper %} {% step %} **Place Nozzle** The customer places the nozzle in fuel tank. {% endstep %} {% step %} **Receive Payment Information** The POS receives payment information from the MWGT. {% endstep %} {% step %} **Skip Loyalty Prompt** The POS skips the Loyalty prompt since this is an AVI transaction. {% endstep %} {% step %} **Approve Fueling** The POS approves the dispenser for fueling. {% endstep %} {% step %} **Fuel and Hang Up** The customer dispenses the fuel and hangs up the nozzle. {% endstep %} {% endstepper %} #### Handle Up Calling This section describes the system behavior when the POS is configured for a ***“call in”***from the dispenser to the POS workstation. The dispenser call in begins when a dispenser handle is lifted. The POS workstation produces both an audible and visual alert indicating that a dispenser is calling in for authorization. The cashier can then authorize the dispenser by pressing a key on the workstation. **Card Takeover Enabled** Precondition: The system is configured to allow payment information to be presented at the DCR after the dispenser has been approved for fueling by the cashier (Card Takeover Enabled). ***Scenario 1: Cashier authorizes fueling prior to customer placing nozzle in fuel***** tank.** {% stepper %} {% step %} **Raise Handle** The customer raises the handle on dispenser. {% endstep %} {% step %} **Alert Cashier** The POS alerts the cashier of the pump calling in for authorization. {% endstep %} {% step %} **Approve Dispenser** The cashier approves the dispenser for fueling. {% endstep %} {% step %} **Place Nozzle** The customer places the nozzle in the tank. {% endstep %} {% step %} **Receive Payment Information** The POS receives payment information from the MWGT. {% endstep %} {% step %} **Fuel and Hang Up** The customer dispenses the fuel and hangs up the nozzle. {% endstep %} {% endstepper %} ***Scenario 2: Cashier authorizes fueling after customer places nozzle in fuel***** tank.** {% stepper %} {% step %} **Raise Handle** The customer raises the handle on the dispenser. {% endstep %} {% step %} **Alert Cashier** The POS alerts the cashier of the fueling authorization request. {% endstep %} {% step %} **Place Nozzle** The customer places the nozzle in the tank. {% endstep %} {% step %} **Receive Payment Information** The POS receives payment information from the MWGT. {% endstep %} {% step %} **Approve Fueling** The POS approves the dispenser for fueling. {% endstep %} {% step %} **Disable Cashier Approval** The POS disables the cashier approval of the dispenser. {% endstep %} {% step %} **Fuel and Hang Up** The customer dispenses the fuel and hangs up the nozzle. {% endstep %} {% endstepper %} --- # 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/feature-references/feature-references/orpak-avi-rfid-fueling.md?ask= ``` 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.