> 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/nextgenpsd2-xs2a/funds-confirmation-service.md). # Funds Confirmation Service Funds confirmation is a single question, and your platform carries it: a licensed third party asks whether a given amount is available on a given account, the bank holding that account answers, and the platform returns yes or no. No balance passes through, and none can be worked out from the answer. For the banks on your platform, this is the third regulated service they owe under PSD2, satisfied without a project of their own. For the card issuers in your market — the usual askers, since their cards draw on accounts held at those banks — one connection to you reaches every bank you serve instead of a separate integration per institution. And for you it is the cheapest of the three services to operate and the one with the smallest data footprint, since nothing but a yes or no crosses the platform. The customer's permission stays with their own bank, where they granted it and where they can withdraw it; the platform records it and enforces it on every call. The reference below is generated from the Berlin Group **openFinance API Framework XS2A — Confirmation of Funds Service, version 2.4.1**. It is one operation, which is the point. ## Funds confirmation {% openapi src="" path="/funds-confirmations" method="post" %} {% endopenapi %} --- # 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/nextgenpsd2-xs2a/funds-confirmation-service.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.