> 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/e-commerce-payment-gateway/target-audience.md).

# Target Audience

Tieto E-Commerce Payment Gateway (EGW) is designed for organizations operating payment services, commerce platforms, and transaction ecosystems.

The platform supports multiple operational and business models across the payments and financial services landscape.

### Banks & Financial Institutions

Provide merchant payment services, online payment capabilities, and digital commerce solutions through branded and scalable payment infrastructure.

### Acquirers

Support merchant onboarding, transaction processing, routing, and operational payment services across acquiring ecosystems.

### Payment Service Providers (PSPs)

Operate and scale payment services through modular gateway capabilities, orchestration, integrations, and operational tooling.

### Processing Centers

Manage transaction processing, routing, authorization flows, and connectivity with external payment networks and financial systems.

### Fintech Platforms

Integrate embedded payment capabilities, recurring billing, and digital payment services into modern financial products and platforms.

### Marketplaces & Commerce Platforms

Support multi-vendor payment operations, fund distribution, and centralized payment management across platform ecosystems.


---

# 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/e-commerce-payment-gateway/target-audience.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.
