> 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/portals-and-interfaces/bank-portal.md). # Bank Portal The Bank Portal belongs to the participating bank. It is where the bank manages its commercial relationships with third-party providers, oversees its customers' consents, and gets the figures it needs for regulatory reporting. ## API Service management In the Bank Administration portal the bank can * connect and disconnect TPPs to and from its premium and regulatory APIs, * set call limits per product, * set per-call and recurring fees — flat or progressive. All changes pass through four-eyes review inside the portal: one administrator edits, another approves. This reduces the risk of unauthorized, incorrect, or fraudulent changes reaching production. It also creates a clear audit trail and separates operational responsibility. ## Consent management The consents module is the portal's most operationally significant feature. Bank staff see every consent granted by the bank's customers. Statuses are mapped to the Berlin Group vocabulary, so what staff see matches what TPP receives. Staff holding the consent management role can **revoke account information consent** directly from the portal. This provides immediate operational control when a consent must end because of suspected fraud, a customer request, or a support case. The action is recorded against the consent, creating an auditable record of who revoked it and why. This shortens investigations, supports dispute handling, and helps the bank demonstrate consistent consent governance. ## User management The bank's Superuser manages the bank's own administrators — inviting them, assigning roles, resetting credentials, suspending accounts. A Superuser cannot create another Superuser; that remains with the platform operator, and is done through the tenant agreement rather than the user list. ## Reporting The portal provides operational, commercial and regulatory reporting. Banks can monitor live API traffic, consent activity, third-party fees and interface performance. Reporting also surfaces payment initiation patterns that support fraud monitoring and oversight. Standard reporting depth is typically a year, with older data retained in cold storage. ## National register integration The portal reflects the platform's integration with the national register of authorized providers. Administrators can view register data for a particular TPP right from Bank Portal UI. --- # 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/portals-and-interfaces/bank-portal.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.