On this page, you can find additional configuration for adding Google Pay to your Drop-in integration.
When shoppers select Google Pay, Drop-in presents the Google Pay payment sheet where shoppers choose a card they want to use. If shoppers select a card that requires 3D Secure authentication, Drop-in also handles redirecting shoppers to another website to complete the verification.
Before you begin
Before starting your Google Pay integration:
- Build a Drop-in integration.
- Follow the setup steps in the Google Pay documentation.
- Add Google Pay in your Customer Area.
You don't need to send additional fields for Google Pay. See the /payments endpoint API reference for the optional fields you can send.
There is no required Google Pay specific integration for Drop-in.
You can optionally include the following properties when you configure
||Your Google Merchant ID. This can be anything for testing. Before you go live, get your Google Merchant ID from the Google Pay & Wallet Console.||The corresponding merchant ID value from the
||The list of supported card networks that you support.||-|
||The list of fields that are supported to authenticate a card transaction. Possible values:
- PAN_ONLY:associated with payment cards stored on file with the user's Google Account. Returned payment data includes personal account number (PAN) with the expiration month and the expiration year.
-CRYPTOGRAM_3DS: associated with cards stored as Android device tokens. Returned payment data includes a 3D Secure cryptogram generated on the device.
||The status of the total price. Possible values:
- FINAL: the total price shown to the shopper doesn't change.
- ESTIMATED: the total price can change based on the details of the response, such as sales tax based on the billing address.
||Set to false to turn off support for prepaid cards.||true: prepaid cards from supported card networks are supported.|
||Set to true to require the shopper to enter their full billing address. Only request this if it's required to process a transaction.||false|
||Set to true to require the shopper to enter their email address.||false|
||Set to true to require the shopper to enter their shipping address.||false|
||Set to true to only show the payment button if a shopper can pay with a supported payment method.
The value that says if the shopper can pay with each allowed payment method comes from the
||The environment for Google Pay. Possible values:
- WalletConstants.ENVIRONMENT_TEST for test.
- WalletConstants.ENVIRONMENT_TEST for live.
|The corresponding environment to the
To make recurring Google Pay payments, you first need to create a shopper token and then make subsequent recurring transactions with the token.
Refer to Tokenization for more information and detailed instructions.
Test and go live
To test Google Pay, log in to a Google account and create a Google Pay wallet with the details of a real card, not a test card. When you make a test payment, the card number is automatically mapped to our test card number starting with 4111, so the real card is not charged.
You can check the status of a Google Pay test payment in your Customer Area > Transactions > Payments.
For more information, see Google Pay's test environment for Android.
Before you go live
- Make sure your API credential has the API Clientside Encryption Payments role. Check this in your live Customer Area or ask your Admin user to verify.
- Go to your live Customer Area to configure your Google Merchant ID.
- Complete all the steps in the Google Pay API deploy to production documentation for Android.
In the live environment, note that Google Pay will only be available if:
- The shopper is logged in to their Google account.
- The shopper has at least one valid payment method on their Google Pay account.