> 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/e-commerce-payment-gateway/sandbox-guide/limitation-and-terms.md).

# Limitation and Terms

The sandbox environment is a simulated testing platform designed for demonstration and integration validation purposes only. Please note the following important limitations and legal disclaimers:

* **Test BINs and Card Numbers** - Only the test BINs and card numbers provided directly by Tieto may be used in the sandbox environment. These BINs are strictly reserved for internal simulation and are configured to operate exclusively within this sandbox system. Transactions using these test BINs do not reach any external payment networks and are fully isolated from live issuer or scheme infrastructure.

{% hint style="info" %}
Use of any real or unauthorized test card numbers is strictly prohibited. Tieto assumes no responsibility for misuse outside of the controlled sandbox scope.
{% endhint %}

* **Mocked Payment Responses** - All payment authorizations, declines, and refund results are simulated and do not reflect actual issuer or bank behavior. No funds are moved at any point.
* **Default Currency (EUR)** - All amounts are processed and calculated in EUR, regardless of any currency selection in your shop configuration or during payment simulation. Even if you select multiple currencies, calculations will default to EUR internally in sandbox mode.
* **A2A Transactions** - The sandbox includes a mock bank for PSD2-compliant account-to-account payments. No connection to real (production) banking systems.
* **Limited Payment Method Support** - Only the following payment methods are available:
  * Mastercard (dummy cards only)
  * Mastercard Click-to-Pay (demo flow)
  * A2A (via a single test bank)
* **No Real User Data**- You must not enter or store real customer data, cardholder data, or personal identifiable information (PII) in the sandbox.
* **No PCI DSS Scope** - The sandbox is not in scope for PCI DSS compliance, and should not be used for any form of certification, penetration testing, or production-grade validation.
* **Session and Access Expiry** - Test environments may be periodically reset or deactivated without notice. Please back up any test results or configurations you wish to retain.

{% hint style="success" %}
By using the sandbox, you agree to use it solely for testing and evaluation purposes, in accordance with Tieto’s sandbox usage policy.
{% endhint %}

{% hint style="warning" %}
All trademarks, trade names or company names used on this website page are for identification purposes only and are the property of their respective owners. Tieto is not associated with, or sponsored by, them.
{% endhint %}


---

# 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/e-commerce-payment-gateway/sandbox-guide/limitation-and-terms.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.
