> 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/integration-with-national-registers.md).

# Integration with National Registers

A certificate proves who is calling. It does not prove they are still allowed to. Those are different questions, and only the second one is authoritative.

Most markets maintain a register of licensed providers, published by the national regulator, recording which services each provider may offer and whether its authorization is currently in force. The platform validates against that register on **every call** — not at onboarding, not nightly, but as part of the request.

## Beyond the register

Register checking is one instance of a general capability: the platform can consult an external authority mid-request and act on the answer. That opens the door to verifications a market or a business may require:

| Check                                    | Purpose                                                                    |
| ---------------------------------------- | -------------------------------------------------------------------------- |
| Register of licensed providers           | Roles and authorization status, as above                                   |
| Sanctions and watchlist screening        | Screen a payment's counterparty before the instruction is routed           |
| Beneficiary or account name verification | Confirm the payee matches the account before initiation                    |
| Corporate registry lookup                | Verify an organization's details during onboarding                         |
| Fraud and risk scoring                   | Score an instruction against an internal or third-party model              |
| Internal blocklists                      | Institution-specific restrictions on accounts, counterparties or providers |

Each behaves the same way in the chain: it can refuse the call outright, enrich the request with data for the back office to use, or record its finding in the audit trail for later scrutiny.


---

# 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/integration-with-national-registers.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.