> 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/open-banking-platform/glossary.md). # Glossary | Term | Meaning | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AIS | Account Information Service. Access to account details, balances and transaction history. | | AISP | Account Information Service Provider. A TPP licensed to provide AIS. | | API Group | The container in which APIs are published and versioned on the platform. Individual APIs have no independent lifecycle; creation and retirement happen at API Group version level. | | API Product | An API Group as it appears to third-party providers in the Developer Portal catalog and subscriptions. | | ASPSP | Account Servicing Payment Service Provider. The institution holding the payment account. | | Back Office | The institution-side systems the platform integrates with, exposed through the SCA Server and Core Server interfaces. | | Berlin Group | The European payments standards initiative that publishes the NextGenPSD2 XS2A Framework — the interface most EU markets implement for PSD2. | | CBPII | Card Based Payment Instrument Issuer. A TPP licensed to request funds confirmation. | | CIBA | Client Initiated Backchannel Authentication. The OpenID Connect flow behind decoupled authentication, where the customer approves in a separate channel such as a banking app. | | Client Application | The registered application through which a TPP is authenticated and authorized. Identified by name, version and API scope, each version carrying its own credentials. | | CMA | Competition and Markets Authority. The UK authority whose Order established Open Banking and mandated the standard. | | Consent | The PSU's authorization for a TPP to access accounts or initiate a payment, held and lifecycle-managed by the Consent Management service. | | Core Server | The institution's RESTful interface serving account information, funds confirmation and payment initiation operations. | | DCR | Dynamic Client Registration. The UK mechanism by which a third party registers a client application automatically, instead of by manual certificate upload. | | Detached JWS | A signature carried in an HTTP header rather than inside the payload, computed over the unencoded body. The form the UK standard mandates, using the PS256 algorithm. | | eIDAS | The EU regulation under which QWAC and QSealC certificates are issued. | | FAPI | Financial-grade API. The OpenID Foundation security profile the UK standard mandates. | | FCA | Financial Conduct Authority. The UK conduct regulator, which supervises payment services alongside the CMA Order. | | HAL | Hypertext Application Language. The hypermedia convention by which responses carry links to the next step in a flow. | | Invitation | A single PSU authentication session within a consent, progressing through received, started, identified, authenticated and finalized states. | | ISO 20022 | The financial messaging standard whose element names and data types both the Berlin Group and OBL specifications follow. | | JWE | JSON Web Encryption. Used for element-level encryption of sensitive payload fields. | | JWS | JSON Web Signature. Used for message-level signatures on requests and responses. | | MI Reporting | Management Information reporting. The metric set a UK institution must submit to OBL, consumed by OBL, the CMA and the FCA. | | mTLS | Mutual TLS. Both parties present certificates, used between the platform and back-office interfaces. | | OBL | Open Banking Limited. The UK standard setter, which publishes the UK Open Banking Standard. | | OBSeal | The UK signing certificate, issued against the OBL Trust Anchor. Equivalent in purpose to a QSealC. | | OBWAC | The UK network certificate, issued against the OBL Trust Anchor. Equivalent in purpose to a QWAC. | | Open Banking Directory | The UK registry of participants, through which third parties are identified and certificates are issued. | | openFinance | The Berlin Group framework extending open banking beyond the payment accounts PSD2 covers. | | PIIS | Payment Instrument Issuer Service. Confirmation that funds are available. | | PIS | Payment Initiation Service. Initiation and status tracking of payments. | | PISP | Payment Initiation Service Provider. A TPP licensed to provide PIS. | | PSD2 | The second Payment Services Directive, which mandates third-party access to payment accounts. | | PSU | Payment Service User. The institution's customer whose account is accessed. | | QSealC | Qualified Certificate for Electronic Seals. Protects the integrity of transaction data. | | QTSP | Qualified Trust Service Provider. Issues QWAC and QSealC certificates. | | QWAC | Qualified Website Authentication Certificate. Secures the TLS channel and identifies the TPP. | | RTS on SCA and CSC | The regulatory technical standards on strong customer authentication and common and secure communication. | | SCA | Strong Customer Authentication. | | SCA Server | The institution's interface enabling the PSU authentication flows defined by the standard. | | Tenant | A financial institution participating in a multi-tenant deployment, with its own data, configuration, administrators and tariffs. | | TPP | Third-Party Provider. The regulated organization consuming the institution's APIs. | | Trust Anchor | The authority whose signature makes a certificate trustworthy — a qualified trust service provider under eIDAS, or OBL in the UK. | | VRP | Variable Recurring Payments. A UK payment type allowing repeated payments under a single consent within agreed limits. Part of the OBL standard, not in the current platform scope. | | XS2A | Access to Account. The Berlin Group framework governing the regulatory interface. | --- # 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/open-banking-platform/glossary.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.