> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/pin-pads/implementation-guides/p400/secondary-pin-pad-configuration.md).

# Secondary PIN Pad Configuration

This section provides additional configuration steps required to enable the Verifone P400 as a Secondary PIN Pad at a Verifone Commander Site Controller location.

The following topics are covered in this chapter:

* Secondary POP Configuration - POP ID 065 (P400) in EPS Global Configuration
* IFSF / POS Configuration - Secondary POP and Secondary EPS settings
* EMV Initialization
* Adding the Choose PIN Pad button to the screen layout
* Applying changes by logging out and back into Sales Mode
* Troubleshooting: PIN Pad not changing from Welcome prompt

### EPS Global Configuration

The P400 must be registered as a Secondary POP (Point of Purchase) device in the EPS Global Configuration. This is done on the POP tab using POP ID 065.

#### Accessing EPS Global Configuration

{% stepper %}
{% step %}

#### Open Configuration Client

Open the Verifone Commander Configuration Client.
{% endstep %}

{% step %}

#### Navigate to EPS Global Configuration

Navigate to Payment Controller > EPS Configuration > EPS Global Configuration.
{% endstep %}

{% step %}

#### Select the POP tab

Select the **POP tab**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Edits to EPS Global Configuration require a one-time password (OTP). Have your OTP ready before making changes.
{% endhint %}

#### Configuring the Secondary POP (POP ID 065)

The POP tab contains two sections: POP Configuration (primary PIN pad) and Secondary POP Configuration. The P400 is configured in the Secondary POP Configuration section.

<figure><img src="/files/XNQs7aIibenGbt9cxut8" alt=""><figcaption></figcaption></figure>

In the Secondary POP Configuration section, configure the following fields:

| Field            | Value / Description                                                 |
| ---------------- | ------------------------------------------------------------------- |
| POP ID           | 065                                                                 |
| Model            | P400                                                                |
| IP Address       | Enter the IP address assigned to the Verifone P400 on your network. |
| Port             | 4000                                                                |
| Connect with TLS | Check enabled (TLS required for secure communication).              |
| Secure Port      | 5000                                                                |

{% stepper %}
{% step %}

#### Add POP ID 065

In the Secondary POP Configuration section, click **Add POP** if no row exists for **POP ID** 065.
{% endstep %}

{% step %}

#### Set the model

Set **Model** to P400 from the drop-down.
{% endstep %}

{% step %}

#### Enter the IP address

Enter the **IP Address** of the Verifone P400.
{% endstep %}

{% step %}

#### Set the ports

Set **Port** to 4000 and **Secure Port** to 5000.
{% endstep %}

{% step %}

#### Enable TLS

Check **Connect with TLS**.
{% endstep %}

{% step %}

#### Save the configuration

Click **Save**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The primary POP (ID 001) entry should already exist. Do not modify the primary POP settings when adding the secondary POP. Example values shown: Primary — Mx870 at 192.168.31.126; Secondary — P400 at 192.168.31.127.
{% endhint %}

### IFSF / POS Configuration — Secondary POP and Secondary EPS

The POS Configuration screen contains the IFSF settings, the VFI POS-POP mapping, the Secondary POP Configuration, and the Secondary EPS Configuration. All of these must be verified or configured for the P400 to operate as a secondary PIN pad.

<figure><img src="/files/Trtzx42XFpuQPwJiOzfc" alt=""><figcaption></figcaption></figure>

#### Accessing POS Configuration

{% stepper %}
{% step %}

#### Navigate to POS Configuration

In the Configuration Client, navigate to Payment Controller > POS Configuration.
{% endstep %}

{% step %}

#### Select the IFSF tab

Select the **IFSF tab.**
{% endstep %}
{% endstepper %}

**VFI POS-POP Configuration**

The left panel maps each VFI POS lane to its POP ID. Verify that the POS lanes at your site are mapped correctly (e.g., VFI POS 1 ? POP ID 001). These mappings are typically pre-configured and do not need to change when adding a secondary PIN pad.

**Secondary POP Configuration**

In the Secondary POP Configuration panel, configure POP ID 065 for the P400:

| Field   | Value / Description                                               |
| ------- | ----------------------------------------------------------------- |
| POP ID  | 065                                                               |
| Name    | Secondary Pinpad (or site-specific name)                          |
| Lane ID | Enter the lane ID associated with the secondary PIN pad location. |
| Enabled | Check to enable the secondary PIN pad.                            |

{% hint style="info" %}
In the example shown, POP ID 065 is named “Secondary Pinpad”, assigned Lane ID 33, and has Enabled checked (highlighted in yellow). Confirm the Lane ID matches the physical lane assignment at your site.
{% endhint %}

