For details, see the Google Developers Site Policies. The debug key doesn't work in the production environment.Įnvironment parameter to WalletConstants.ENVIRONMENT_PRODUCTION.Īfter a review and with launch approval from Google, you can launch your app to the Google PlayĮxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. Make sure that your APK is signed with the release key, not with the debug key you used in the.Use the following steps to configure your app for production: Match the SHA1 fingerprint provided to Google Play. Keytool -printcert -file META-INF/CERT.RSA First extract the META-INF/CERT.RSA from the APK The key used for signing it with the following commands: Once an Android app is signed, you can verify the fingerprint of To resolve this error, make sure that the fingerprint provided to Google matches the fingerprint of the This error typically occurs after an app in development switches from the test environment to the Used to sign the Android app doesn't match the release key fingerprint registered with Google Play. When your app is pointed to the Google Pay API production environment, the Google Pay API returnsĮRROR_CODE_MERCHANT_ACCOUNT_ERROR ( 405) if the signing key fingerprint You must complete all of the steps outlined in the

Important: Before you can start to accept real payment credentials, This section describes how to configure your app to production and start to accept real paymentĬredentials.

Google pay apk