Troubleshooting

  • This guide addresses common issues and questions encountered when integrating the Google Pay API on Android, covering topics like in-app test environment behavior, request failures, registration and access errors, gateway validity, and direct merchant integrations.

  • OR_BIBED_06 request failures often point to Google Pay integration issues and can be further investigated by enabling USB debugging and examining the Android Debug Bridge (adb) logs for WalletMerchantError.

  • Several errors stem from registration or access problems, including missing API access, incorrect Google Play Services versions, and regional restrictions, which are often resolved through the Google Pay & Wallet Console.

  • Gateway-related errors like OR_BIBED_06 can arise from using unsupported or test-only gateway values in production and require contacting your payment gateway for the correct identifiers.

  • The CardInfo feature, displaying card network and last four digits, requires specific button configurations and user payment method availability, relying on the createButton API and CardParameters object.

The Android troubleshooting guide covers issues and questions related to the following topics.

App is currently running within a test environment

The user might see the following message when they choose a payment card from the payment details dialog:

App is currently running within a test environment. Transactions will not result in an actual charge

This error indicates that the app uses ENVIRONMENT_TEST and doesn't receive real payment credentials, but receives personal information that includes billing address, billing address phone number, shipping address, and email address if requested.

Request failed

The most common error message is OR_BIBED_06. This error message also appears in the UI as a dialog with the following text:

Request Failed
There is an issue with merchant's Google Pay integration. Please contact merchant for help or pay with a different method.

To learn more about this error, follow these steps:

  1. Make sure Android Debug Bridge (adb) is installed on your computer.
  2. Make sure USB debugging is enabled on your device. For more information, see Debug Your App.
  3. Connect your Android device to the computer or start your simulator.

  4. Run the following command in a terminal or command prompt on your computer:

    adb logcat -s WalletMerchantError

The response indicates the reason for the error. For example, you might see:

02-26 17:41:28.133 14593 14593 W WalletMerchantError: Error in loadPaymentData: This
merchant profile does not have access to this feature.

The action you need to take to resolve the issue depends on the error message.

Gateway validity

You might encounter the following errors related to gateway validity at some point in your integration. The following list provides some helpful troubleshooting advice should these errors arise.

OR_BIBED_06 Unknown gateway 'yourgateway'
The gateway property value you specified in tokenizationSpecification isn't currently supported by the Google Pay API. Contact your gateway for more information on their gateway identifier and associated fields, such as gatewayMerchantId.
OR_BIBED_06 Gateway 'example' cannot be used in production mode.
The example gateway property value is only used for testing purposes and can't be used with a WalletOptions environment parameter value set to WalletConstants.ENVIRONMENT_PRODUCTION. Contact your gateway for more information about the gateway parameters you need to use with the Google Pay API.

Registration and access

You might encounter the following errors related to registration and access at some point in your integration. The following list provides some helpful troubleshooting advice should these errors arise.

OR_BIBED_07 This API requires Google Play services library version 8.4+
Make sure Google Play services is up-to-date on the device that runs the app.
OR_BIBED_07 No keys found for this merchant profile
You must register your public encryption key with Google using the Google Pay & Wallet Console to complete a DIRECT tokenizationSpecification type integration.
OR_BIBED_07 This merchant profile doesn't have access to this feature.
You haven't completed the process to register your app for the Google Pay API. Review Request production access for more information.
OR_BIBED_10 This merchant is in a region where Google pay is not accepted.
The Google Pay service is not available in the region. See the list of supported countries for more information
OR_BIBED_11 This merchant has not completed registration to use Google Pay API. Please go to console (https://pay.google.com/business/console) to verify.
You haven't completed the process to register your app for the Google Pay API. Review Request production access for more information.
OR_BIBED_12 This Google Pay API integration is disabled. Please contact us for more information (https://developers.google.com/pay/api/faq#how-to-get-support).
Contact us to learn more about the required steps to re-enable the Google Pay API for your account.
OR_BIBED_13 Signing key fingerprints {11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF:11:22:33:44:55} don't match our records for this app.
The Google Pay API can only be used in production mode if the APK is signed with the correct signing key. For more information, see Sign Your App.

Direct merchants

You might encounter the following errors related to direct merchant at some point in your integration. The following list provides some helpful troubleshooting advice should these errors arise.

Signature verification
You might encounter a signature verification error if the merchantId is wrong. This can happen in the TEST environment when you use the Tink paymentmethodtoken library. To avoid this issue, set YOUR_MERCHANT_ID to in:
.recipientId("merchant:YOUR_MERCHANT_ID")
Cannot decrypt token
If you use the Tink paymentmethodtoken library to decrypt a token, take note of the following:
  • Ensure that the Google Pay API response environment corresponds with the Tink environment. For example, if the Google Pay API response was returned by ENVIRONMENT_TEST, then Tink points to the test environment for decryption.
  • Don't modify the response from Google Pay API before it's passed to Tink. Ensure that you pass the entire token returned from the Google Pay API response. For more details, see the following note:
  • Verify that you have the proper private key associated with the public key that you registered with Google.
Generate public and private key pair on Windows
If you're on Windows, and you want to follow the steps mentioned in Use OpenSSL to generate a private and public key pair, make sure you install Cygwin on your machine. This is needed to run the Linux commands.

Android WebView

OR_BIBED_15 Google Pay couldn't load properly because this App uses a WebView. App developers must follow the instructions to enable Google Pay to work within Android WebView.
Follow the instructions to enable the Google Pay API for Android WebView.

CardInfo

What is the CardInfo feature?
Google Pay indicates to consumers that there's a card behind the Google Pay payment button, which renders both the card brand network and the last four digits of the card.
Why doesn't the CardInfo feature render in my implementation?

To make the CardInfo feature work, we require the following conditions: