This version of the application is not configured for billing through Google Play

The question:

When I try to run my application with in-app billing I am getting the error: “This version of the application is not configured for billing through Google Play. Check the help center for more information”.

I have the billing permission already in the Manifest file and I have a signed .apk uploaded as a draft onto Google Play and I have also installed that same signed apk onto my phone.

Any help on how to solve this issue?

The Solutions:

Below are the methods you can try. The first solution is probably the best. Try others if the first one doesn’t work. Senior developers aren’t just copying/pasting – they read the methods carefully & apply them wisely to each case.

Method 1

This error may be caused by several reasons.

Here is the list of requirements for the Google IAB testing.


  1. AndroidManifest must include “” permission.
  2. APK is built in release mode.
  3. APK is signed with the release certificate(s). (Important: with “App Signing by Google Play” it only works if you download directly from GooglePlayStore!)
  4. APK is uploaded to alpha/beta distribution channel (previously – as a draft) to the developer console at least once. (takes some time ~2h-24h).
  5. IAB products are published and their status set to active.
  6. Test account(s) is added in developer console.

Testing requirements:

  1. Test APK has the same versionCode as the one uploaded to developer console.
  2. Test APK is signed with the same certificate(s) as the one uploaded to dev.console.
  3. Test account (not developer) – is the main account on the device. (Main account might be not necessary – according to @MinosL comment)
  4. Test account is opted-in as a tester and it’s linked to a valid payment method. (@Kyone)

P.S: Debugging with release certificate: (Thnx @dipp for the link)

P.P.S: Wanted to make this list for a long time already.

Thnx @zlgdev, @Kyone, @MinosL for updates

Method 2

Ahh found the solution after trying for a couple of hours.

  1. Google takes a while to process applications and update them to their servers, for me it takes about half a day. So after saving the apk as a draft on Google Play, you must wait a few hours before the in-app products will respond normally and allow for regular purchases.
  2. Export and sign APK. Unsigned APK trying to make purchases will get error.

Method 3

The same will happen if your published version is not the same as the version you’re testing on your phone.

For example, uploaded version is android:versionCode="1", and the version you’re testing on your phone is android:versionCode="2"

Method 4

In the old developer console:

Settings -> Account details -> License Testing -> Gmail accounts with testing access and type here your accounts

In new developer console:

Setup -> License Testing -> Type your Gmail account, hit ‘Enter’ and click ‘Save’.

This version of the application is not configured for billing through Google Play

Method 5

You need to sign your APK with your live certificate. Then install that onto your test device. You can then test InAppBilling. If you are testing your application by direct run via eclipse to device(In debug mode) then you will get this error.

If you are using android.test.purchased as the SKU, it will work all the way, but you won’t have the developerPayload in your final response.

If you are using your own draft in app item you can test all the way but you will be charged and so will have to refund it yourself afterwards.

You cannot buy items with the same gmail account that you use for the google play development console.

Method 6

Conclusions in 2021

For all of you who concerned about debugging – You CAN run and debug and test the code in debug mode

Here’s how you can test the process:

(This of course relies on the fact that you have already added and activated your products, and your code is ready for integration with those products)

  1. Add to the manifest
  2. Upload signed apk to internal testing
  3. Add license testers (Play console -> Settings -> License testing) – If you use multiple accounts on your device and you’re not sure which one to use, just add all of them as testers.
  4. Run the application, as you normally would, from Android Studio (* The application should have the same version code as the one you just uploaded to internal testing)

I did the above and it is working just fine.

Method 7

If you’re here from 2018, you need to download the APK directly from Play Store and install the “derived” APK. Maybe it is because of Google’s Play Store has a feature “App Signing by Google Play”.

Method 8

This will happen if you use a different version of the apk than the one in the google play.

Method 9

Let me just add what happened with me, may help some one.

It was mainly due to signing.

Since I have added the signing details in the Project structure, I was thinking that every time when I run, expected signed apk is getting installed. But build type ‘debug’ was selected.

Below fix solved the problem for me.

  • Generated signed apk of build type ‘release’.
  • Manually installed the apk.

Method 10

Contrary to many answers and comments on SO and other sites, you do NOT have to perform preliminary tests with an alpha/beta version of your product that has been downloaded from Google Play onto your test device (the alpha/beta publication process often eats up half a day). Neither do you have to load and re-load a signed release apk from your developer studio to your test device.

