Prerequisites
Before you start integrating the Google Pay button, make sure you have the following in place.
What you need
| Artifact | Where to get it |
|---|---|
Google Pay-enabled terminal (terminalId) | Test-portal / portal → Settings → Online payment methods → Google Pay: see your terminals, find the terminalId, and toggle Google Pay on/off per terminal. |
OAuth client credentials (clientId / clientSecret) | Provided by DNA Payments after merchant onboarding |
| HTTPS-enabled web server | Your hosting |
The OAuth credentials are used to generate an access token on your backend: see Authentication for the full flow.
What DNA Payments handles for you
- All Google-side setup, including decryption of the encrypted payment token returned by Google.
- Server-to-server authorization of the decrypted card data against the acquirer.
You only need a DNA Payments terminal with Google Pay enabled and a public HTTPS-hosted page. You do not need a Google Pay & Wallet Console account or any signed Google Pay merchant agreement for production processing.
Google Pay does not work in WebView
Google Pay is not supported in WebView contexts (WKWebView, WebView, WebView2). Open the checkout in an external browser instead:
- Android: Chrome Custom Tabs or the user's default browser.
- iOS:
SFSafariViewControlleror the user's default browser.
With these prerequisites in place, you are ready to move on to Integration.