> 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/google-pay-tm/additional-feature-and-information.md). # Additional Feature and Information ### 1. Google Pay™ With DANA Balances By enabling both DANA and the Google Pay API, you offer customers a streamlined 'One-Tap' checkout. This integration allows users to pay with their DANA balance directly through the Google Pay interface whenever DANA is selected as the payment method As a prerequisite, the customer must have their DANA account already linked as a payment method within their Google Account settings. ### 2. Google Pay Supported Card Types Our integration with Google Pay currently supports only the PAN\_ONLY card credential method.\ In this method, the Primary Account Number (PAN) is used for communication between Google Pay, DOKU, and the card networks, instead of a network token. The PAN obtained from Google Pay is then processed through the standard 3DS authentication flow, which is applicable across all supported countries depending on your merchant configuration on our Back Office. ### 3. Activate 3DS Support For Non Google Payment Methods We support 3DS authentication for Google Pay PAN\_ONLY transactions. When a customer selects Google Pay on our Hosted Checkout Page, they can either enter their card details manually or choose a card previously saved in their Google account. For PAN\_ONLY credentials, Google Pay returns the card details to DOKU in encrypted form for each transaction. DOKU then decrypts and uses these credentials to initiate the 3DS verification process, followed by payment authorization with the acquirer ### 4. Brand Guidelines As DOKU manages the entire Hosted Checkout UI on your behalf, **you are not required to implement or customize the Google Pay button yourself.** DOKU ensures full compliance with [Google Pay Brand Guidelines](https://developers.google.com/pay/api/web/guides/brand-guidelines) on your behalf. --- # 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/google-pay-tm/additional-feature-and-information.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.