> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/tietoevry-egw-documentation-es/pasarela-de-pagos-de-comercio-electronico/publico-objetivo.md).

# Público objetivo

Tieto E-Commerce Payment Gateway (EGW) está diseñado para organizaciones que operan servicios de pago, plataformas de comercio y ecosistemas de transacciones.

La plataforma admite múltiples modelos operativos y de negocio en el panorama de pagos y servicios financieros.

### Bancos e instituciones financieras

Proporcionan servicios de pago para comercios, capacidades de pago en línea y soluciones de comercio digital mediante una infraestructura de pagos con marca y escalable.

### Adquirentes

Dan soporte a la incorporación de comercios, el procesamiento de transacciones, el enrutamiento y los servicios operativos de pago en ecosistemas de adquirencia.

### Proveedores de Servicios de Pago (PSP)

Operan y escalan servicios de pago mediante capacidades modulares de gateway, orquestación, integraciones y herramientas operativas.

### Centros de procesamiento

Gestionan el procesamiento de transacciones, el enrutamiento, los flujos de autorización y la conectividad con redes de pago externas y sistemas financieros.

### Plataformas fintech

Integran capacidades de pago embebido, facturación recurrente y servicios de pago digital en productos y plataformas financieras modernas.

### Marketplaces y plataformas de comercio

Dan soporte a operaciones de pago multivendedor, distribución de fondos y gestión centralizada de pagos en ecosistemas de plataformas.


---

# 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://doc.ecomm.api.tietoevry.com/tietoevry-egw-documentation-es/pasarela-de-pagos-de-comercio-electronico/publico-objetivo.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.
