Android

Incorrect mode

Cause: This error occurs due to an incorrect mode on the phone.

Fix: You have to switch the phone from SANDBOX mode to PROD mode to resolve this error.

Refer to Configure Sandbox Testing for more information.

Example error:

Internal Error: CheckEligibility error in CardNetworkTokenService vendor layer: code: 14

Invalid field length: cardHolderName

This error occurs on the Mastercard payment network when the length of cardHolderName exceeds the maximum length allowed.

The maximum length of cardHolderName is set at 27 characters according to Mastercard policy.

Refer to the Mastercard documentation for more details.

Example error:

Invalid Field Length - cardholderName"Internal Error: CheckEligibility error in CardNetworkTokenService vendor layer: code: 3

Incorrect credentials of API key

This error indicates that the project is not configured on the payment network.

You have to configure the project to be on the payment network.

Example error:

card_network_token_error_code: "AUTHENTICATION_ERROR"

Google Pay unavailable

This error occurs if one of these conditions is met:

• The issuer application is running on the emulator.

• The device does not have Google Play services installed. The Google Play services can be downloaded from the store.

• The issuer application failed to obtain access to Google's Push Provisioning API. Please cross-check the package name and fingerprint of the test issuer application with the values that have been submitted to Google in the Push Provisioning API Access Request form. If all data seem to match then escalate the issue to Google via [email protected].

• The Sandbox Environment does not have guaranteed service and can temporarily go out for a few days, but usually it doesn't take that long to come back. We suggest waiting a few days and trying the Sandbox Environment intermittently throughout the day to see if the service returns. If the issue persists or happen on PreProd or Production, contact [email protected]

Compile error due to duplicate entry of R.txt

This happens when the issuer application has the android.enableJetifier=true property set in gradle.properties.

To fix this, the issuer application may either turn off the Jetifier tool or ignore D1 SDK from being transformed by Jetifier as follows:

android.jetifier.blacklist=d1-release.aar

Example error:

> Failed to transform d1-release.aar to match attributes {artifactType=android-res}.
> Execution failed for JetifyTransform: d1-release.aar.
> Failed to transform 'd1-release.aar' using Jetifier. Reason: duplicate entry: R.txt. (Run with --stacktrace for more details.)

Push provisioning launching new app

In some rare cases the push provisioning flow can be opened as an external application, when it happens it is not possible to get the Google Pay wallet result back to the launched issuer application.

Example: push provisioning flow opens in an external application