> 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/target-audience.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.