in-app-billing

This is the first time I am implementing in-app billing in android app and I took most of the code straightly from guideline and everything forget perfectly til I thought about refunding. The example app has already refunding implemented, but in a weird way! Refund is received on app as purchase but with state of refund which is totally understandable but the original source looks like this: // Count the number of times the product was purchased while (cursor.moveToNext()) { int stateIndex = cursor.getInt(2); PurchaseState state = PurchaseState.valueOf(stateIndex); // Note that a refunded

I was wondering how to detect a refund, or any type of cancelation of an in-app purchase(not a subscription and not a consumable). I'm currently making my test and when I refund a test in google like that : The purchase is still present in billingClient.queryPurchaseHistoryAsync() (even in queryPurchase() ). How can I detect such changes and how can I disable my app for refunded users? Thanks in advance. Have to tried this function PurchasesUpdatedListener Listener interface for purchase updates which happen when, for example, the user buys something within the app or by initiating a purchase

I've been playing around the the Dungeons app and also my own billing code and pretty much have everything working except for one strangeness. It seems that no matter what I do I can't get the DEVELOPER_PAYLOAD to show up in the JSON signed response. If I'm reading thing right, the docs seem to say that I should see the developer_payload in the JSON market response. The Dungeons app seems to think it should see the developer_payload in the json too. I haven't gotten it to work in my code and it doesn't seem to work in the Dungeons example either on my phone. Here are some snippets of my code:

My Project is in Plyatore beta. The project contains subscription as monthly and yearly. So I added a Sandbox settings with 8 Gmail id's for testing the subscription.Then I configure each Gmail id in device account settings, only two Id is getting purchase dialog. Remaining 6 Gmail id's are getting one error message as "the item you requested is not available for purchase". Is anyone has the same problem occurred, or anyone has the solution please help me to fix the issue. The mail id is separated with a comma in the sandbox filed in Playstore account. Also, each mail id has a valid credit

I want to use Google Play's in-app billing for one of my applications. But it seems I can't use it. First problem is that according to supported locations for merchants my country - Turkey - is not in the list. And as a second problem , my app is listed on some other markets except Google Play. Google Play in-app billing overview section In-app Billing Requirements and Limitations says that In-app billing can be implemented only in applications that you publish through Google Play. Therefore even if Turkey will be in merchant list in the future, I could not use Google Play's in-app billing for

I have defined some in app products in my app. I've uploaded the apk to the Google Play and added the inapp purchase products on the Google play. I've got my ServiceConnection defined as followed: ServiceConnection mServiceConn = new ServiceConnection() { @Override public void onServiceDisconnected(ComponentName name) { mService = null; } @Override public void onServiceConnected(ComponentName name, IBinder service) { mService = IInAppBillingService.Stub.asInterface(service); connect(); } }; The onServiceConnected function is called, the bindService returns true. Next is the connect function.

I have an application and I am trying to understand in-app billing. I want to do this : If a user buys an item with in-app billing. user can use this item with same account in different device without paying again. So my scenerio is this: Assume that I have a application and it has in-app billing V3 service. And then a user purchases an "Managed Product" item and the user has an another device then the user wants to install this purcashed item in other device without paying again . But I read here, people talk about this problem: BILLING_RESPONSE_RESULT_ITEM_ALREADY_OWNED At this point I am