> 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/features/payment-facilitator.md).

# Payment Facilitator

The E-Commerce Payment Gateway (EGW) supports payment facilitator (PF) models in which a payment facilitator manages payment acceptance for multiple underlying sub-merchants. EGW provides the technical capabilities to represent this structure, link its entities, process transactions, and give authorized users operational visibility across the hierarchy.

### How the model works

A PF relationship can be represented through three levels:

* **Payment Facilitator (PF):** the intermediary that has a contractual acquiring relationship with the Customer and maintains commercial relationships with underlying sub-merchants.
* **Sub-merchant:** the legal entity whose goods or services are being paid for.
* **E-shop (acceptor):** the online shop associated with a sub-merchant where the payment is initiated.

A PF may manage multiple sub-merchants, and each sub-merchant may have one or more e-shops. EGW maintains the links between these entities and their acquiring configuration. Depending on the Customer’s acquiring and onboarding model, the setup may include only the PF, the PF and its sub-merchants, or the full hierarchy including individual e-shops.

### Onboarding and management

The Gateway Owner can register and manage PF entities, sub-merchants, and associated e-shops through the Administration Portal or through integration with its acquiring environment. The Gateway Owner’s configuration determines which PF-related functions are available in the Merchant Portal and which users can access them. By default, the Gateway Owner manages PF entities; sub-merchants do not have direct Merchant Portal access unless the Gateway Owner enables it.

Sub-merchants and e-shops use EGW’s standard merchant and e-shop data model. The PF model adds the hierarchical relationships and PF-specific operational configuration rather than introducing a separate data model for each entity type. PF records can include legal entity details, scheme identifiers, supported payment schemes, processing settings, time zone, language, and contact information, subject to the Gateway Owner's setup and applicable requirements.

### Transaction processing and visibility

EGW can process payments initiated by e-shops operating under a PF structure and transmit PF, sub-merchant, e-shop, and acquiring information to the Gateway Owner’s acquiring environment as required by the configured flow. Authorization data may include sub-merchant identifiers and, where required and supported, tax or registration details.&#x20;

The exact authorization fields, mappings, and routing depend on the acquiring host, card-scheme requirements, regional rules, and Gateway Owner-specific configuration. In some setups, sub-merchants are not separately registered as acquiring merchants; the PF supplies their identifying data dynamically with each authorization request.

Authorized users can search and monitor transactions at PF, sub-merchant, and e-shop level through the applicable portal interfaces. Integration with acquiring host can synchronize PF identifiers, e-shop registration and status, processing configuration, and acquiring or routing parameters.

### Responsibilities and scope

EGW provides technical orchestration and management capabilities for the PF structure. The Gateway Owner, PF, and other regulated parties remain responsible for merchant onboarding, underwriting, KYC/AML checks, scheme registration, and their applicable regulatory obligations. EGW does not act as the Merchant of Record, assume acquiring or financial risk, or perform clearing and settlement between the PF and its sub-merchants. Fund distribution or split settlement requires a separately agreed scope.

Detailed field definitions, data mappings, and integration requirements are agreed for each implementation. The solution does not independently determine whether a PF or its sub-merchants meet scheme or regulatory requirements.


---

# 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/features/payment-facilitator.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.
