> 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/feature-references/feature-references-lac-es/referencias-de-funciones-y-productos/tarjetas-de-flota-configuracion-y-uso-general-de-combustible/configuracion-de-tarjetas-de-flota-comercial/habilitacion-y-asignacion-de-teclas-alfanumericas-del-dcr.md).

# Habilitación y asignación de teclas alfanuméricas del DCR

Cada DCR debe asignarse a una configuración de claves DCR. Si los sitios tienen una combinación de DCR con y sin capacidades alfanuméricas, los sitios tendrían que crear 2 o más configuraciones de claves DCR.

La configuración para los DCR que son alfanuméricos debe tener marcada la opción “Habilitar alfanumérico”, y NO debe estar marcada para los DCR que solo aceptan entrada numérica.

Vaya a **Cliente de configuración > Forecourt > Teclas DCR** para configurar las teclas DCR.

1. Seleccione **Habilitar alfanumérico**.

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

Haga clic **Asignar posiciones**.

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

Seleccione el DCR que se puede usar para ingresar caracteres alfanuméricos. Los DCR que no tienen capacidades alfanuméricas aparecen atenuados.


---

# 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://docs.verifone.com/feature-references/feature-references-lac-es/referencias-de-funciones-y-productos/tarjetas-de-flota-configuracion-y-uso-general-de-combustible/configuracion-de-tarjetas-de-flota-comercial/habilitacion-y-asignacion-de-teclas-alfanumericas-del-dcr.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.
