> 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/configuring-outside-emv/configuring-gilbarco/outdoor-emv-configuration-for-gilbarco-crind.md).

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

   <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>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.</p></div>
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.<br>

      <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FxbXrjwYmFvRX4vainwAj%2Fimage.png?alt=media&amp;token=d167315a-bc0e-4ad3-ad73-2f4660c8b313" alt=""><figcaption></figcaption></figure>
   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.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FYBocq9PxaYAS9ClLjhlG%2Fimage.png?alt=media&amp;token=79699eee-4b9d-4915-b8f8-4d0be4ed94f6" alt=""><figcaption></figcaption></figure>
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 %}

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

## 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 %}

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

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FAIsW2Gzb7eoj6uLuEJV8%2Fimage.png?alt=media&amp;token=f396a664-4c4c-4d6c-9cd5-97effd5e44a6" alt=""><figcaption></figcaption></figure>

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

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

Create a DCR Keys layout by clicking on Add for Gilbarco DCRs below.

**Gilbarco DCRs:**

* **Label:** Gilbarco EMV
* **#Rows:** 4
* **#Columns:** 6

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

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)<br>

      <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FC7iv76mR0eoIg8RrBZ9x%2Fimage.png?alt=media&amp;token=cb8bc664-3be0-4d0b-9378-9d26a2356718" alt=""><figcaption></figcaption></figure>
2. Select Assign Positions and Select DCR Position(s) to all the DCRs and click Save.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fyn3iwrozMzacg9v6RbJa%2Fimage.png?alt=media&amp;token=c055a47e-7e9f-4086-ba45-526a52de4f2d" alt=""><figcaption></figcaption></figure>
3. Click Save at DCR Keys Configuration.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2F7isR5pj8dGVxqBfz7hSe%2Fimage.png?alt=media&amp;token=4014158a-a7ef-4566-83cb-2e8a10a4c2cc" alt=""><figcaption></figcaption></figure>
4. Navigate to **Configuration Client > Tools > Refresh Configuration**.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FJJxvl2kvHeknexvgeMTj%2Fimage.png?alt=media&amp;token=38f62695-df95-49cf-9043-aac813f7b7fe" alt=""><figcaption></figcaption></figure>


---

# 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/configuring-outside-emv/configuring-gilbarco/outdoor-emv-configuration-for-gilbarco-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.
