> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/changelog/june-2024/whitelist-domain-doku-checkout.md). # Whitelist Domain - DOKU Checkout NEW! Whitelist Domain Feature for DOKU Checkout Users. Activate this feature for FREE for Additional Security Layer. #### **Why is this feature important for the security of your business transactions?** The sophistication of digital technology not only helps businesses grow, but also has the potential to attract fraudsters who target payment security on your business platform. For example, fraudsters can trick your customers into using fake URL domains so that customer payments can be diverted out of the payment system already registered with DOKU. #### **What should you do if this happens?** You can specify the URL domain with registered DOKU credentials. If you find that your business URL domain is being misused, take the step of blocking the URL domain using the Whitelist Domain feature. Fake URL domains are blocked, customer payments cannot be diverted to other domains. By activating this feature, your business will gain an additional layer of security so that customer trust and loyalty can always be maintained. #### **How to activate this feature?** 1. Login to DOKU Dashboard 2. Go to the Settings menu, then select Checkout Page 3. Select the System Settings Tab 4. In the Whitelist Domain Setting section, Set Your Checkout Page Domain.
With this setting, only registered checkout page URL domains can process your customer payments. Any access from unauthorized URLs and reported via the dashboard will be rejected. --- # 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://docs.doku.com/changelog/june-2024/whitelist-domain-doku-checkout.md?ask=&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.