> 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/incomm/usando-incomm/venta-prepago.md).

# Venta prepago

### Venta prepaga en tienda

La Venta prepaga en tienda es una solicitud de transacción de prepago de combustible que se inicia en el POS interior y se paga usando una tarjeta de circuito cerrado InComm.

#### Pasos de la venta prepaga en tienda

{% stepper %}
{% step %}
**Número de surtidor**

Ingrese el **\<número de surtidor>**.
{% endstep %}

{% step %}
**PREPAGO**

Presione **\[PREPAGO]**.
{% endstep %}

{% step %}
**Monto**

Ingrese el **\<monto en dólares>**.
{% endstep %}

{% step %}
**TOTAL y crédito**

Presione **\[TOTAL]** y seleccione **\[CREDIT]**.
{% endstep %}

{% step %}
**Pasar**

Pida al cliente que pase la tarjeta por el teclado PIN del POP.
{% endstep %}
{% endstepper %}

El teclado PIN del POP muestra un mensaje de Aprobado, y la terminal imprime un recibo que muestra:

* número de cuenta enmascarado
* número de autorización

### Venta prepaga exterior

Cuando un cliente desliza una tarjeta InComm de circuito cerrado en el DCR para comprar combustible, se inicia una solicitud de transacción de venta prepaga exterior.

#### Pasos de la venta prepaga exterior

Deslice la tarjeta en el DCR. Si se aprueba, el DCR imprime un recibo que muestra:

* número de cuenta enmascarado
* número de autorización


---

# 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/incomm/usando-incomm/venta-prepago.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.