> 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/sandbox-guide/going-live.md).

# From Sandbox to Production

The walkthrough stops at the sandbox, because production access belongs to a real deployment — yours. This page sets out what a TPP does next, and which of those gates you would be holding.

## The three preconditions

There is no re-integration between sandbox and production. The APIs are identical; what changes is what has to be true before a call is accepted.

1. **Credentials.** What is required depends entirely on what is being consumed — see the table below. The eIDAS regime applies to XS2A and nowhere else.
2. **Subscription.** The TPP requests a subscription to the service it needs. A subscription is with one institution, so a TPP consuming several of your tenants holds several.
3. **Live applications.** Production applications are created, with the right credentials attached and scopes covering the subscribed APIs.

| Consuming                             | Credentials required                                                                                                                                                                                                                                                                                       |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **XS2A regulatory services**          | Live **QWAC and QSealC** issued by a qualified trust service provider and uploaded to the portal. The caller must hold a PSD2 license and the roles for the service it is exercising.                                                                                                                      |
| **Premium and other commercial APIs** | **No eIDAS certificates and no license.** The subscriber submits a certificate signing request and the platform issues its client and signature certificates. A premium subscriber can be any organization you choose to sell to — a corporate, a software vendor, a fintech without a PSD2 authorization. |
| **Aggregation services**              | Depends on the model: the TPP's own eIDAS identity where it is licensed, or yours where it is not.                                                                                                                                                                                                         |

## After go-live

The portal reports on live traffic — call volumes, success and failure counts, average and maximum response times, by product, application and environment — and fee reports show what is owed against premium products. Reporting depth is configurable and is typically at least a year. See [Monitoring and Reporting](/features/monitoring-and-reporting.md) for the operator's side of the same data, including the regulatory performance dashboard.


---

# 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/sandbox-guide/going-live.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.