Outdoor EMV transactions must utilize Quick Chip. Quick Chip is automatically enabled within the software configuration once the supported Base software (Base 51) has been loaded. Quick Chip changes the flow of transactions inside the store, prompting the customer to remove their card prior to selecting OK for the total. ``` {% hint style="warning" %} *Outdoor EMV transactions must utilize Quick Chip. Quick Chip is automatically enabled within the software configuration once the supported Base software (Base 51) has been loaded. Quick Chip changes the flow of transactions inside the store, prompting the customer to remove their card prior to selecting OK for the total.* *As part of the installation, prior to leaving the store, notify the store personnel that the transaction flow on the PIN pad has changed. Failure to complete the transaction on the PIN pad will result in the card not being charged for the transaction.* *Do not disable quick chip for outdoor EMV locations!* {% endhint %} {% hint style="info" %} Shell Vantage sites do not need to have the Quick Chip feature enabled in the Commander software. {% endhint %} The screenshot below shows where to enable Quick Chip in Configuration Manager. ![](/files/2052bcae6eb0e7e84e1396af5162424c8eba1925) ### EMV Network Communication #### Verifone Gilbarco FlexPay™ CRIND The Verifone Commander Site Controller establishes outbound connections to the Gilbarco FlexPay™ CRIND. Verifone Commander is the TCP client and the Gilbarco dispenser are the listening server. EMV port 4871 is used for TLS communications with the Gilbarco FlexPay™ CRINDs. The network communication between the Verifone zone and the outdoor EMV VLAN is controlled by the Managed Network Service Provider (MNSP). #### Wayne iX Pay™ CAT The Wayne iX Pay CAT establishes outbound connections to the Verifone Commander. Wayne dispenser is the TCP client and the Verifone Commander is the listening server. EMV port 9700 is used for TLS communications with Wayne iX Pay CAT. The network communication between the Verifone zone and the outdoor EMV VLAN is controlled by the Managed Network Service Provider (MNSP). #### Bennett Simply Secure Payment (SSP) The Bennett SSP establishes outbound connections to the Verifone Commander. Bennett SSP is the TCP client and the Verifone Commander is the listening server. EMV port 9700 is used for TLS communications with Bennett SSP. The network communication between the Verifone zone and the outdoor EMV VLAN is controlled by the Managed Network Service Provider (MNSP). #### Invenco G6 OPT The Invenco G6 OPT establishes outbound connections to the Verifone Commander. Invenco G6 OPT is the TCP client and the Verifone Commander is the listening server. EMV port 9700 is used for TLS communications with Invenco G6 OPT. The network communication between the Verifone zone and the outdoor EMV VLAN is controlled by the Managed Network Service Provider (MNSP). ### Pre-Install Checklist for EMV Readiness The following steps are expected to be configured prior to setting up Outdoor EMV on Commander. It is the responsibility of the pump technician to complete this configuration. {% hint style="danger" %} IP Address for the Gilbarco CRIND and Wayne CAT CANNOT be on Verifone subnet. Consult IP scheme recommended by the dispenser manufacturer if it has not been pre-identified by the site. {% endhint %}

Select All	Managed Network Service Provider (MNSP)
	Acquire/Install MNSP solution (See Appendix A)

Select All	Gilbarco® Dispenser
	Verify with the Network if Gilbarco dispensers are EMV Contact certified and EMV Contactless certified. Make sure to configure accordingly as Noted in the DCR Configuration section. Also, see Outdoor EMV Implementation Status.
	Verify EMV ready card reader hardware (HCR/UX 300)
	Hardware needed for IP connectivity to CRIND (BRCM/DCM)
	CRIND IP Addresses
	Pump Router IP Address (Check with MNSP if required)
	Install required EMV CRIND software
	Install TLS Certification (Required for FlexPay II)
	Set Single-Auth setting
	Change POS COM from SERIAL to IP

Select All	Wayne Dispenser Requirements
	Verify with the Network if Wayne dispensers are EMV Contact certified and EMV Contactless certified. Make sure to configure accordingly as Noted in the DCR Configuration section. Also, see Outdoor EMV Implementation Status.
	Verify iX Pay card reader (iX Pay II currently not supported)
	Load Minimum CAT software prior to IP software
	Using Wayne iX Configuration Tool, build/load Minimum EMV CAT software
	Hardware needed for IP connectivity to dispenser (Wayne Connect IP-485S)
	CAT IP Addresses
	Pump Router IP Address (Check with MNSP if required)

Select All	Bennett Dispenser Requirements
	Verify with the Network if Bennett SSPs are EMV Contact certified and EMV Contactless certified. Make sure to configure accordingly as Noted in the DCR Configuration section. Also, see Outdoor EMV Implementation Status.
	Verify EMV ready card reader hardware
	Install required EMV DCR software

Select All	Invenco Dispenser Requirements
	Verify with the Network if Invenco OPTs are EMV Contact certified and EMV Contactless certified. Make sure to configure accordingly as Noted in the DCR Configuration section. Also, see Outdoor EMV Implementation Status.
	Verify EMV ready card reader hardware
	Hardware needed for IP connectivity to DCR
	DCR IP Addresses
	Pump Router IP Address (Check with MNSP if required)
	Install required EMV DCR software

### Order of Upgrade/Install Checklist The general steps for the implementation of Outdoor EMV is outlined below. Do not proceed with the installation if the site is experiencing other issues such as not being able to process cards.

#	Select All	Order of Upgrade/Install Checklist
1.		Verify site is functional and Indoor EMV is operational
2.		Perform any site backups and close daily. Ensure the site's transactions are received by the network before completing any software reloads or upgrades.
3.		Upgrade POS/PIN Pad software (Auto-Upgrade recommended)
	If an Auto Upgrade is being completed, see the Auto Upgrade Feature Reference Manual.
4.		Verify Payment Network Communication for indoor (EMV) and outdoor (Swipe) card transactions after upgrading the software.
5.		Verify that Pre-install Checklist for EMV Readiness has been completed.
6.		Configure hardware wiring (i.e. Re-wiring Ethernet cables, replacing routers with MNSP, etc.)
	DO NOT rewire the Gilbarco BRCM or Wayne Connect from the existing 2-wire loops media connection. Outdoor EMV TCP/IP packets will be sent on the existing 2-wires and converted back in the dispenser same as the media.
7.		LAN Configuration in POS for site specific outdoor EMV topology (i.e. Adding routes)
8.		Enable/Configure POS for outdoor EMV DCR.
9.		Verify Payment Network Communication for EMV indoor/ outdoor card transactions.

### Network Topology Configuration {% hint style="info" %} It is important that the site networking and routing changes have been completed prior to making changes to the Configuration Client. Contact the site MNSP for the outdoor EMV network topology. Also, for more information regarding Network Topology Configurations, see the following Appendices: •Appendix A - Documentation •Appendix B - Support •Appendix C - Diagrams {% endhint %} {% hint style="warning" %} The Customer/Site area is owned, managed and configured by the MNSP network administrator. Installer should ensure there is a bi-directional communication to and from the Forecourt between the VFI network and CRIND/CAT network before beginning installation. Failure to do so will result in issues during setup. {% endhint %} ## CONFIGURING GILBARCO {% hint style="danger" %} The following steps are for configuring POS for Gilbarco CRIND. Before starting the conversion of the outdoor EMV, make sure that Pre-Install Checklist for EMV Readiness has been completed. Before configuring Commander Configuration Client, follow the steps in setting up the networking communication that is identified for the site by the MNSP. {% endhint %} ### Configuring EMV in Configuration Client By default, the Commander is installed with EMV disabled. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. ### Configuration Client Access {% hint style="info" %}

For Shell branded sites, the EPS controls the configuration of roles below. {% endhint %} ### Accessing EMV Configuration If this is a new Production Signed software installation, all menu selections to configure the system for EMV transaction processing are immediately visible and available. If the software is being updated for EMV-readiness from a prior installation, user permissions must be updated to allow access to the EMV menu selections. If accessing the Configuration Client from the POS and the EMV Configuration and Initialization tabs are grayed out, then this indicates the logged in user account does not have the correct functions added to the associated role. Activate the following roles for the user accessing Configuration Client at ConfigClient.html.

1. *Navigate to Security > Manage Users > Configure Roles.* 2. Select Role (i.e. Manager). 3. Select Edit. 4. Check the following Functions: \ \* uemvcfg - Update EMV Configuration \ \* uemvinit - Update EMV Initialization \ \* vemvcfg - View EMV Configuration \ \* vemvinit - View EMV Initialization 5. Logout of the Configuration Client and log back in for the Role changes to take effect. ### Outdoor EMV Configuration for Gilbarco CRIND #### Managed Modules 1. Navigate to **Tools > Managed Modules > Current Configuration**. 2. At Host Names, select sitecontroller. 3. At Select Module, choose the DCR Driver option. 4. Select the DCR Channel to set up.

All IP enabled DCR, the DCR should be placed on the same channel (i.e. DCR Channel 01). There is no advantage to splitting up the channels.

5. For each DCR Channel for EMV, select: 1. Enable option must be checked. 2. IP Enabled option must be checked. 3. Port Name option must remain empty.\ **NOTE:** EMV communications is done via the Ethernet port on the Commander, therefore the DCR Channel Port Name will be left blank. There will be no LED lights for DCR on the front of the Commander since the communications is via the Ethernet port. 1. DCR Family type selection is Gilbarco. 4. DCR Family type selection is Gilbarco.

5. Save DCR Driver changes. **Note:** If both IP Enabled and Port Name parameters are selected, an error displays when attempting to save the configuration changes.

6. After completing the DCR Channel set-up, select DCR Positions option and assign CRIND positions to their respective DCR. {% hint style="info" %} If the site is an Auto-Upgrade and has multiple channels configured, reconfigure all the DCR Positions on a single channel (i.e. Channel 01). {% endhint %}

#### DCR Configuration The following EMV specific parameters are required for each EMV DCR/CRIND position: Navigate to **Configuration Client > Forecourt > DCR**. {% hint style="info" %} In order for NFC Readers to accept mobile device payments, make sure Contactless is not disabled at **Configuration Client > Forecourt > DCR > DCR Configuration > DCR Position Attributes > NFC Mode**. {% endhint %}

1. Select DCR Position Attributes. 2. Under EMV Parameters section for each of the Selected EMV DCR Position: 1. Enable EMV must be checked. 2. IP Address must be entered.\ **NOTE:** *IP Address for the EMV CRIND CANNOT be on a Verifone subnet.*\ **NOTE:** *Consult IP scheme recommended by Gilbarco if it has not been pre-identified by the site.* 3. Port value is 4871. 4. For NFC Mode, select one of the following: \ \* Contactless Disabled -- Contactless (including Mobile Payments) is not being used at the DCR. \ \* Contactless MSD Enabled -- Use only if Contactless EMV is not supported or not certified for Gilbarco dispensers. This mode uses the Mag-Stripe Data (MSD). \ \* Contactless EMV Enabled -- Use if Contactless EMV is supported and network certified for Gilbarco dispensers. This mode uses the chip data on the card. 3. In the Other Parameters section, select the appropriate parameter configurations and click Save. #### DCR Keys Configuration DCR key mapping is necessary for the PIN pad to respond correctly to customer key presses. 1. Navigate to **Configuration Client > Forecourt > DCR Keys**. ![](/files/cadf7f4b625ad0496427153575ec97573e386cb2) Create a DCR Keys layout by clicking on Add for Gilbarco DCRs below. **Gilbarco DCRs:** * **Label:** Gilbarco EMV * **#Rows:** 4 * **#Columns:** 6 ![](/files/6ffe64a2ab693a73ac225a88b6058e09f379185c) 1. Select a (NA) square and configure the Key type for the DCR: 1. Key Type: Function 2. Function Key Code: (As shown in the images above for the site EMV key pads)

2. Select Assign Positions and Select DCR Position(s) to all the DCRs and click Save.

3. Click Save at DCR Keys Configuration.

4. Navigate to **Configuration Client > Tools > Refresh Configuration**.

### Local Area Network Configuration The LAN needs to be configured for Gilbarco CRIND. In the Gilbarco configuration, the Commander is the CLIENT and the Gilbarco CRIND is the SERVER. The Outdoor EMV DCR IP traffic must be routed from Commander through the network IP of 192.168.31.31. Depending on which device specific IP configuration is selected for the site. Device Specific network routes might need to be added. {% hint style="info" %}

For Shell branded sites, see Appendix D at the back of the document for Shell Verifone Zone settings. {% endhint %} #### Isolated Payment NIC 1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration. 2. Click on Isolated Payment NIC in the Device Specific IP Configuration. 3. Verify with your network provider if the "Default Route" parameter needs to be checked. If the parameter is checked, then continue with the next steps. If not checked, then skip to the EPS Global Configuration Section.

{% hint style="info" %} Using the IP address entered in the EMV Parameter in DCR configuration, add a network destination route with the 4th octet (last) set to ZERO. i.e. 10.5.55.0. This should cover all the IP ranges from 10.5.55.1 through10.5.55.255. {% endhint %} If Default Route is checked, then add New Route Config to the Device Specific Routes per site. * **Route Type**: Network * EMV Parameter IP Address (Forecourt > DCR > DCR Position Attributes) with the 4th octet set to 0. * **Gateway**: 192.168.31.31 * **Netmask**: 255.255.255.0 ![](/files/b976924d79fe57aaf031c4002edfe04d40c6d838) Save the configuration changes and reboot Verifone Commander. #### EPS Global Configuration {% hint style="info" %} For Shell branded sites, EPS Global Configuration is controlled by Wincor. This should be pre-configured and enabled prior to converting the site for outdoor EMV. No changes are needed in EPS Global Configuration. Proceed to Fuel and DCR Initialization.The EMV Configuration tab of the EPS Global Configuration screen contains options for both inside and outside EMV use. {% endhint %} The EMV Configuration tab of the EPS Global Configuration screen contains options for both inside and outside EMV use. 1. Navigate to **Configuration Client > Payment Controller > EPS Global Configuration > EMV Configuration**.

2. From the Config Type drop down menu, select OUTSIDE. 3. In the Terminal Configuration section and from the EMV Enable Status drop down menu, select the parameter CONTACT or CONTACT AND CONTACTLESS. 4. Select Save. #### Fuel and DCR Initialization 1. After configuring Managed Modules for Fuel and DCR, perform a Fuel and DCR initialization. 2. Navigate to Configuration Client > Tools > Refresh Configuration. 3. To initialize Fuel, navigate to **Configuration Client > Forecourt > Initialization** and then select Fuel.

4. A message stating Fuel Initialization Successfully Sent displayed. Select Ok.

5. To initialize the Fuel Driver, navigate to Configuration Client > Forecourt > Initialization and then select Fuel Driver.

6. A message stating Fuel Driver Initialization Successfully Sent displayed. Select Ok.

7. To initialize DCR Driver, navigate to Configuration Client > Forecourt > Initialization and then select DCR Driver.

8. A message stating DCR Driver Initialization Successfully Sent displayed. Select Ok.

{% hint style="danger" %} Check the dispensers to verify that they are loaded. After the dispensers are all loaded, perform second DCR Driver initialization. {% endhint %} #### EMV Initialization {% hint style="danger" %} For Shell branded sites, Shell will enable Outdoor EMV on the Wincor device prior to the EMV installation. EMV Initialization is controlled by Wincor. This should take place when Wincor and Commander sync and exchange information. {% endhint %} After Commander has established communications with the Gilbarco FlexPay™ CRIND positions, it will require an EMV Initialization to be performed. This action sends required Gilbarco EMV resource files to the selected CRIND positions. {% hint style="info" %} A DCR Driver Initialization must have been performed before starting the following steps. This will add DCR IDs to the Available POP List which can then be selected to receive the EMV Initialization. An EMV Initialization does not perform a DCR Driver Initialization or a DCR Initialization. {% endhint %} 1. Navigate to the **Configuration Client > Payment Controller > EPS Global Configuration > EMV Initialization**. 2. From the Initialize POP section locate the Available POP List. 3. For the CRIND(s) requiring initialization, select the required CRIND ID and click the Add >> button to move it to the Selected POP List.

Outdoor card readers will be identified as POP 101, 102, 103, etc.

4. Repeat steps 2 and 3 for any additional CRIND IDs.

5. When finished selecting POP positions to be initialized, click Save. This performs an EMV POP initialization of the selected CRIND positions. 6. If another EMV Initialization is required, first perform a Refresh Configuration. 7. Navigate to **Configuration Client > Tools > Refresh Configuration**. This updates the Available POP List contents. Repeat the EMV Initialization steps 1 through 5 above.

#### Verification of Forecourt Status Use the following steps to verify IP based communications to the DCRs. Navigate to Configuration Client > Tools > Helpdesk Diagnostics > Forecourt. The DCR Status should appear as "Online." If they are offline, then communications to the DCRs have not been established. Recheck the connections and verify TCP/IP connectivity.

## CONFIGURING WAYNE {% hint style="danger" %} The following steps are for configuring POS for Wayne. Before starting the conversion of the outdoor EMV, make sure that Pre-Install Checklist for EMV Readiness has been completed. Before configuring Commander Configuration Client, follow the steps in setting up the networking communication that is identified for the site by the MNSP. {% endhint %} ### Configuring EMV in Configuration Client By default, the Commander is installed with EMV disabled. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. ### Configuration Client Access {% hint style="info" %}

1. *Navigate to Security > Manage Users > Configure Roles.* 2. Select Role (i.e. Manager). 3. Select Edit. 4. Check the following Functions: \ \* uemvcfg - Update EMV Configuration \ \* uemvinit - Update EMV Initialization \ \* vemvcfg - View EMV Configuration \ \* vemvinit - View EMV Initialization 5. Logout of the Configuration Client and log back in for the Role changes to take effect. ### Outdoor EMV Configuration for Wayne iX Pay CAT #### Managed Modules 1. Navigate to **Tools > Managed Modules > Current Configuration**. 2. At Host Names, select sitecontroller. 3. At Select Module, choose the DCR Driver option. 4. Select the DCR Channel to set up.

All IP enabled DCR, the DCR should be placed on the same channel (i.e. DCR Channel 01). There is no advantage to splitting up the channels.

5. For each DCR Channel for EMV, select: 1. Enable option must be checked. 2. IP Enabled option must be checked. 3. Port Name option must remain empty.\ **NOTE:** *EMV communications is done via the Ethernet port on the Commander, therefore the DCR Channel Port Name will be left blank.* *There will be no LED lights for DCR on the front of the Commander since the communications is via the Ethernet port.* 4. DCR Family type selection is Wayne.

5. Save DCR Driver changes. **Note:** *If both IP Enabled and Port Name parameters are selected, an error displays when attempting to save the configuration changes.*

1. Select DCR Position Attributes. 2. Under EMV Parameters section for each of the Selected EMV DCR Position: 1. Enable EMV must be checked. 2. IP Address must be left blank. 3. Port must be left blank. 4. For NFC Mode, select one of the following: \ \* Contactless Disabled -- Contactless (including Mobile Payments) is not being used at the DCR. \ \* Contactless MSD Enabled -- Use only if Contactless EMV is not supported or not certified for Gilbarco dispensers. This mode uses the Mag-Stripe Data (MSD). \ \* Contactless EMV Enabled -- Use if Contactless EMV is supported and network certified for Gilbarco dispensers. This mode uses the chip data on the card. 3. In the Other Parameters section, select the appropriate parameter configurations and click Save. {% hint style="warning" %} *IP Address and Port should be left blank for Wayne Configuration.* {% endhint %} #### DCR Keys Configuration DCR key mapping is necessary for the PIN pad to respond correctly to customer key presses. Navigate to **Configuration Client > Forecourt > DCR Keys**. ![](/files/cadf7f4b625ad0496427153575ec97573e386cb2) Create a DCR Keys layout by clicking on Add for Wayne DCRs below. **Wayne DCRs:** * **Label:** Wayne EMV * **#Rows:** 4 * **#Columns:** 5 {% hint style="info" %} *The two right-hand columns, outlined in green below, are left blank. They are programmed internally in the Commander software.* {% endhint %}

1. Select Assign Positions and Select DCR Position(s) to all the DCRs and click Save.

2. Click Save at DCR Keys Configuration.

3. Navigate to **Configuration Client > Tools > Refresh Configuration**.

{% hint style="info" %} *Using the Wayne DCR IP addresses, add a Network Destination Route with the 4th octet (last) set to ZERO. i.e. if the DCR IP addresses were 172.29.1.1. to 172.29.1.10, then the IP address used for this route would be 172.29.1.0.* {% endhint %} If Default Route is checked, then add New Route Config to the Device Specific Routes per site. * **Route Type**: Network * Enter in the IP address used for the DCRs with the last octet set to 0. See the note above for more details. * **Gateway**: 192.168.31.31 * **Netmask**: 255.255.255.0

Save the configuration changes and reboot Verifone Commander. #### EPS Global Configuration {% hint style="warning" %}

For Shell branded sites, EPS Global Configuration is controlled by Wincor. This should be pre-configured and enabled prior to converting the site for outdoor EMV. No changes are needed in EPS Global Configuration. Proceed to Fuel and DCR Initialization. {% endhint %} The EMV Configuration tab of the EPS Global Configuration screen contains options for both inside and outside EMV use. 1. Navigate to **Configuration Client > Payment Controller > EPS Global Configuration > EMV Configuration**.

4. A message stating Fuel Initialization Successfully Sent displayed. Select Ok.

5. To initialize the Fuel Driver, navigate to Configuration Client > Forecourt > Initialization and then select Fuel Driver.

6. A message stating Fuel Driver Initialization Successfully Sent displayed. Select Ok.

7. To initialize DCR Driver, navigate to Configuration Client > Forecourt > Initialization and then select DCR Driver.

8. A message stating DCR Driver Initialization Successfully Sent displayed. Select Ok.

For Shell branded sites, Shell will enable Outdoor EMV on the Wincor device prior to the EMV installation. EMV Initialization is controlled by Wincor. This should take place when Wincor and Commander sync and exchange information. {% endhint %} After the Commander has established communications with the Wayne DCR positions, it is required to perform an EMV Initialization. {% hint style="info" %} A DCR Driver Initialization must have been performed before starting the following steps. This will add DCR IDs to the Available POP List which can then be selected to receive the EMV Initialization. An EMV Initialization does not perform a DCR Driver Initialization or a DCR Initialization. {% endhint %} 1. Navigate to the **Configuration Client > Payment Controller > EPS Global Configuration > EMV Initialization**. 2. From the Initialize POP section locate the Available POP List. 3. For the DCR(s) requiring initialization, select the required DCR ID and click the **Add >>** button to move it to the Selected POP List.

Outdoor card readers will be identified as POP 101, 102, 103, etc.

4. Repeat steps 2 and 3 for any additional DCR IDs.

5. When finished selecting POP positions to be initialized, click Save. This performs an EMV POP initialization of the selected DCR positions. 6. If another EMV Initialization is required, first perform a Refresh Configuration. 7. Navigate to **Configuration Client > Tools > Refresh Configuration**. This updates the Available POP List contents. Repeat the EMV Initialization steps 1 through 5 above.

## CONFIGURING BENNETT {% hint style="danger" %} The following steps are for configuring POS for Bennett. Before starting the conversion of the outdoor EMV, make sure that Pre-Install Checklist for EMV Readiness has been completed. Before configuring Commander Configuration Client, follow the steps in setting up the networking communication that is identified for the site by the MNSP. {% endhint %} ### Configuring EMV in Configuration Client By default, the Commander is installed with EMV disabled. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. ### Configuration Client Access {% hint style="info" %} For Shell branded sites, the EPS controls the configuration of roles below. {% endhint %} ### Accessing EMV Configuration If this is a new Production Signed software installation, all menu selections to configure the system for EMV transaction processing are immediately visible and available. If the software is being updated for EMV-readiness from a prior installation, user permissions must be updated to allow access to the EMV menu selections. If accessing the Configuration Client from the POS and the EMV Configuration and Initialization tabs are grayed out, then this indicates the logged in user account does not have the correct functions added to the associated role. Activate the following roles for the user accessing Configuration Client at ConfigClient.html.

1. *Navigate to Security > Manage Users > Configure Roles.* 2. Select Role (i.e. Manager). 3. Select Edit. 4. Check the following Functions: \ \* uemvcfg - Update EMV Configuration \ \* uemvinit - Update EMV Initialization \ \* vemvcfg - View EMV Configuration \ \* vemvinit - View EMV Initialization 5. Logout of the Configuration Client and log back in for the Role changes to take effect. ### Outdoor EMV Configuration for Bennett SSP #### Managed Modules 1. Navigate to **Tools > Managed Modules > Current Configuration**. 2. At Host Names, select sitecontroller. 3. At Select Module, choose the DCR Driver option. 4. Select the DCR Channel to set up.

All IP enabled DCR, the DCR should be placed on the same channel (i.e. DCR Channel 01). There is no advantage to splitting up the channels.

5. Save DCR Driver changes. **Note:** *If both IP Enabled and Port Name parameters are selected, an error displays when attempting to save the configuration changes.*

#### DCR Configuration The following EMV specific parameters are required for each EMV DCR position: Navigate to **Configuration Client > Forecourt > DCR**. {% hint style="info" %} In order for NFC Readers to accept mobile device payments, make sure Contactless is not disabled at **Configuration Client > Forecourt > DCR > DCR Configuration > DCR Position Attributes > NFC Mode**. {% endhint %}

1. Select DCR Position Attributes. 2. Under EMV Parameters section for each of the Selected EMV DCR Position: 1. Enable EMV must be checked. 2. IP Address must be left blank. 3. Port must be left blank. 4. For NFC Mode, select one of the following: \ \* Contactless Disabled -- Contactless (including Mobile Payments) is not being used at the DCR. \ \* Contactless MSD Enabled -- Use only if Contactless EMV is not supported or not certified for Gilbarco dispensers. This mode uses the Mag-Stripe Data (MSD). \ \* Contactless EMV Enabled -- Use if Contactless EMV is supported and network certified for Gilbarco dispensers. This mode uses the chip data on the card. 3. In the Other Parameters section, select the appropriate parameter configurations and click Save. {% hint style="warning" %} *IP Address and Port should be left blank for Bennett Configuration.* {% endhint %} #### DCR Keys Configuration DCR key mapping is necessary for the PIN pad to respond correctly to customer key presses. Navigate to **Configuration Client > Forecourt > DCR Keys**. ![](/files/cadf7f4b625ad0496427153575ec97573e386cb2) Create a DCR Keys layout by clicking on Add for Bennett SSPs below. **Bennett SSPs:** * **Label:** Bennett EMV * **#Rows:** 4 * **#Columns:** 5 {% hint style="info" %} *The two right-hand columns, outlined in green below, are left blank. They are programmed internally in the Commander software.* {% endhint %}

1. Select Assign Positions and Select DCR Position(s) to all the DCRs and click Save.

2. Click Save at DCR Keys Configuration.

3. Navigate to **Configuration Client > Tools > Refresh Configuration**.

### Local Area Network Configuration {% hint style="info" %} *Verify Gateway IP addresses have been setup for EMV and the MNSP (Switch) Vendor has pushed the correct rules and polices.* {% endhint %} The LAN is required to be configured for Bennett SSP. In the Bennett configuration, the Commander is the SERVER and the Bennett SSP is the CLIENT. The Outdoor EMV DCR IP traffic must be routed from the Commander through the Network IP Address 192.168.31.31. Depending on which Device Specific IP Configuration is selected for the site, Device Specific Network Routes may need to be added. #### Isolated Payment NIC 1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration. 2. Click on Isolated Payment NIC in the Device Specific IP Configuration. 3. Verify with your network provider if the "Default Route" parameter needs to be checked. If the parameter is checked, then continue with the next steps. If not checked, then skip to the EPS Global Configuration Section.

{% hint style="info" %} *Using the Bennett SSP IP addresses, add a Network Destination Route with the 4th octet (last) set to ZERO. i.e. if the DCR IP addresses were 172.29.1.1. to 172.29.1.10, then the IP address used for this route would be 172.29.1.0.* {% endhint %} If Default Route is checked, then add New Route Config to the Device Specific Routes per site. * **Route Type**: Network * b. Enter in the IP address used for the DCRs with the last octet set to 0. See the note above for more details. * **Gateway**: 192.168.31.31 * **Netmask**: 255.255.255.0

Save the configuration changes and reboot Verifone Commander. #### EPS Global Configuration The EMV Configuration tab of the EPS Global Configuration screen contains options for both inside and outside EMV use. 1. Navigate to **Configuration Client > Payment Controller > EPS Global Configuration > EMV Configuration**.

4. A message stating Fuel Initialization Successfully Sent displayed. Select Ok.

5. To initialize the Fuel Driver, navigate to Configuration Client > Forecourt > Initialization and then select Fuel Driver.

6. A message stating Fuel Driver Initialization Successfully Sent displayed. Select Ok.

7. To initialize DCR Driver, navigate to Configuration Client > Forecourt > Initialization and then select DCR Driver.

8. A message stating DCR Driver Initialization Successfully Sent displayed. Select Ok.

{% hint style="danger" %} Check the dispensers to verify that they are loaded. After the dispensers are all loaded, perform second DCR Driver initialization. *Again, check the dispensers to verify that they are loaded. Perform EMV transaction. If loaded and unable to perform an Outdoor EMV transactions, then go to next step.* {% endhint %} #### EMV Initialization After the Commander has established communications with the Bennett SSP positions, it is required to perform an EMV Initialization. {% hint style="info" %} A DCR Driver Initialization must have been performed before starting the following steps. This will add DCR IDs to the Available POP List which can then be selected to receive the EMV Initialization. An EMV Initialization does not perform a DCR Driver Initialization or a DCR Initialization. {% endhint %} 1. Navigate to the **Configuration Client > Payment Controller > EPS Global Configuration > EMV Initialization**. 2. From the Initialize POP section locate the Available POP List. 3. For the CRIND(s) requiring initialization, select the required CRIND ID and click the **Add >>** button to move it to the Selected POP List.

Outdoor card readers will be identified as POP 101, 102, 103, etc.

4. Repeat steps 2 and 3 for any additional DCR IDs.

## CONFIGURING INVENCO {% hint style="danger" %} The following steps are for configuring POS for Invenco. Before starting the conversion of the outdoor EMV, make sure that Pre-Install Checklist for EMV Readiness has been completed. Before configuring Commander Configuration Client, follow the steps in setting up the networking communication that is identified for the site by the MNSP. {% endhint %} ### Configuring EMV in Configuration Client By default, the Commander is installed with EMV disabled. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. The following section provides instructions on how to enable Outside EMV for the Commander Site Controller. ### Configuration Client Access ### Accessing EMV Configuration If this is a new Production Signed software installation, all menu selections to configure the system for EMV transaction processing are immediately visible and available. If the software is being updated for EMV-readiness from a prior installation, user permissions must be updated to allow access to the EMV menu selections. If accessing the Configuration Client from the POS and the EMV Configuration and Initialization tabs are grayed out, then this indicates the logged in user account does not have the correct functions added to the associated role. Activate the following roles for the user accessing Configuration Client at ConfigClient.html.

1. *Navigate to Security > Manage Users > Configure Roles.* 2. Select Role (i.e. Manager). 3. Select Edit. 4. Check the following Functions: \ \* uemvcfg - Update EMV Configuration \ \* uemvinit - Update EMV Initialization \ \* vemvcfg - View EMV Configuration \ \* vemvinit - View EMV Initialization 5. Logout of the Configuration Client and log back in for the Role changes to take effect. ### Outdoor EMV Configuration for Invenco OPT #### Managed Modules 1. Navigate to **Tools > Managed Modules > Current Configuration**. 2. At Host Names, select sitecontroller. 3. At Select Module, choose the DCR Driver option. 4. Select the DCR Channel to set up.

All IP enabled DCR, the DCR should be placed on the same channel (i.e. DCR Channel 01). There is no advantage to splitting up the channels.

5. Save DCR Driver changes. **Note:** *If both IP Enabled and Port Name parameters are selected, an error displays when attempting to save the configuration changes.*

1. Select DCR Position Attributes. 2. Under EMV Parameters section for each of the Selected EMV DCR Position: 1. Enable EMV must be checked. 2. IP Address must be left blank. 3. Port must be left blank. 4. For NFC Mode, select one of the following: \ \* Contactless Disabled -- Contactless (including Mobile Payments) is not being used at the DCR. \ \* Contactless MSD Enabled -- Use only if Contactless EMV is not supported or not certified for Gilbarco dispensers. This mode uses the Mag-Stripe Data (MSD). \ \* Contactless EMV Enabled -- Use if Contactless EMV is supported and network certified for Gilbarco dispensers. This mode uses the chip data on the card. 3. In the Other Parameters section, select the appropriate parameter configurations and click Save. {% hint style="info" %} *IP Address and Port should be left blank for Invenco Configuration.* {% endhint %} #### DCR Keys Configuration DCR key mapping is necessary for the PIN pad to respond correctly to customer key presses. Navigate to **Configuration Client > Forecourt > DCR Keys**. ![](/files/cadf7f4b625ad0496427153575ec97573e386cb2) Create a DCR Keys layout by clicking on Add for Invenco OPTs below. **Invenco OPTs:** * **Label:** Invenco EMV * **#Rows:** 4 * **#Columns:** 5 {% hint style="info" %} *The two right-hand columns, outlined in green below, are left blank. They are programmed internally in the Commander software.* {% endhint %}

1. Select Assign Positions and Select DCR Position(s) to all the DCRs and click Save.

2. Click Save at DCR Keys Configuration.

3. Navigate to **Configuration Client > Tools > Refresh Configuration**.

### Local Area Network Configuration {% hint style="info" %} *Verify Gateway IP addresses have been setup for EMV and the MNSP (Switch) Vendor has pushed the correct rules and polices.* {% endhint %} The LAN needs to be configured for Gilbarco CRIND. In the Gilbarco configuration, the Commander is the CLIENT and the Gilbarco CRIND is the SERVER. The Outdoor EMV DCR IP traffic must be routed from Commander through the network IP of 192.168.31.31. Depending on which device specific IP configuration is selected for the site. Device Specific network routes might need to be added. #### Isolated Payment NIC 1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration. 2. Click on Isolated Payment NIC in the Device Specific IP Configuration. 3. Verify with your network provider if the "Default Route" parameter needs to be checked. If the parameter is checked, then continue with the next steps. If not checked, then skip to the EPS Global Configuration Section.

{% hint style="info" %} *Using the Invenco DCR IP addresses, add a Network Destination Route with the 4th octet (last) set to ZERO. i.e. if the DCR IP addresses were 172.29.1.1. to 172.29.1.10, then the IP address used for this route would be 172.29.1.0.* {% endhint %} If Default Route is checked, then add New Route Config to the Device Specific Routes per site. * **Route Type**: Network * Enter in the IP address used for the DCRs with the last octet set to 0. See the note above for more details. * **Gateway**: 192.168.31.31 * **Netmask**: 255.255.255.0

4. A message stating Fuel Initialization Successfully Sent displayed. Select Ok.

5. To initialize the Fuel Driver, navigate to Configuration Client > Forecourt > Initialization and then select Fuel Driver.

6. A message stating Fuel Driver Initialization Successfully Sent displayed. Select Ok.

7. To initialize DCR Driver, navigate to Configuration Client > Forecourt > Initialization and then select DCR Driver.

8. A message stating DCR Driver Initialization Successfully Sent displayed. Select Ok.

{% hint style="danger" %} Check the dispensers to verify that they are loaded. After the dispensers are all loaded, perform second DCR Driver initialization. *Again, check the dispensers to verify that they are loaded. Perform EMV transaction. If loaded and unable to perform an Outdoor EMV transactions, then go to next step.* {% endhint %} #### EMV Initialization After the Commander has established communications with the Invenco DCR positions, it is required to perform an EMV Initialization. {% hint style="info" %} A DCR Driver Initialization must have been performed before starting the following steps. This will add DCR IDs to the Available POP List which can then be selected to receive the EMV Initialization. An EMV Initialization does not perform a DCR Driver Initialization or a DCR Initialization. {% endhint %} 1. Navigate to the **Configuration Client > Payment Controller > EPS Global Configuration > EMV Initialization**. 2. From the Initialize POP section locate the Available POP List. 3. For the CRIND(s) requiring initialization, select the required CRIND ID and click the Add >> button to move it to the Selected POP List.

Outdoor card readers will be identified as POP 101, 102, 103, etc.

4. Repeat steps 2 and 3 for any additional CRIND IDs.

## TROUBLESHOOTING GILBARCO DISPENSERS {% hint style="info" %} The information in this chapter is for reference only. Contact the Area of Responsibility (AOR) parties for up-to-date information. {% endhint %} ### Gilbarco FlexPay II CRIND #### Verification of TLS Certification The TLS Certification enhances a secure communication between the Gilbarco CRIND and Verifone Commander. Gilbarco FlexPay II CRIND does not always come loaded with a TLS Certification. Using the Advanced FlexPay Maintenance Tool, the TLS Certification can be verified and loaded if necessary. 1. Open the FlexPay Tool and connect to the FlexPay Control Board. 2. Select the TLS tab. 3. Select Show Hierarchy List button.

4. If the TLS Certification is installed, the TLS files will be listed.

5\. If the Certification is not installed, then the error window below displays. Contact Gilbarco for steps and instructions on how to install the TLS Certification in the Gilbarco CRIND. ![](/files/71452b29d2959bdaf4841ee5822a9a0528640777) ### Gilbarco FlexPay II CRIND #### Verification of Single-Auth TLS Mode The TLS Certification enhances the secure communication between the Gilbarco CRIND and Verifone Commander. Gilbarco FlexPay II CRIND does not always come loaded with TLS Certification. Using the Advanced FlexPay Maintenance Tool, the TLS Certification can be verified and loaded if necessary. 1. Reboot the CRIND and enter Service Menu with dispenser password.

2. From the Service Menu, select option <3> Security Setup Menu.

3. Enter Matching Password. This requires a call to Gilbarco TAC.

4. After entering the Security Setup Menu, select <3> Protocol Menu.

5. Verify that option <1> CRIND TLS Authentication is set: ON SINGLE AUTH.

### Gilbarco FlexPay II CRIND #### POS COMM set to IP The outdoor EMV communication from the Verifone Commander to the CRIND is in the TCP/IP protocol. Previously Verifone Commander communicated in a SERIAL protocol. For the CRINDS to accept the TCP/IP protocol, the settings on the CRINDs needs to be changed. Using the Gilbarco Diagnostic, enter into Diagnostic Startup Menu. Press '1' and Enter for Main Menu. ![](/files/04482f185a54f1f83c3873ed3093ef174c805329) Press '1' and Enter for CRIND Config. ![](/files/ce957c8b28f16c979553faa06007d0384a5de7c1) Press '3' and Enter for POS Comm Config. ![](/files/a466b1db8a97deaf383f12caf71d73f340bafea5) 1. Press '1' and Enter to Set POS COMM Mode to IP. ![](/files/d5d9b8632358055e28ec3725547c5fda37c18833) {% hint style="info" %} If the POS Comm Mode is already set to IP, then Cancel out of the POS Comm Config settings. {% endhint %}

After the POS Comm Mode is set to IP, press the Cancel key until back at the Diagnostic Startup Menu.

Press '2' and Enter to Exit the Diagnostics. This will warm reboot the CRINDS. ![](/files/95df9ad3a6a52da04ac4f9d1e604c0b0f1f20429) ### Gilbarco FlexPay IV CRIND #### Verification of Single-Authorization TLS Mode The TLS Certification enhances the secure communication between the Gilbarco CRIND and Verifone Commander. Gilbarco FlexPay II CRIND does not always come loaded with TLS Certification. Using the Advanced FlexPay Maintenance Tool, the TLS Certification can be verified and loaded if necessary. Reboot the CRIND and enter the System Menu. Select <3> App Configuration. ![](/files/8f33c7d3b6b46ab70fad45ca0ec3c7dbefd82bd0) Select <1> CRINDBIOS. ![](/files/866fa91214a758db0ed5213fa7f0c65c7480ec21) Select <1> CRIND. ![](/files/a049419997ead0aed69739bd0866e7f723daf2ac) ![](/files/426cc133853cad9c2d04dceb9ec3f249850f78b6) Verify the following two CRIND Settings: 1. Option <4> INTERFACE: IP 2. Option <5> TLS Mode: SINGLE\_AUTH 3. If they are set, then Press all the way back to the System Menu. ### Gilbarco FlexPay IV CRIND #### Verify IP Interface The outdoor EMV communication from the Verifone Commander to the CRIND is in the TCP/IP protocol. The previously Verifone Commander communicated in a SERIAL protocol. For the CRINDS to accept the TCP/IP protocol, the settings on the CRINDs needs to be changed 1. From the System Menu, select Secure Menu. Call Gilbarco TAC and provide the CHALLENGE ## displayed on the screen for the unit and get the VERIFICATION CODE to enter SECURE MENU. ![](/files/59f72c81bff2d34def75aa1d35830a9a3af888d1) ![](/files/9a57ad8295a356979437f431e9cff8a05acd96d1) After entering Secure Menu, select <2> Network Menu. ![](/files/fb91dd10de7526157911f2ce8e615b58b473a754) Set all the TCP/IP info for the dispenser. ![](/files/3a309c7ac53f77427c74848143d52de27224610d) {% hint style="info" %} IP Address for the EMV CRIND CANNOT be on Verifone subnet. Consult IP scheme recommended by Gilbarco if it has not been pre-identified by the site. {% endhint %} Press \ to set configuration. ### Wayne iX CAT Firmware #### Client/Server Configuration In the Wayne iX CAT Outdoor EMV Configuration, the Verifone POS is the SERVER and the Wayne iX CAT is the CLIENT. The Wayne iX CAT needs to communicate to the Verifone POS on Server PORT 9700. Using the Wayne iXConfigurator tool, set the Client/Server Configuration. ![](/files/ef68ee2e62597a474bdc0cc7cbd6865a8fcce13e) ## GLOSSARY OF TERMS The following terms and definitions will assist with understanding the contents of the Feature Reference. | Term | Definition | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | AAC | Application Authentication Cryptogram. Generated whenever a card declines a transaction. This may be generated at the 1st or 2nd GenAC step. | | AID | Application Identifier, specified by the acquiring host and used to identify the EMV applications that a system can support. Cards and terminals use AIDs to determine which applications are mutually supported, as both the card and the terminal must support the same AID to initiate a transaction. Both cards and terminals may support multiple AIDs. | | ARC | Authorization Response Code indicates the transaction disposition of the transaction received from the issuer for online authorizations. | | ARQC | Authorization Request Cryptogram. Generated by the card when it instructs the system to go online for an approval. An ARQC is generated at the 1st Gen AC step. | | CAPK | Certificate Authority Public Key. The list of keys created by the card issuers used to support EMV cryptographic functions. Each card brand has CAPKs. These keys are loaded into the PIN Pad's during system startup and kept up to date by the system based on data exchanges from the acquiring host. | | Contact EMV | An EMV transaction where the EMV card data is read by inserting a chipped card into the card reader slot on the PIN pad. The card remains inserted in the PIN pad for the duration of the transaction. The PIN pad and the card communicate several times during the course of a transaction. | | Contactless EMV | See NFC, Near Field Communications. | | Term | Definition | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CVM | Cardholder Verification Method. The method that the card instructs the terminal to use in order to validate the cardholder. Consists of online PIN, offline PIN, Signature, and No CVM. | | EMV | Europay, MasterCard, and Visa. The implementation-oriented global specifications regarding the use of chip card technology for the payments industry; established to ensure interoperability and acceptance of payment system Integrated Circuit Cards on a worldwide basis; the acronym refers to the three organizations that initially collaborated on the specification, now maintained by EMVCo. EMV is now analogous with payment cards with embedded security microchips. Within this document EMV is assumed to mean "Inside Contact EMV". | | EMV Kernel | A layer of software, specific to the hardware it is running on that handles the actual communication with the EMV chip on the card. It is versioned, it has an expiration date, and is certified by EMVCo. | | EMV Tag | An EMV identifier. EMV data is maintained in tags - for example 8A and 9F12 are tags representing Authorization Response Code and Application Preferred Name respectively. | | EPS | Electronic Payment Server | | Fallback | Fallback in EMV terms means allowing a magnetic stripe swipe if the chip read fails. See Technical Fallback. | | FEP | Front-End Processor | | First Generate AC or 1st Gen AC | At a high level this is the stage in an EMV transaction where an approval is first requested from the card. Responses can be a TC (approved by the card), ARQC (request to go online for approval) or an AAC (decline). | | Global AID | An AID that is owned by the global/international payment network whose logo is on the card. Global Payment Networks include American Express, Discover, MasterCard and Visa. | | IAD | The Issuer Application Data (IAD) contains proprietary application data for transmission to the issuer in an online transaction. | | ICC | Integrated Chip Card, or Integrated Circuit Card. | | Term | Definition | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Magnetic Stripe Fallback | See Technical Fallback. | | MSA | Merchant Services Account. | | MSD | Magnetic Stripe Data - The term is used to describe the legacy card entry method requiring a swipe of the card to read the magnetic stripe. | | MSP | A merchant services provider (MSP) is an umbrella term that covers banks, third-party processors or any other entity that provides businesses and individuals with the products and services necessary to accept credit cards, debit cards and other forms of electronic payment. | | MSR | Magnetic Swipe Read. | | NFC | Near Field Communications is used to describe an EMV transaction where the EMV card data is read by tapping or waving the card above the PIN pad within the zone, allowing the card and the PIN pad to interact. The card is then removed from the zone and the transaction proceeds with no further Card to PINpad interaction. | | PDL | Parameter Download. Some acquiring hosts supply configuration and other processing data via a PDL. | | PIN | Personal Identification Number. | | POP | Point of Purchase hardware, referring to MX800 Series and MX900 Series PINpads used to read EMV cards. | | POS System | Includes the POS (Point of Sale) terminal(s), site controller and the electronic payment system (EPS). | | Rapid Connect | Rapid Connect is a new payment interface that provides single point integration to all First Data payment platforms including Buypass. | | RCI | Remote Configuration Interface. | | RFID | Radio-Frequency Identification, a process where a transponder chip uses radio waves to communicate between a reader device and the chip. An RFID reader device (in this case, the DCR) transmits a radio pulse to the chip (in a mobile device), which responds with the payment information. | | Term | Definition | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | RID | Registered Application Provider Identifier. The RID is a fixed length unique identifier allocated to each card scheme to identify EMV applications provided by that scheme. The schemes may then suffix this with an optional PIX to further differentiate between multiple products supported by the scheme, and together they form the AID. | | STAN | The System Trace Audit Number which identifies the transaction number processed through the merchant account. | | Stand-in | A process whereby a transaction may be approved locally according to specific transaction criteria even if the system cannot approve a transaction online. | | Table Owner | The entity responsible for maintaining the VIPER tables. Depending on the FEP and the brand, this may be the major oil brand, the processor, Verifone, or a combination of Verifone and brand/processor. | | TC | Transaction Certificate. Generated at the 2nd Gen AC step for approved transactions. | | Technical Fallback | This is the exception process whereby the magnetic stripe, rather than the chip data, is read by an EMV-capable device. | | Terminal ID | The PINpad terminal identifier. | | TPP ID | Third Party Processor ID. This is an ID that uniquely identifies a particular version of a payment application and which also functions as the Project ID during the certification process. It is assigned when the project is created and follows the application through to the production environment. | | TSI | Transaction Status Information. | | TVR | Terminal Verification Results. | | UMF | Universal Message Format. This is the XML based message format specification for the Rapid Connect application. | | U.S. Common Debit AID | An AID that is owned by a global card brand, but can be licensed by a debit network. Discover, MasterCard, and Visa all provide a U.S. Common Debit AID. | | VAP | Value Added Platform. | | VIPER | Verifone's EPS payment processing application. | ## A DOCUMENTATION Any additional documentation required for the installation of outdoor EMV may be found on the Verifone Premier Portal (; Documentation for updating the dispenser equipment can be obtained by the dispenser manufacturer. Managed Network Service Provider documentation may be obtained through the Premier Portal under Manage > Petro Downloads > PC Utilities & Routers. If additional information is needed for the MNSP configuration, please contact the MNSP for this information. ## B SUPPORT ### Contact Information {% hint style="warning" %} The Area of Responsibility (AOR) for customer/site area is owned, managed and configured by the Managed Network Service Provider (MNSP) network administrator. Installer should ensure there is bi-directional communication to and from the Forecourt between the VFI network and Dispenser network before beginning installation. Failure to do so will result in issues during setup. {% endhint %} For installations support, contact appropriate Area of Responsibility (AOR) via listed contact information. The following contact info may be needed during installation: | Verifone POS (AOR) | Phone number | Availability | | ---------------------- | ------------ | ------------ | | Verifone VASC Helpdesk | 888-777-3536 | 24/7 | | Dispenser (AOR) | Phone number | Availability | | --------------- | ----------------------------- | ------------ | | Gilbarco (TAC) | 800-743-7501 | 24/7 | | Wayne/Dover | 800-289-2963 (1 800 AT WAYNE) | | | Invenco | 877-515-0939 | | | Bennett | 800-423-6638 | | | MNSP Network (AOR) | Phone number | Availability | | ---------------------------------- | -------------------------------------- | ------------------------------------ | | Acumera | 512-687-7401 | 24/7 | | AvaLAN | 603-644-1461 Option 1 | 24/7 | | ControlScan | 800-393-3246 | 24/7 | | Cybera | 866-429-2372 Option 1 | 24/7 | | Hughes | 866-350-8786 | 24/7 | | Mako Networks | 844-807-0307 or 636-557-8888 | 24/7 | | Omega | 610-639-7996 or 636-557-8888 | 24/7 | | SageNet | 866-480-2263 or 918-505-2400 | Monday - Friday 8:00am to 6:00pm CST | | Transaction Network Services (TNS) | 866-523-0661 or 800-240-4824, Option 5 | 24/7 | ## C DIAGRAMS ### Gilbarco FlexPay with MNSP (AOR)

### Wayne iX Pay with MNSP (AOR)

### Bennett SSP with MNSP

### Invenco G6 OPT with MNSP

## D SHELL BRANDED SITES ### Gilbarco Local Area Network Configuration The LAN needs to be configured for Gilbarco CRIND. In the Gilbarco configuration, the Commander is the CLIENT and the Gilbarco CRIND is the SERVER. The Outdoor EMV DCR IP traffic must be routed from Commander through the network IP of 192.168.31.31. Depending on which device specific IP configuration is selected for the site. Device Specific network routes might need to be added. {% hint style="danger" %}

For Shell branded sites with two routers MNSP, see Shell Verifone Zone settings below. Follow the Isolated Payment NIC steps for Shell Single MNSP option. {% endhint %} #### Isolated Payment NIC 1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration. 2. Select Isolated Payment NIC in Device Specific IP Configuration. 3. Verify if "Default Route" parameter is checked. If the parameter is checked then, continue to the next steps. If not checked, then skip to EPS Global Configuration Section.

Save the configuration changes and reboot the site controller. #### Verifone Zone (Shell - Two router MNSP LAN Settings) Verify if "Default Route" parameter is checked. If the parameter is checked then continue to next step. ![](/files/ab0d608ed6ace63035c17f605a7d11972c711bb9) ### Wayne Local Area Network Configuration {% hint style="info" %} Verify Gateway IP addresses have been setup for EMV and the MNSP (Switch) Vendor has pushed the correct rules and polices. {% endhint %} The LAN is required to be configured for Wayne CAT. In the Wayne configuration, the Commander is the SERVER and the Wayne CAT is the CLIENT. The Outdoor EMV DCR IP traffic must be routed from the Commander through the Network IP Address 192.168.31.31. Depending on which Device Specific IP Configuration is selected for the site, Device Specific Network Routes may need to be added. {% hint style="warning" %}

For Shell branded sites with two routers MNSP, see Shell Verifone Zone settings below. Follow the Isolated Payment NIC steps for the Shell Single MNSP option. {% endhint %} #### Isolated Payment NIC 1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration. 2. Click on Isolated Payment NIC in the Device Specific IP Configuration. 3. Verify if the "Default Route" parameter is checked. If the parameter is checked, then continue with the next steps. If not checked, then skip to the EPS Global Configuration Section.

{% hint style="info" %} Using the Wayne DCR IP addresses, add a Network Destination Route with the 4th octet (last) set to ZERO. i.e. if the DCR IP addresses were 172.29.1.1. to 172.29.1.10, then the IP address used for this route would be 172.29.1.0. {% endhint %} If the Default Route is checked, then add New Route Config to the Device Specific Routes per site. 1. Route Type: Network 2. Enter in the IP address used for the DCRs with the last octet set to 0. See the note above for more details. 3. Gateway: 192.168.31.31 4. Netmask: 255.255.255.0 ![](/files/7dec9a223bc156c6c989229ee7b62b9b7e8ae26d) Click Save and then reboot the Commander. #### Verifone Zone (Shell - Two router MNSP LAN Settings) Verify if the "Default Route" parameter is checked. If the parameter is checked, then continue with the next section.

--- # 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/emv-outside-emv.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.