> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/transarmor-verifone-edition-tave/configuring-tave/tave-in-verifone-commander-configuration-client.md).

# TAVE in Verifone Commander Configuration Client

## Firmware Configurations

{% hint style="info" %}
Each distribution will have different Inside/Outside Domain values. The letter "X" will be used in place of the latest version in the configuration files below.
{% endhint %}

5X Firmware Configuration for MX 900 Series devices:

* VIPER-5XGEN\_ConfigXXX.config (5X with generic BINs including condensed VISA Fleet and 8-digit BIN entries
  * Domain -- VIPER
  * Inside Brand/Key ID -- 5XGEN
  * Example File -- dl-VCL\_Settings\_VIPER-5XGEN\_ConfigXXX.config-XXXXXX.tgz

9X Firmware Configuration for Engage devices:

* VIPER-9XGEN\_ConfigXXX.config (5X with generic BINs including condensed VISA Fleet and 8-digit BIN entries
  * Domain -- VIPER
  * Inside Brand/Key ID -- 9XGEN
  * Example File -- dl-VCL\_Settings\_VIPER-5XGEN\_ConfigXXX.config-XXXXX.tgz

## Buypass Configuration

Log into Verifone Commander Configuration Client and then navigate to Payment Controller

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/7eyRsnD9LmZLByGOUZju/images/image13.jpeg)

Scroll down to TAVE Configuration.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FRIF3ntaIwjFfYtonkzdS%2Fimage.png?alt=media&amp;token=964aef89-746a-4e1c-9c30-9ed792b24ec1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The Domain and Inside Brand must be compatible with BIN and the Configuration File. If not, the registration will not be successful.
{% endhint %}

{% stepper %}
{% step %}
Key in the Domain.
{% endstep %}

{% step %}
Key in the Inside Brand.

* 5XGEN (MX 900 Series PINpad)
* 9XGEN (Engage Series PINpad)
  {% endstep %}

{% step %}
Key in the Outside Brand.

* GBQA7 (Gilbarco)
* Wayne (Currently, not supported.)
  {% endstep %}

{% step %}
Key in the Token Type.
{% endstep %}

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

## EPS Global Configuration

Log into Verifone Commander Configuration Client and then navigate to Payment Controller > EPS Configuration > EPS Global Configuration.

{% hint style="info" %}
The Advance DDK should not be used, unless Fiserv, major oil, or merchant has indicated the site should advance the DDK. If a new BIN Exclusion file was received, then use Update Settings only.
{% endhint %}

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FuMGKhERemGZw3d5OO21F%2Fimage.png?alt=media&amp;token=b52af2fb-c394-4cf3-9831-8ed2e09f382b" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}
Select the PTPE tab.
{% endstep %}

{% step %}
Check the Enabled box.

It will allow access to the POP Operations section.

{% hint style="info" %}
If using TAVE inside or outside, the Enabled box must be checked.
{% endhint %}
{% endstep %}

{% step %}
Select the appropriate PIN Pad from the POP ID drop-down menu.
{% endstep %}

{% step %}
Key in the correct Brand for the POP ID.
{% endstep %}

{% step %}
Click Save in the upper right-hand corner.
{% endstep %}

{% step %}
Navigate to the Tools menu and click Refresh Configuration.
{% endstep %}

{% step %}
Navigate back to the PTPE tab in EPS Global Configuration.
{% endstep %}

{% step %}
Click on Register.

This processes the TAVE Configuration File and notifies the host of TAVE settings. The Register Command Sent Successfully message displays.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/MDJ2NpyCwcf5TsjGjhBs/images/image16.png)
{% endstep %}

{% step %}
Click on Update Settings.

This processes the BIN Exclusion File and notifies the host of the TAVE settings. The Update Command Sent Successfully message displays.

{% hint style="info" %}
Use the Update Settings button only when a new BIN Exclusion file, separate from the Configuration file, is used.
{% endhint %}

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ShLz7G3Sg5MXp0cS2Zov/images/image17.png)
{% endstep %}

{% step %}
Click Save in the upper right-hand corner.
{% endstep %}
{% endstepper %}

## DCR Configuration

Use these steps to enable Outdoor TAVE.

