> 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/configuracion-de-tarjetas-comdata.md).

# Configuración de tarjetas Comdata

## Configuración de la actualización del precio del diésel

Haga lo siguiente para cambiar el precio del diésel y enviar el cambio de precio al host.

En Configuration Client, vaya a **Forecourt > Combustible > Fuel Config- Pending > Productos de combustible**. Anote el ID del grado de combustible para el producto Comdata con cambio de precio.

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

En Configuration Client, vaya a **Payment Controller > Configuración de BUYPASS**. En la sección Admin Messages, habilite “Send Price Change Notification XML” y seleccione el mismo ID de grado de combustible en el **ID de grado de combustible para diésel**campo.

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

Guarde la configuración y reinicie Verifone Commander.

Después de reiniciar, vaya a **Configuration Client > Forecourt > Fuel > Precio del combustible - Pendiente** y actualice el precio del diésel.

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

El precio del diésel actualizado para Self, tanto para el precio en efectivo como para el precio a crédito, se envía al host.


---

# 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/configuracion-de-tarjetas-comdata.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.
