> 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/card-payment.md).

# Card payment

The Card Payment option in the sandbox simulates the traditional card checkout flow where the user manually enters card details. This demonstrates how EGW handles direct card data entry in a secure and structured way.

{% hint style="info" %}
In sandbox mode, all transactions are mocked, and card data is not processed or sent to any external networks.
{% endhint %}

### Testing Data

* **Cardholder Name:** Any value
* **Card Number:**
  * 5186 0000 0000 0005 – Successful authorization
  * 5186 0000 0000 0013 – Failed authorization
* **Expiry Date:** Any valid future date (e.g., 12/28)
* **CVV:** Any 3-digit number (e.g., 123)

{% hint style="info" %}
All data is simulated. No real authorization takes place, and responses are based on predefined sandbox rules.
{% endhint %}

### How-to

The overall checkout journey for Card Payments follows the same steps as the[ Click-to-Pay flow](/e-commerce-payment-gateway/sandbox-guide/self-hosted-checkout-page/click-to-pay.md#how-to).

1. The user starts from the Demo Shop, selects a product, adds it to the basket, and proceeds to checkout. 
2. The only difference is that, on the Gateway Hosted Checkout Page, the user must select the “ Card” option instead of Click-to-Pay.
3. After choosing the method, the user enters the test card details manually and completes the simulated transaction.

<figure><img src="/files/OIZnQ9fxrYr59d0Y7H8r" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/sandbox-guide/self-hosted-checkout-page/card-payment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.