**IFSF Configuration**

The right panel contains the IFSF communication parameters. Verify or enter the following values to match your site configuration:

| Field                            | Value / Description                                                   |
| -------------------------------- | --------------------------------------------------------------------- |
| EPS IP Address                   | IP address of the Verifone Commander EPS server (e.g., 192.168.31.11) |
| POS Refresh Timer                | 60 (default)                                                          |
| Device Request Default Timer     | 75 (default)                                                          |
| Timeout Request                  | 5                                                                     |
| Timeout Connect                  | 0.5                                                                   |
| Timeout Response                 | 240                                                                   |
| Max Repetition                   | 3                                                                     |
| Service Waiting Port             | 4002                                                                  |
| Card Waiting Port                | 4001                                                                  |
| Device Waiting Port              | 4003                                                                  |
| Device Request Port              | 4004                                                                  |
| Unsolicited Request Waiting Port | 4005                                                                  |

{% hint style="info" %}
TLS Configuration ports (7001–7005) are shown in the lower portion of the IFSF panel. Ensure TLS Mode Disabled is unchecked if TLS is required at your site.
{% endhint %}

**Secondary EPS Configuration**

The Secondary EPS Configuration section at the bottom of the screen is used for sites with a third-party EPS. For standard Verifone Commander deployments, verify the following:

| Field          | Value / Description                                                          |
| -------------- | ---------------------------------------------------------------------------- |
| Select EPS     | Set to Third-Party if a secondary EPS is in use; otherwise leave as default. |
| Enable         | Check only if a secondary EPS is required at your site.                      |
| EPS IP Address | Enter the IP address of the secondary EPS if enabled.                        |

{% stepper %}
{% step %}

#### Configure IFSF and Secondary POP

Configure all **IFSF** and **Secondary POP** fields as described above.
{% endstep %}

{% step %}

#### Save the configuration

Click **Save**.
{% endstep %}
{% endstepper %}

### EMV Initialization

After completing the POP and IFSF configuration, perform an EMV initialization to push the EMV configuration from EPS to the Verifone EVPAY application on the P400.

{% stepper %}
{% step %}

#### Navigate to EPS Global Configuration

In the Configuration Client, navigate to Payment Controller > EPS Configuration > EPS Global Configuration.
{% endstep %}

{% step %}

#### Select EMV Initialization

Select the **EMV Initialization tab**.
{% endstep %}

{% step %}

#### Initialize

Click **Initialize** to push the EMV configuration to the P400.
{% endstep %}

{% step %}

#### Wait for completion

Wait for the initialization to complete before proceeding.
{% endstep %}
{% endstepper %}

### Adding the Choose PIN Pad Button to Screen Configuration

To allow cashiers to toggle between the primary and secondary PIN pads, the Choose Pinpad button must be added to the POS screen layout.

{% stepper %}
{% step %}

#### Open Configuration Client

Open the Verifone Commander Configuration Client.
{% endstep %}

{% step %}

#### Navigate to Screen Configuration

Navigate to Store Operations > Touch Screen > Screen Configuration section.
{% endstep %}

{% step %}

#### Select the screen layout

Select the screen layout where the button should appear (typically the main cashier function key screen).
{% endstep %}

{% step %}

#### Add the button

Add a new button and assign it the function: **Choose Pinpad**.
{% endstep %}

{% step %}

#### Set the label

Set the button label as desired (e.g., “Choose Pinpad”).
{% endstep %}

{% step %}

#### Save

**Save** the screen configuration.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The Choose Pinpad button follows the standard function-key button process. Refer to the Verifone Commander Screen Configuration Guide for general button-adding instructions. An example of the button in use is shown in the PIN Pad Toggle section of the Using the P400 PIN pad chapter.
{% endhint %}

### Applying Changes — Log Out and Back Into Sales Mode

After completing all configuration changes, you must log out of Sales Mode and log back in for the updates to take effect at the POS.

{% stepper %}
{% step %}

#### Save all changes

Complete and save all configuration changes in the Configuration Client.
{% endstep %}

{% step %}

#### Log out of Sales Mode

At the POS terminal, log out of Sales Mode.
{% endstep %}

{% step %}

#### Log back in

Log back into Sales Mode.
{% endstep %}

{% step %}

#### Verify the button

Verify the Choose Pinpad button appears on the configured screen.
{% endstep %}

{% step %}

#### Test the toggle

Test the toggle by selecting Secondary PinPad from the Choose Pinpad dialog.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

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

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/pin-pads/implementation-guides/p400/secondary-pin-pad-configuration.md?ask=<question>&goal=<endgoal>
```

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

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.