> 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/self-hosted-checkout-page.md).

# Self-Hosted Checkout Page

The Self-Hosted Checkout Page in the sandbox is a simplified version of the production checkout experience. It is designed to demonstrate the essential capabilities of the Tieto E-commerce Gateway (EGW) across multiple payment processing types.

This page is hosted by the Gateway and embedded or redirected from the merchant’s site during the checkout process. In sandbox mode, it includes limited functionality but still reflects the typical customer experience flow.

### Available Payment Methods

The sandbox checkout supports three payment options, each simulating real transaction behavior:

1. [Click-to-Pay](https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/click-to-pay.md) (Mastercard only) - A secure, card-on-file payment experience based on network tokenization and cardholder recognition.
2. Card Payments (Mastercard demo only) - Traditional card entry with CVV and expiry date, using dummy credentials.
3. A2A via PSD2 Channel (demo bank) - Account-to-account payments through a PSD2-compliant simulated bank flow.

{% hint style="success" %}
These options cover the core processing types—card-based, token-based, and bank-based—allowing you to validate EGW’s capability in handling various transaction paths.
{% 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/self-hosted-checkout-page.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.
