> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/security-and-compliance/dora.md).

# DORA

Our E-Comerce Payment Gateway service (delivery method SaaS) is designed to fully align with the requirements set out in the Digital Operational Resilience Act (DORA)– Regulation (EU) 2022/2554 of the European Parliament and of the Council.

As a third-party ICT service provider supporting financial institutions, we ensure compliance with DORA’s operational resilience requirements, including:

* Implementing robust ICT risk management frameworks to safeguard financial operations.
* Enabling timely identification, reporting, and mitigation of ICT-related incidents in accordance with regulatory mandates.
* Maintaining resilient infrastructure, redundancy mechanisms, and tested recovery plans to ensure service continuity.
* Adhering to supervisory expectations for critical ICT providers, ensuring transparency, accountability, and compliance with financial sector regulations.

Our commitment to DORA compliance ensures that financial institutions using our services can meet the highest standards of digital resilience, operational continuity, and regulatory oversight.

For further details on our compliance framework and how our service supports DORA-aligned operational resilience, please contact us.


---

# 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.ecomm.api.tietoevry.com/security-and-compliance/dora.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.