{% stepper %}
{% step %}
Log into Verifone Commander Configuration Client and then click on the Forecourt menu.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fyo2z6YT7FRfTSvs8o5jP%2Fimage.png?alt=media&amp;token=91ed6dd9-f687-4a7b-8a0f-e642d76e1939" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click on the DCR menu.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fy6hn09Q3pMuwwvn0kYSC%2Fimage.png?alt=media&amp;token=8434a94f-2677-48cf-9294-0957e2abf6a3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click on the Site Configuration tab.
{% endstep %}

{% step %}
Check the Enable Outdoor TAVE box.
{% endstep %}

{% step %}
Navigate back to the Forecourt menu and click on Outdoor TAVE.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FUTrwuGbckYvqB9Hg8r49%2Fimage.png?alt=media&amp;token=48b8fb94-d45b-4439-b823-19068cbe7bbd" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FRwTvfBUH2TwMkxhfMYln%2Fimage.png?alt=media&amp;token=9c064c89-64da-4fe4-9ab5-f27a494f73d2" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The Advance DDK should not be used, unless Fiserv, major oil, or merchant has indicated the site should advance the DDK.

If a new BIN Exclusion file was received, then use Update Settings only.
{% endhint %}
{% endstep %}

{% step %}
At TAVE Operations, select the desired DCR from the DCR ID drop-down menu.
{% endstep %}

{% step %}
Key in the correct Brand for the DCR ID.
{% endstep %}

{% step %}
Click Save in the upper right-hand corner.
{% endstep %}

{% step %}
Navigate to the Tools menu and click Refresh Configuration.
{% endstep %}

{% step %}
Navigate back to the Forecourt menu and click on Outdoor TAVE.
{% endstep %}

{% step %}
Click on Register.

The Register Command Sent Successfully message displays.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/MDJ2NpyCwcf5TsjGjhBs/images/image16.png)
{% endstep %}

{% step %}
Click on Status to verify the TAVE Status.

{% hint style="info" %}
If Update DCR Settings is used without receiving a new BIN Exclusion file, the "BIN table update file missing or invalid" displays. This error does not have any overall effect on DCR TAVE processing, but it removes the registered message.

<img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FO2dcZfe6nXuqg1Apwt8g%2Fimage.png?alt=media&amp;token=cbc4ee2d-2688-4ebe-aa5f-4a1336f8cf66" alt="" data-size="original">
{% endhint %}
{% endstep %}

{% step %}
Click on Update Settings if a new BIN Exclusion file was received.

The Update Command Sent Successfully message displays.

{% hint style="info" %}
Use the Update Settings button only when a new BIN Exclusion file, separate from the Configuration file, is used.
{% endhint %}

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ShLz7G3Sg5MXp0cS2Zov/images/image17.png)
{% endstep %}
{% endstepper %}

## Cloud Bin Service Configuration

The sites should do the following before configuring the cloud BIN service:

* Sites should get the API Keys and Secret keys from Fiserv.
* Sites also need to provide Verifone the backend merchant ID, also known as PROC MID that they received from Fiserv.
* Sites need to provide the upper and lower range of the cards they want to be processed to Fiserv.

{% stepper %}
{% step %}
Log into Verifone Commander Configuration Client and then navigate to **Payment Controller > EPS Configuration > Buypass Configuration**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/7eyRsnD9LmZLByGOUZju/images/image13.jpeg)
{% endstep %}

{% step %}
Scroll down to Cloud BIN Service.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/tTpzyuK6l4ZeaXeQyLh9/images/image23.png)
{% endstep %}

{% step %}
Key in the API Key.
{% endstep %}

{% step %}
Key in the Secret key.
{% endstep %}

{% step %}
Key in Proc MID.
{% endstep %}

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

## Download POS Decision Table

The POS decision table will be downloaded every time a day close happens. Additionally, It can also be downloaded from the cashier menu in POS.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/MlbRsgPz45nqT7ikOzzR/images/image24.png)

## Loyalty/Gift card Configuration

The newly encrypted cards will only be identified based on the first 6 digits upon encryption, any new card configuration should only have upper and lower ISO configured to 6 digits only.

{% hint style="info" %}
The Card Track data gets encrypted by device only if the track 2 data s in PCI data format - (\[Primary Account Number]=\[Expiration Date]\[Service Code]\[Discretionary Data]).

The loyalty cards that do not follow this format does not have to be included in the Cloud BIN Service.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/transarmor-verifone-edition-tave/configuring-tave/tave-in-verifone-commander-configuration-client.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
