> For the complete documentation index, see [llms.txt](https://developers.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.doku.com/accept-payments/doku-checkout/additional-feature/tokenization.md). # Tokenization ### What is Tokenization ? Tokenization is a helpful feature that makes transactions easier. It works by connecting a user's account to future payments. Once someone enters their credit card details during their first transaction on the DOKU checkout page, that information is securely saved. Later on, when they make another payment, they can simply use the linked account, avoiding the need to enter their credit card details again. ### Supported Payment Channel Tokenization supported by payment channel : * Credit Card ### How to use tokenized in Checkout Page ? What you need to ensure when activate tokenization is by bring parameter `customer.id` in your initial payment request. #### Request sample : ```json "customer":{ "id":"JC-01" } ``` --- # 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://developers.doku.com/accept-payments/doku-checkout/additional-feature/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.