> 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/emv-outside-emv/troubleshooting-outside-emv/gilbarco-flexpay-ii-crind.md).

# 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.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FaEAnahUPy9BcDBznz3av%2Fimage.png?alt=media&amp;token=9b5ff983-ae13-46f8-9ed6-be91416d4471" alt=""><figcaption></figcaption></figure>
4. If the TLS Certification is installed, the TLS files will be listed.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FDqFVhcBuxR6SqD0MJeX4%2Fimage.png?alt=media&amp;token=70d900f4-393d-491d-8dd2-e5b377d72757" alt=""><figcaption></figcaption></figure>

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.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/BFt0Wbqvx2B5zA1Xu8PU/Unknown%20image)

## 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.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2F3bfv18RZ8XVKPgjsUPlu%2Fimage.png?alt=media&amp;token=0b07451f-2c8e-4772-bb44-93b655917c3a" alt=""><figcaption></figcaption></figure>
2. From the Service Menu, select option <3> Security Setup Menu.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FJmcYnZAr9qB2n2bxLuJU%2Fimage.png?alt=media&amp;token=2e947ba2-3d75-47dd-a4ef-976f69d71677" alt=""><figcaption></figcaption></figure>
3. Enter Matching Password. This requires a call to Gilbarco TAC.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2F7hliEvNOhF9yYZxsVYmo%2Fimage.png?alt=media&amp;token=a02ea49b-2b11-4a6b-abac-3d9aa55eb859" alt=""><figcaption></figcaption></figure>
4. After entering the Security Setup Menu, select <3> Protocol Menu.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FlIkvsgIxn5phUa7LtK1i%2Fimage.png?alt=media&amp;token=e18ffa1a-669a-466b-883b-74b5b748d49b" alt=""><figcaption></figcaption></figure>
5. Verify that option <1> CRIND TLS Authentication is set: ON SINGLE AUTH.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FxJYZb9PhheLXiQpLcl3U%2Fimage.png?alt=media&amp;token=5eb7311b-cc48-440b-a8ea-49a5f43c9c23" alt=""><figcaption></figcaption></figure>

## 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.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/GItbtFr4RvPgI5Rjhfpn/Unknown%20image)

Press '1' and Enter for CRIND Config.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/KgiafKF4gkN6VIYBwKKN/Unknown%20image)

Press '3' and Enter for POS Comm Config.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Pvp8cO0Y5q6Ft8D8PJJz/Unknown%20image)

1. Press '1' and Enter to Set POS COMM Mode to IP.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/3I16FNhzIYEjqsd7YKCb/Unknown%20image)

{% hint style="info" %}
If the POS Comm Mode is already set to IP, then Cancel out of the POS Comm Config settings.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/XrGVtl8eQaljazE040D5/Unknown%20image" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FMZVuazyrWpJHUGKGXiIo%2Fimage.png?alt=media&amp;token=0f310a31-7a67-42eb-939a-4bef232c4076" alt=""><figcaption></figcaption></figure>

Press '2' and Enter to Exit the Diagnostics. This will warm reboot the CRINDS.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/5hcVJ0rv4dPrK3ChqP7V/Unknown%20image)


---

# 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/emv-outside-emv/troubleshooting-outside-emv/gilbarco-flexpay-ii-crind.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.
