> 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/troubleshooting-tave.md).

# Troubleshooting TAVE

This section contains frequently asked questions for the TAVE feature.

## FAQs

<details>

<summary>How do I re-register a device after relocating it? How do I "force" a registration?</summary>

It is the same as a new or newly upgraded device. Navigate to Payment Controller > EPS Configuration > EPS Global Configuration > PTPE tab. Select the correct POP under POP Operations and click Register.

</details>

<details>

<summary>How do I request an updated BIN Configuration file?</summary>

Occasionally, cards that do not require PTPE might be added to a card table. These might be loyalty programs, gift card programs, etc. This will require a new Bin Configuration file (AKA BIN Exclusion File) from the payment network. This updates the file to synchronize with the card table.

The merchant will request the BIN Configuration file from their company, who will in turn request it from Fiserv.

</details>

<details>

<summary>How do I force Advance DDK?</summary>

Advance DDK should not be used unless directed by Fiserv or the Major Oil/Merchant. Navigate to Payment Controller > EPS Configuration > EPS Global Configuration: PTPE. Select the correct POP under POP Operations and click

</details>

<details>

<summary>Where do I find documentation on how to load TAVE configuration to device in the forecourt?</summary>

Contact the device manufacturer. All devices are required to be updated in Verifone Commander Configuration Client via POP Operations as described in this document after the actual devices are loaded and configured correctly.

</details>


---

# 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/troubleshooting-tave.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.
