Page Summary

outlined_flag

• The Google Pay test card suite enables developers to test integrations and APIs inTEST environments without using real credit cards.

• Developers can access the test card suite by joining the Google Pay test card suite group, which replaces real cards with test cards in the payment sheet.

• The test suite includes gateway-specific test cards for supported gateways, providing realistic testing scenarios with expected responses.

• If a gateway isn't supported, mock test cards are available to simulate basic payment sheet behavior, but they should not be used for end-to-end or production testing.

• Developers can leverage the test card suite to streamline the integration approval process for Google Pay and Wallet Console.

The test card suite lets Google Pay developers run integration and API tests without the need to add an actual credit card in their Google Account.

We recommend that you test your integration before you take it live. By default, when the payment sheet opens with the environment variable set toTEST, it displays a suite of test cards. Those test cards return as Funding Primary Account Number (FPAN) or Device Primary Account Number (DPAN) based on the processor configuration.

This suite helps you to complete the Integration checklist to simplify the approval process in our Google Pay & Wallet Console to request production access.

Gateway test cards

Warning: Gateway test cards are not available for integrations using the OFFERPaymentDataCallback options.

Gateway test cards

When you use the test suite with an eligible gateway, the gateway displays a list of test cards instead of our mock test card suite. When the payment sheet flow generates thePaymentData object, the selected card value is encrypted into the provided token. This lets you pass the selected card value to the gateway's test environment and receive the expected response.

The test card suite supports the following gateways:

If your gateway isn't listed in this table, refer to the Mock test cards section of this document.

Note:

• Refer to your gateway's documentation to determine which test cards support DPAN.
• If a gateway-provided test card doesn't support DPAN, it returns an FPAN.
• If your integration doesn't supportCRYPTOGRAM_3DS, test cards return only FPANs.
• DPANs are only available on Android devices.
• The test card suite doesn't affect the behavior of the payment button, only the cards displayed in the payment sheet.

Mock test cards

• Visa, Mastercard, Discover, and Amex card networks
• ThePAN_ONLY authentication method
• A single billing address in the US
• Shipping addresses in the US, Australia, Brazil, Canada, Hong Kong, Japan, Poland, Russia, Singapore, United Kingdom, Austria, Switzerland, Germany, Croatia, Czech Republic, Hungary, Romania, Slovakia, Slovenia, Serbia, and Sweden

Warning: Use the test suite only to test the payment sheet's behavior and mock its output format. It doesn't provide data intended for use in production. Tokens that are sent with these cards to a processor can result in an error.

Disable the test card suite

To see your account's saved cards in the test environment, join the real data group and disable the test card suite for your account. You can leave this group at any time to re-enable the test card suite with that account.

Warning: Production cards will return placeholder data when used in the test environment. Tokens sent with production cards to a processor in the test environment can result in an error.

Troubleshooting

Use thepublic issue tracker for PSP test cards to file any issues with this product feature. Make sure to refer to the existing issues before you create new ones.

Note: Refer to your gateway's documentation to troubleshoot unexpected responses received when you use gateway test cards.