FakecreditcardHow Google Pay test cards work
To use the test card suite, join the Google Pay test card suite group with the Google account you test with, and create the payments client with the TEST environment (environment: 'TEST' on the web, WalletConstants.ENVIRONMENT_TEST on Android). The payment sheet then lists test cards instead of the cards saved in your account, so you can work through the integration checklist and request production access without a real card.
If your gateway is in the table above, the sheet shows that gateway’s own test cards. The card you pick is encrypted into the payment token, so you can send the token to the gateway’s test environment and get a realistic response. Depending on your processor setup, a card comes back as an FPAN (the card number) or a DPAN (a device token, Android only, and only if you allow CRYPTOGRAM_3DS).
Other gateways get mock test cards: Visa, Mastercard, Discover and American Express with PAN_ONLY authentication and one US billing address. They only exercise the payment sheet and the shape of its output; a token from a mock card sent to a processor can return an error. Gateway test cards are not available with the OFFER PaymentDataCallback option.
Testing Google Pay payments step by step
- Join the Google Pay test card suite group with the Google account you test with.
- Create the payments client with the TEST environment and your gateway’s
gatewayvalue in the tokenization specification. - Open the payment sheet, pick a test card and check the PaymentData your app receives.
- Send the token to your gateway’s test environment and check approvals and declines.
- Complete the integration checklist, then request production access in the Google Pay & Wallet Console.
Common errors and fixes
- The sheet shows my real cards
- The account is in the “real data” group or not in the test card suite group. Leave the real data group to turn the suite back on.
- Processor error with a mock card
- Mock cards only test the sheet. Use a supported gateway, or test the gateway separately with its own test numbers.
- Real card returns placeholder data
- Expected: production cards return placeholder data in the TEST environment.
Sources
Everything on this page comes from Google Pay’s official documentation. Checked October 2026; gateways change their test data from time to time, so if a number stops working, check the source:
Frequently asked questions
Does Google Pay have test card numbers?
Not as a list to type in. With the TEST environment and your account in the test card suite group, the payment sheet shows test cards — your gateway’s own cards if it is supported.
Can I use Stripe test cards with Google Pay?
Stripe is one of the supported gateways, so with the test card suite the sheet shows Stripe test cards. See our Stripe test cards page for what each card does.
Why does Google Pay show placeholder card data?
Real cards saved in a Google account return placeholder data in the TEST environment. Use the test card suite instead.
Can I use these test cards on another gateway?
Usually not. Each gateway only recognises its own documented test numbers in its own sandbox. Some numbers, such as 4111 1111 1111 1111, appear in several lists, but the results they trigger differ. For format-only testing on your own forms, use our card generator.