> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/pagos/sobre-los-pagos.md).

# Sobre los pagos

Las ventas deben tener un **pago aprobado** asociado para poder procesarse. Fenicio admite un **único pago por venta**, que debe cubrir el importe total.

Los pagos online se gestionan mediante **integradores de pago**, que conectan con bancos, tarjetas y redes de cobranza, centralizando la operativa técnica y administrativa.

Para habilitar un medio de pago, selecciona un **integrador disponible en Fenicio** que incluya el método que deseas. Cada integrador ofrece condiciones comerciales, funcionalidades y experiencias de compra distintas.

{% hint style="success" %}
Se recomienda mostrar los **métodos de pago en la ficha de producto** para facilitar la decisión de compra.
{% endhint %}

Fenicio también permite **pagos manuales**, para registrar pagos en efectivo o realizados por medios externos no conectados directamente a la plataforma.


---

# 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://guia.fenicio.help/pagos/sobre-los-pagos.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.