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:
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.
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.paymentMethodto your server.
From your server, make a /payments request, specifying:
paymentComponentData.paymentMethodfrom 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
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.typeredirect in the response.
If you received an
actionobject, pass the
actionobject to your client app and return it inside a
If you did not receive an
actionobject, 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
From your server, make a POST /payments/details request providing:
actionComponentData.detailsobject 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
|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
|Refused||The payment was refused by the shopper's bank.||Ask the shopper to try the payment again using a different payment method.|
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 in the test environment:
- Log in to a Google account and create a Google Pay wallet.
- Enrol your wallet in the Google Pay test card suite
- Add the details for a real card to the wallet.
After you make a test payment, you can check the status of a Google Pay test payment in your Customer Area > Transactions > Payments.
When you test with a real card, it will be masked to one of our test cards, and your card will not be charged. In your Customer Area, your test transactions show test card details of the same brand.
Limitations apply when testing Google Pay:
- When testing with a wallet enrolled in the Google test card suite, you cannot test changes to your configuration in the
PaymentDataRequestobject, because the Google Pay API always returns the same output.
- When using Google's test cards, only full PAN tokens (FPANs) are returned for test payments, instead of device authenticated tokens, known as Cryptograms.
- To test 3D Secure 2, you can only 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.
For more information, see Google Pay's test environment for Android.
Before you go live
We recommend that you test the scenarios described in Google Pay’s API reference for Android in your live environment.
- 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.