You CAN debug preliminary Google Play in app billing services using the debug app as loaded from your developer studio directly to your test device via ADB. If you are experiencing errors that prevent this, likely you have done something wrong in your code. Pay especially close attention to the CASE of your SKU’s (product ids) and their format (for example, if you load your APK as com.mydomain.my_product_id, be sure your try to purchase it this way – providing the same case and domain). Also, pay especially close attention to your itemType – this should be either “inapp” or “subs” for managed/unmanaged in app purchases or subscriptions, respectively.

As suggested by Chirag Patel, provided you have your billing code properly established, perform all testing using the android.test.purchased Sku (product ID) during your preliminary tests. Check for this ID throughout your billing operations to pass it through signature, token and payload checks, since this data is not provided by the Google test system. Additionally, give one of your test products this ID to test its purchase, unlock/load and presentation all the way through your schema. To CLEAR the purchase, simply consume it, passing the same Sku AND a token string formatted this way – no other fields are relevant :


Once you have completed this phase of testing, move to semi-live testing with your alpha/beta product. Create a Google group (essentially a mailing list), add your test users emails to it, and add/invite this group to test your device in this phase (performed at the “APK” portion of your app’s Google developer listing). Purchases will be simulated but not actually charged – however to clear and re-test the purchases, Google indicates that you must refund them from your Google wallet. THIS is the only phase of testing that requires the time-consuming process of using alpha/beta loads and test users.

Method 11

In my case I saw the same message due to the different signatures of the installed apk and an uploaded to the market apk.

Method 12

Had the same problem, and it was not solved before i read the post from DZDomi. It suddenly occurred to be that there is a setting in the Google Developer Console that you need to enable. In the “In app purchases” section, there’s a line for your product and to the far right there’s a status for it. It should be ACTIVE!

Method 13

2022 Answer:

This is tested for debug/release builds & either if the app is signed by Play Signing (which means the signing certificate of the delivered app from Google Play is different from the certificate when installing the app from your machine using Android Studio).

check these following steps:

  1. Create your product on Google Play Console and activate it.
  2. Add license testers (open the Google Play Console -> Settings -> License Testing). Add all the Google accounts listed on your android device.
  3. Upload signed app to the internal testing track (it must be in release mode).
  4. Use the testing link to check if the app is available to download (make sure the uploaded app version to the internal track matches the version you’re testing in debug mode). It takes some time to see the latest uploaded version there, so I recommend clearing the cache of the Play Store app.
  5. Run your app in debug mode from Android Studio. (Again, the app version and build number must match the values on the published version to the internal track).

I tested that on two different Google Play Console accounts (two different apps), and it works.

Method 14

If you want to debug IAB what do you have to do is:

  1. Submit to google play a version of your app with the IAB permission on the manifest:

  2. Add a product to your app on google play: Administering In-app Billing

  3. Set a custom debug keystore signed: Configure Eclipse to use signed keystore

Method 15

Recently google has implemented a change on their systems, and since you have uploaded at least one APK to your console, you can test your in-app requests with your app with any version code / number.

Cross reference LINK

Configure gradle to sign your debug build for debugging.

android {
    defaultConfig { ... }
    signingConfigs {
        release {
            storeFile file("my-release-key.jks")
            storePassword "password"
            keyAlias "my-alias"
            keyPassword "password"
    buildTypes {
        debug {
            signingConfig signingConfigs.release

Method 16

my problem was that i tried to check it with the debug.keystore , i mean running it through eclipse.I exported it with the keystore with which i published in alpha mode(it must be published before you can test it).installed it in my phone and than i could test it normally.

Method 17

The problem also occurs, when you have added an in-app purchase after you uploaded the apk, but you have not published the application in the play store (alpha, beta and production).

Which basically means, that you have to add the In-App purchase AFTER you have published the apk in the Play store (alpha, beta and production). Otherwise you wont be able to purchase or query for the In-App purchase.

Method 18

Another reason not mentioned here is that you need to be testing on a real device.
With the emulator becoming really good, it’s an easy mistake to make.

Method 19


Just hold on a while after uploading your app on play store because google takes some time to update app versions.It will work !

Method 20

If you wanted to integrate with another app that is not published but has the same id, version code, and version name of deployed one so don’t forget to edit appname.iml file version in flutter app because I stuck on to it with the same error.

Method 21

If all the settings are OK and still you are getting the error This version of the application is not configured for billing through Google Play. Check the help center for more information.

Edit your In-App Products pricing in the Play Store or deactivate and activate the In-App products. This will solve the issue.

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Comment