Testing and Go-Live

Before launch, test across the following combinations:

Minimum supported environments:

• Chrome (Android, Desktop)
• Safari (iOS where supported)
• Edge (Desktop)

1. Google Pay button is shown in hosted checkout when eligible
2. Google Pay button is shown in iframe checkout when eligible
3. Google Pay button is hidden when the session is not eligible
4. Google Pay payment sheet opens after clicking the button
5. Shopper can select a card and authorize payment
6. PSP backend receives payment data
7. Successful payment confirmation is shown
8. Shopper cancellation is handled correctly
9. Error states are handled and displayed correctly

1. Button uses official Google Pay style
2. Button color is only black or white
3. Button text “Google Pay” is in English
4. Button prominence is equal or higher than other wallet buttons
5. Spacing requirements are met
6. No custom button shape or font changes

Rules: Button and Branding.

1. Merchant tested the full end-to-end payment in the test environment
2. Merchant confirmed correct button rendering within their integration context
3. Merchant verified cancellation and error flows
4. Merchant signed off UAT results

Before moving the merchant to production, Gateway verifies:

• All functional and branding checklist items are completed.
• Merchant UAT is signed off.
• Production domains are confirmed.
• Production merchant identifier is issued.
• Production gatewayMerchantId is confirmed.

Sensitive for Google review Google may require integration review before granting production access. Gateway must confirm whether Google review is required for this merchant or integration type.

Submission requires:

• Completed Google Review Pack;
• Screenshots of the button in all relevant checkout contexts;
• Confirmed list of domains.

Launch is confirmed when:

• Gateway confirms production configuration is active;
• Functional and branding checklists are complete;
• Google review approval is received (if required);
• Merchant readiness for production is confirmed.

The integration is considered production-ready only after:

• Google approval is received (if required)
• merchantId is configured
• Environment is set to PRODUCTION
• The integration is deployed on a verified production domain

1. Successful testing
2. Branding compliance
3. Google review approval (if required)
4. Gateway confirmation