> 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/donaciones-beneficas/solucion-de-problemas-de-beneficencia/informacion-importante.md).

# Información importante

Si tiene problemas con la función, consulte esta información.

* El departamento no aparece en la lista desplegable de caridad - verifique el número de código de producto para el departamento de caridad.
* Solo tengo 2 opciones en mi PIN pad - la implementación del PIN pad solo admite dos opciones.
* Configuré dos montos predeterminados para el PIN pad, pero solo aparece uno - confirme que los montos predeterminados sean diferentes. Esto incluye el predeterminado 2, que solo se usa para DCR. Si los valores son iguales, no se mostrará el valor.
* La caridad aparece en gris en el cliente de configuración - verifique los niveles de seguridad del usuario.
* Cash MOP no está recibiendo el mensaje de caridad - asegúrese de que "Se requiere monto del pago" esté habilitado para Cash MOP.


---

# 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/donaciones-beneficas/solucion-de-problemas-de-beneficencia/informacion-importante.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.
