Google Pay Drop-in integration

Our Android Drop-in renders Google Pay in your payment form. 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.

Show Google Pay in your payment form

Drop-in uses the countryCode and the amount.currency from your /paymentMethods request to show the available payment methods to your shopper. From your server, make a /paymentMethods request specifying:

• countryCode: Country where Google Pay is supported. For example, NL.
• amount.currency: Any supported currency. For example, EUR.

Optional configuration

When creating an instance of Drop-in, you can optionally include a GooglePayConfiguration object to add custom configuration for Google Pay in your payment form.

val googlePayConfig = GooglePayConfiguration.Builder(YourContext, "YOUR_CLIENT_KEY")
   .setAmount(amount)
   // When you're ready to accept live payments, change the value to one of our live environments (for example, Environment.LIVE).
   .setEnvironment(Environment.TEST)
   .build()

val dropInConfiguration =
   DropInConfiguration.Builder(YourContext, YourDropInService::class.java, "YOUR_CLIENT_KEY")
   // When you're ready to accept live payments, change the value to one of our live environments (for example, Environment.LIVE).
   .setEnvironment(Environment.TEST)
   // Required for versions earlier than v4.5.0. When you're ready to accept live payments, change the value to ENVIRONMENT_PRODUCTION.
   .setGooglePayEnvironment(WalletConstants.ENVIRONMENT_TEST)
   .addGooglePayConfiguration(googlePayConfig)
   .build()

Make a payment

When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod.

1. Pass the paymentComponentData.paymentMethod to your server.

2. From your server, make a /payments request, specifying:

   • paymentMethod: The paymentComponentData.paymentMethod from your client app.
   • browserInfo: Required if you want to trigger 3D Secure authentication.
   • returnURL: URL where the shopper will be redirected back to after completing a 3D Secure authentication. The returnUrl can have a maximum of 1024 characters. Get this URL from the Component in the RedirectComponent.getReturnUrl(context).

   The response contains the result of the payment.

   If the shopper used a card that requires 3D Secure authentication before the payment can be completed, you receive an action.type redirect in the response.

3. If you received an action object, pass the action object to your client app and return it inside a DropInServiceResult.Action.

   If you did not receive an action object, proceed to present the payment result to your shopper.

Cards with 3D Secure: Check the payment result

Drop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the actionComponentData object.

From your server, make a POST /payments/details request providing:

• details: The actionComponentData.details object from Drop-in.

You receive a response containing:

• resultCode: Use this to present the payment result to your shopper.
• pspReference: Our unique identifier for the transaction.

Present the payment result

Use the resultCode that you received in the /payments or /payments/details response to present the payment result to your shopper.
The resultCode values you can receive for Google Pay are:

resultCode	Description	Action to take
Authorised	The payment was successful.	Inform the shopper that the payment has been successful.
Error	There was an error when the payment was being processed.	Inform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.
Refused	The payment was refused by the shopper's bank.	Ask the shopper to try the payment again using a different payment method.

Recurring payments

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, create a Google Pay wallet and add the details for a real card.

When you test with this card it will be masked to one of our test cards, so there are no charges to your card. Your test transactions show test card details of the same brand in your Customer Area.

You can enrol your wallet in the Google Pay test card suite to use their test cards, which cover a limited number of scenarios. For example, you cannot test changes to your configuration in the PaymentDataRequest object using the Google Pay test card suite because Google Pay API always returns the same output.

To test 3D Secure 2, you can use American Express or Discover cards, which trigger 3D Secure 2 challenge flows in the test environment. You cannot use any other card brands or any of Google Pay's test cards to test 3D Secure 2.

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

1. 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.
2. Go to your live Customer Area to configure your Google Merchant ID.
3. 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.

See also