A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developers.google.com/pay/api/android/guides/test-and-deploy/integration-checklist below:

Integration checklist | Google Pay API for Android

Skip to main content Integration checklist

Stay organized with collections Save and categorize content based on your preferences.

Use the following checklist to ensure you've completed all of the required steps in your Android integration.

About the test environment

Our test environment doesn't return live chargeable tokens in the PaymentData response, but the test environment allows us to test elements of your purchase:

An Unrecognized App error appears on the Google Pay payment sheet until your app has production access.

The value of the environment parameter from WalletOptions indicates whether the server runs in a production or in a test environment. The environment value can be one of the following:

For testing and development, use WalletConstants.ENVIRONMENT_TEST.

Test your integration

Before you submit your integration to Google for validation in ENVIRONMENT_TEST, ensure that you've fulfilled the exit criteria for each of the following functional and brand checks.

1. Basics Ensure that your current risk checks and controls for card or PAN transactions are also applied to the Google Pay transactions. Google Pay validation and fraud checks aren't intended to replace your risk management processes. If you selectively trigger 3D Secure (step-up authentication) for normal card transactions based on risk criteria, be sure to use the same risk criteria to trigger 3D Secure for Google Pay PAN PAN_ONLY transactions. Ensure that you've read and are ready to accept our Terms of Service. Registration with the Google Pay API requires that you have access to the account owner email address of your Android application. Use the data received from the Google Pay API to process transactions only. All other use cases require separate, express consent from the user. Confirm the payment card authentication and card networks are accepted by the payment processor in your country. If you complete a DIRECT tokenizationSpecification type integration, you must annually rotate your public encryption key and provide PCI Attestation to Google via the Google Pay & Wallet Console. PCI Attestation can be submitted by a third-party or Qualified Security Assessor certified by the PCI Security Standards Council, and approved by an Approved Vendor or Qualified Assessor. 2. Branding tests Create the Google Pay payment button using the PayButton API to adhere to all elements of our Branding guidelines. Ensure the Google Pay payment button only appears after your app has confirmed the user's ability to pay through the isReadyToPay() function. Confirm that the displayed Google Pay payment button dimensions match similar buttons and elements on the page. Choose an appropriate button based on the background color of the area where it's intended to appear. 3. Functional tests Key Point: You can now leverage our new test card suite to complete the following checklist.

When you request a CARD payment method type with PAN_ONLY card authentication, complete the cards on file test:

  1. If applicable, remove all cards from the Google Wallet application.
  2. If applicable, remove all cards on file from pay.google.com.
  3. Return to your integration.
  4. Click Google Pay.
  5. Validate that you see the option to add a card.
  6. Add a card from a supported network, as defined in allowedCardNetworks.
  7. Validate that you see the added card with a network logo in the selector.

When you request a CARD payment method type with CRYPTOGRAM_3DS card authentication, complete the Android device token test:

  1. Check that your card issuer is supported, and add an eligible card in the Google Wallet application.
  2. Return to your integration.
  3. Click Google Pay.
  4. Validate that you see the added card with card art in the chooser.

If you've confirmed that your processor supports CRYPTOGRAM_3DS card authentication, you might proceed, even if CRYPTOGRAM_3DS card authentication isn't available to you as an Android user or cardholder.

If you require a shipping address, test processing of the shipping address in varied states of completion. Try the following methods:

If you require a telephone number, test the parse and storage of the telephone number to the data standards of your app for different formats such as +14155551212, 14155551212, (415) 555-1212. Ensure that Google Pay is displayed on parity with other third party payment methods. For users who don't have any payment information stored on their account within your app, Google Pay should be defaulted or shown prominently as the payment method. For users who previously selected Google Pay at checkout and indicated Google Pay as their preference for payment within your app, Google Pay should be the default payment method for their subsequent purchase. A final price must be displayed to the user before the transaction is processed. If the amount to be charged has varied based on data received from the Google Pay API you're expected to show a confirmation page with a final price.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["Use the checklist to confirm completion of all integration steps for Google Pay on Android."],["Before production, ensure fulfillment of functional and brand checks using the test environment (`WalletConstants.ENVIRONMENT_TEST`)."],["Review the basics including terms of service, data usage, and risk management alignment with existing processes."],["Adhere to branding guidelines using the PayButton API and ensure proper button placement and functionality."],["Test integration thoroughly, including payment methods, shipping, contact information, and UI elements, using the provided test card suite."]]],["This document outlines testing requirements for Android Google Pay integration. Use `WalletConstants.ENVIRONMENT_TEST` for testing. Apply existing risk checks to Google Pay transactions. Ensure adherence to Terms of Service and proper use of received data. Test both `PAN_ONLY` and `CRYPTOGRAM_3DS` card authentication, verify shipping address and phone number parsing. Correctly use the PayButton API. Google Pay must be displayed consistently with other payment methods, defaulting to it for new or preferred users. A final price must be shown before processing.\n"]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4