{"title":"Google Pay Drop-in integration","category":"default","creationDate":1776961628,"content":"

This page explains how to add Google Pay to your existing Drop-in integration.<\/p>\n

Requirements<\/h2>\n

Follow the setup instructions in the Google Pay documentation<\/a>.<\/p>\n

Select the server-side flow<\/a> that your integration uses:<\/p>\n\n

\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

API reference<\/h2>\n\n
\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

Drop-in configuration<\/h2>\n\n
\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n\n\n\n\n\n
Property<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
googlePayEnvironment<\/code><\/td>\nThe environment for Google Pay.
Possible values:
- test<\/strong>
- production<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n <\/code-sample>\n<\/div>\n

Optional configuration<\/h3>\n

You can include the following parameters in the configuration object:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Parameter<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
merchantAccount<\/code><\/td>\nYour Google Merchant ID<\/a>. This can be anything for testing. Before you go live, get your Google Merchant ID from the Google Pay & Wallet Console<\/a>.<\/td>\n<\/tr>\n
merchantInfo<\/code><\/td>\nThe merchant name that shows on the payment form. For more information, refer to Google Pay API documentation on MerchantInfo<\/a> for more details.<\/td>\n<\/tr>\n
totalPriceStatus<\/code><\/td>\nThe status of the total price. Possible values:
- finalPrice<\/strong>: the total price shown to the shopper doesn't change.
- estimated<\/strong>: the total price can change based on the details of the response, such as sales tax based on the billing address.
notCurrentlyKnown<\/strong>: the total price is not known.<\/td>\n<\/tr>\n
allowedCardNetworks<\/code><\/td>\nThe list of supported card networks<\/a> that you support.<\/td>\n<\/tr>\n
allowedAuthMethods<\/code><\/td>\nThe list of fields that are supported to authenticate a card transaction. Possible values:
- panOnly<\/strong>: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.
-cryptogram3DS<\/strong>: associated with cards stored as Android device tokens. Returned payment data includes a 3D Secure cryptogram generated on the device.<\/td>\n<\/tr>\n
allowPrepaidCards<\/code><\/td>\nSet to true<\/strong> to allow prepaid cards.<\/td>\n<\/tr>\n
allowCreditCards<\/code><\/td>\nSet to true<\/strong> to allow credit cards.<\/td>\n<\/tr>\n
assuranceDetailsRequired<\/code><\/td>\nSet to true<\/strong> to require<\/td>\n<\/tr>\n
emailRequired<\/code><\/td>\nSet to true<\/strong> to require email.<\/td>\n<\/tr>\n
existingPaymentMethodRequired<\/code><\/td>\nSet to true<\/strong> to only show the payment button if a shopper can pay with a supported payment method.<\/td>\n<\/tr>\n
shippingAddressRequired<\/code><\/td>\nSet to true<\/strong> to require the shipping address.<\/td>\n<\/tr>\n
shippingAddressParameters<\/code><\/td>\nSet any\u00a0shipping restrictions<\/a>.<\/td>\n<\/tr>\n
billingAddressRequired<\/code><\/td>\nSet to true<\/strong> to require the billing address.<\/td>\n<\/tr>\n
billingAddressParameters<\/code><\/td>\nThe expected fields returned if billingAddressRequired<\/code> is set to true. For more information on the available fields, refer Google Pay API documentation on billingAddressParameters<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

You can refer to the GooglePayConfiguration<\/code> class in Github<\/a>.<\/p>\n\n

\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

Test and go live<\/h2>\n

To start testing Google Pay, log in to a Google account and create a Google Pay wallet.<\/p>\n

There are two approaches to using this wallet for testing:<\/p>\n