> 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/features/localization-and-regional-adaptation.md).

# Localization and Regional Adaptation

The Developer Portal is where third parties meet your platform, and the language it speaks is the first thing they judge it by. Language is treated as a property of the portal rather than an afterthought, and how far you take it is your choice.

## Two options

|                     |                                                                                                                                                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Single language** | The whole portal — interface and content — delivered in one language of your choosing. The straightforward answer for an operator serving a single market, or one where every third party works in the same language. |
| **Multi-language**  | A distinct version of the portal for each language, with its own content and its own editing. The answer where you serve several markets, or where one market expects both its local language and English.            |

Either way, localization covers two layers: the portal's own **interface** — labels, navigation, forms and system messages — and the **content** held in the CMS, meaning the landing page, product catalog, guides, FAQ, support pages and legal text. Interface languages are set up as part of delivery; the content is yours to maintain from the first day onward.

## Each language version is edited separately

This is what distinguishes a multi-language portal from a translated one. Every language is a version in its own right, not a field inside a master copy. A **CMS manager** opens one language and edits it without touching the others.

## Regional adaptation

Language is the visible half of localization. The other half is the market's own rules — and most of that is configuration rather than development, which is what keeps a second market from becoming a second project.

| Area                    | How it adapts                                                                                                                                                                                                                                                           |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| National register       | The platform integrates with the national register of authorized providers and validates every call against the roles and status recorded there, so the register that governs a market is the register that is enforced.                                                |
| National specifications | Where a regulator publishes its own profile of the Berlin Group specification, that profile is what is published and served. Major versions follow both Berlin Group releases and national mandates.                                                                    |
| Access limits           | Frequency limits, consent validity periods and transaction history reach are configurable within the bounds the regulator sets, per market and per bank, without a release.                                                                                             |
| Statistical reporting   | Interface availability and performance statistics are calculated to the definitions used by the European Banking Authority guidelines and published at the cadence the market requires.                                                                                 |
| Local payment products  | Domestic payment schemes can be added to the suite of payment products supported by Payment Initiation Service. Additional services can be easily accommodated — including bulk and multi-bulk, future-dated, recurring, and cross-border payments in foreign currency. |


---

# 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/features/localization-and-regional-adaptation.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.