> 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/consent-management.md). # Consent Management Consent is the legal basis for third-party access to PSU account information, and the platform treats it as a first-class object rather than a side effect of an API call. Our dedicated Consent Management service safely stores all consents and makes them available for oversight and management via [Bank Administration Portal](/portals-and-interfaces/bank-portal.md). Consents can also be exposed to your tenant banks to enable integration of consent information into their own digital channels. ## What a consent holds Every consent holds * owners — the third party that requested it, the customer who granted it, and the bank that services the account; * terms; * status; * authentication history; * revocation details The terms describe exactly what was agreed: the consent type, its expiry, how many times per day it may be used without the customer present, and which accounts, balances and transaction lists are covered. ## SCA sessions Each authentication attempt (SCA) against a consent is a distinct session, stored by our Consent Management service and progressing through its own lifecycle. Keeping sessions separate from the consent allows multi-level authorization, where several people must authenticate against one consent. ## Integration with the bank's channels The Consent Management service exposes a RESTful interface that tenant banks can integrate into their internet and mobile banking. The bank authenticates with client credentials obtained from the Bank Portal and exchanged for an access token. This integration is what makes consent oversight real for the customer. Without it, a customer can only withdraw access through the third party that asked for it. With it, the bank's own channel becomes the place to review and revoke every third-party consent, and a consent withdrawn there is recorded as revoked in the customer's channel and reflected everywhere else. ## Oversight by the bank Bank administrators see consents across the institution, filtered by third party, customer, status, creation date and validity date, in both sandbox and live environments. Staff holding the consent management role can **revoke** an account information consent directly — the control that matters when a customer reports a problem or fraud is suspected. --- # 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/consent-management.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.