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 does not return live chargeable tokens in the
response, but the test environment allows us to test elements of your purchase:
- Confirmation pages
- Billing address (optional)
- Billing phone number (optional)
- Shipping address (optional)
- Email address (optional)
You will see an
Unrecognized App error on the Google Pay payment sheet until your app has
The value of the environment parameter from WalletOptions indicates whether the server is running in a production or in a test environment. The environment value can be one of the following:
For testing and development, use
Testing your integration
Before submitting your integration to Google for validation in
ensure that you've fulfilled the exit criteria for each functional and branding check below.
|Ensure that your existing risk checks and controls for card or PAN transactions are also applied to Google Pay transactions. Google Pay validation and fraud checks are not intended to replace your risk management processes.|
|Ensure that you have 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 only for transaction processing. All other use cases require a separate, express consent from the user.|
|Confirm the payment card authentication and card networks accepted by your payment processor in your country.|
If completing a
2. Branding testing
|Use our approved assets and adhere to all elements of our Brand guidelines.|
|Ensure the Google Pay payment button only appears after your app has confirmed the user's
ability to pay through the
|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 will appear.|
3. Functional testing
If requesting a
If you have confirmed your processor supports
If requesting a
If you require a shipping address, test processing of the shipping address in varied states of completion:
|If you require a telephone number, test parsing and storing the telephone number to the data standards of your app using 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 do not 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 processing the transaction. If the amount to be charged has varied based on data received from the Google Pay API you are expected to show a confirmation page with a final price.|
|To expedite testing, enable test items for Google to purchase and provide instructions on how to access the Google Pay integration.|
Requesting production access
Once you validate that you've fulfilled the exit criteria for each check above, click Request production access to begin the process of obtaining production access.Request production access
Our onboarding process is as follows:
- Google reviews your submitted integration in our test environment, with the API set to
ENVIRONMENT_TEST. Any modifications required to your integration, for either functionality or branding, must be made in this step.
- With approval, Google provides you with instructions for registration and production access to the Google Pay API.
- Google reviews your submitted integration in our production environment, with the API set to
ENVIRONMENT_PRODUCTION, to complete end-to-end transactions.
- With approval, Google provides launch clearance.
We evaluate your integration based on each check above and notify you of any errors found. If no errors are found, we provide further instructions for onboarding and testing in production.