> 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/features/internal-tokenization.md). # Internal Tokenization The Tieto E-Commerce Payment Gateway employs internal merchant tokenization to enhance payment security and streamline the checkout experience. Sensitive cardholder data is replaced with secure internal tokens, ensuring that neither merchants nor acquirer employees have access to raw card details at any point. These internal tokens are used exclusively within the EGW system for secure transaction processing. By reducing the PCI DSS compliance scope for merchants, internal tokenization enables secure storage and handling of customer payment credentials. Merchants can offer one-click payments, recurring transactions, and subscription services with faster and safer checkout experiences, while significantly reducing the risk of fraud and data breaches. --- # 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/features/internal-tokenization.md?ask=&goal= ``` `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.