> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/open-banking-platform/target-audience.md). # Target Audience The Tieto Banking API Platform is built for organizations that expose, govern and monetize banking APIs under regulatory supervision. It supports operating models ranging from a single bank publishing its own PSD2 interface, to nation-wide multi-tenant implementations hosting dozens of banks as tenants on shared infrastructure. ## Why this platform Regulatory compliance is the entry ticket, not the destination. The platform treats the mandated interface and the commercial one as the same problem — published, versioned, governed and metered the same way. * **Compliant by construction.** Berlin Group NextGenPSD2, eIDAS certificates, strong customer authentication in every approach the framework defines, and the availability statistics behind exemption from the fallback mechanism. The UK Open Banking Standard is supported alongside it, so one installation can serve both regimes. * **Monetizable.** Premium API products alongside compliance APIs, with per-call and recurring fees set by the publishing bank, limits per third party, and usage metering that reconciles with billing. * **Multi-tenant.** One installation serving many banks, each with its own data, administrators, tariffs and consents — as separate branded portals or as a single shared marketplace. * **Integration-light for the bank.** Two RESTful interfaces on the bank's side. Everything else — developer channel, certificates, consents, policy, reporting, billing — comes with the platform. * **Extensible to your own services.** Published API products can be connected to the operator's own back-office systems, not only to a tenant bank's — so your own services become governed, metered API products on the same platform. * **Deployable either way.** On your own infrastructure or as a managed service, running the same software. ## For whom? ### ASPSPs Publish compliant Account Information, Payment Initiation and Funds Confirmation APIs, satisfy the RTS on SCA and CSC, and extend the same interface with commercial premium APIs. ### Processing Centers and Clearing Houses Operate the platform as shared national or regional infrastructure. Onboard multiple banks as tenants and give them a common developer-facing channel, while each bank retains control of its own data, tariffs and consents. ### Third-Party Providers PSPs, fintechs and financial API aggregators use the platform to reach multiple banks through a single integration. The Platform reduces their operational overhead of bank-by-bank onboarding, API discovery and integration support. Standardized API products, documentation and lifecycle management make integrations easier to build, operate and scale. --- # 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.api.tieto.com/open-banking-platform/target-audience.md?ask=&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.