> 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/api-references/openfinance.md).

# openFinance

PSD2 covers payment accounts and stops there. The Berlin Group's **openFinance** framework picks up where the directive ends, applying the same shape of interface to products and data the regulation never touched.

The commercial difference is the whole point. The regulatory interfaces are obligations your tenants owe and cannot charge for. openFinance services are products — you and your tenants decide which to publish, to whom, with what limits and at what price, and the revenue is real rather than a compliance cost recovered. Because they run on the platform you already operate, using the same consent handling, the same certificates and the same catalog and billing machinery you put in place for compliance, there is nothing new to run.

|                                                                                                             |                                              |
| ----------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| [Extended Account Information Service](/api-references/openfinance/extended-account-information-service.md) | Account data beyond the PSD2 perimeter       |
| [Extended Payment Initiation Service](/api-references/openfinance/extended-payment-initiation-service.md)   | Payment initiation beyond the PSD2 perimeter |

For third parties there is almost nothing new to learn either, and that matters commercially: a provider already integrated with your regulatory interface is most of the way to buying a premium one. A premium product is defined once on the platform and can then be offered by any tenant that wants it.


---

# 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/api-references/openfinance.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.