Google payments are being automatically refunded.

Yes, good catch and is likely the cause.

 

Please refer to this URL:
https://developer.android.com/google/play/billing/integrate#pending

"To enable pending purchases, call enablePendingPurchases() as part of initializing your app."

Can we disable pending purchases for Unity IAP in any way?
I prefer to have it disabled until it's available in a reliable and non-exploitable manner.

(And why does Google call it pending purchases )

 

No, we already checked. It is required. Do you have the deferred callback? What exploit are you seeing? Have you implemented the deferred listener?

 

exploit:
The exploit you talked about in these posts:
https://forum.unity.com/threads/goo...-automatically-refunded.1033057/#post-6874100
https://forum.unity.com/threads/goo...-automatically-refunded.1033057/#post-6891062

deferred callback?
no. Does it fix it? What should I code in this callback?

 

The exploit is when the developer has a "Please wait" dialog up, waiting on ProcessPurchase and the user exits the app (is my understanding) with the dialog up. So if you receive the deferred callback, you know not to display the message. This should bypass the exploit. If you have no such dialog, my suspicion is users are legitimately attempting a deferred purchase but then not paying in the 3 days allowed. In addition to the Consume checkbox mentioned previously, if you are using Codeless.

 

I didn't touch Unity IAP for years (didn't update the code or update the version of the library), but recently I got a warning from Google to update the billing library to version 3. So, I decided to update In App Purchasing to 3.0.2. After releasing my game with this In App Purchasing version, I got the auto refund problem.

I came to this thread and saw @JeffDUnity3D replied that In App Purchasing 2.2.2 and Unity IAP 2.2.7 should fix this problem. I downgraded the library to these version and I'm still waiting to see the result, but I'm not that confident about it though.

 

If you are using Codeless, ensure that you select the Consume checkbox for the IAP Button property in the Inspector. Also, please provide your device logs. Place Debug.Log statements throughout your purchasing code to follow your logic, they will show in the device logs https://forum.unity.com/threads/how-to-capturing-device-logs-on-android.528680/ . And "waiting to see the result", what are you waiting on?

 

I'm back.

Recently, while uploading the Unity version, the App Purchasing library version was also uploaded.
- Unity 2021.1.4f1
- App Purchasing library 3.1.0

In the 3.x version, it was stated in the manual that the Unity IAP (Asset Store plugin) should be deleted, so the Assets/Plugins/UnityPurchasing folder was removed. After updating to this state, the automatic refund problem started to occur again.

The package manager indicated the recommended version of In App Purchasing as 3.0.2. Is there any problem with this version? It is difficult to test the game in service again, so I think I will have to lower the version of the library again right now.

 

Without steps to reproduce, the device logs, or seeing your code, unfortunately there isn't much I can suggest. It works correctly in the Sample IAP Project v2 https://forum.unity.com/threads/sample-iap-project.529555/#post-6950270

 

I am using IAP 2.2.7, and I'm experiencing an issue in testing where if I do a "Slow test card. Declines after a few minutes" purchase and exit the app (by closing it normally). When I re-enter the app my profile gets credited with the currency from the purchase that should have failed whether or not I wait 5-10 minutes before exiting the application. The products I am testing purchasing with are set to be consumable.

My intended result from this test purchase is to have no money charged and no currency granted.

I have also found that if I'm to try and get a purchase receipt at the time of the deferred purchase listener it either comes back as " " or a previously successful.

 

Yes, this looks to be a Google issue, slow decline does not look to work correctly.

 

Hey JeffDUnity3D,

I got the same 72Hour Non Consumable Problem as discussed above.
I ve checked on all things (Inspector - Consume Product Check Box is Checked, Automatically Init UnityPurchasing is checked)

Here is my code: (did I missed something in order for Google to recognize that the user received the non consumable)

Code (CSharp):

1. public void onPurchaseComplete(Product product)
2.     {
3.         if (product.definition.id == adFree)
4.         {
5.             //remove ads
6.             PlayerPrefs.SetInt("adFree", 1);
7.             PlayerPrefs.Save();
8.             PurchaseCompleted();
9.  
10.         }
11.         else
12.         {
13.             Debug.Log("Shouldnt be visiable ");
14.  
15.         }
16.     }
17.  
18.     public void onPurchaseFailed(Product product, PurchaseFailureReason reason)
19.     {
20.         Debug.Log("Purchase Failed: " + reason);
21.     }
22.  
23.     private void DisableRestoreBtn()
24.     {
25.         if (Application.platform != RuntimePlatform.IPhonePlayer)
26.         {
27.             restoreBtn.SetActive(false);
28.         }
29.     }
30.  
31.     private void PurchaseCompleted()
32.     {
33.         buyBtn.SetActive(false);
34.         thankYouText.gameObject.SetActive(true);
35.         if (Application.systemLanguage == SystemLanguage.German)
36.         {
37.             thankYouText.text = "Danke für den Kauf!";
38.         }
39.     }

 

Yes, we've heard similar reports with Codeless, I believe we may have a bug, it hasn't been properly updated in some time. I would recommend instead to use Scripted IAP like in the Sample IAP Project v2

 

ok I will do so, thanks for fast reply. In Case you know that the bug is fixed - please reply to this answer.
Thanks a lot and have a nice day!

 

I have the same exact problem @JeffDUnity3D all the purchases got refunded after 3 days automatically, I'm using the latest IAP and those products are marked as consumable in the codeless IAP. But the other problem here is may be related that I'm not able to buy the consumable products again as google play billing shows that i already own this product. and I'm overall confused. Please Help.

 

Hi @JeffDUnity3D,

I was testing Google Play purchases yesterday and accidently came across this 'issue' by instigating a slow credit card purchase then quitting my app (whilst a wait ui was showing)

I assumed that if I purchased, then closed the app then waited (say 10 minutes) the ProcessPurchase method would be called when initialising IAP (the next time the app was restarted) but that didn't appear to happen.

Should it have? Or should I be checking transactions\receipts on init and activating in-game content as well?

What was received was an mail from Google (after 5 minutes) saying...

This test purchase was cancelled because it was not acknowledged. You should ensure that all purchases are acknowledged so that they are not subject to refunds. For more information, see https://developer.android.com/google/play/billing/integrate#process

So after a little investigation, I saw this thread and realised the deferred listener has not been implemented, which I'm just doing now.

Are you saying that best practice is to close the waiting ui? Or warn users that the purchase is slow and to wait?

PS: This is using scripted Unity IAP 3.2.3

 

You cannot close the waiting UI, that is a system dialog. And warn which users, you mean your testers using the slow credit card option? You would not know the credit card was "slow". Are you seeing the deferred listener being called?

 

Thanks Jeff.

Yes sorry, I meant the game (purchase) ui.

It looks like I wasn't handling the GoogleReceipt.purchaseState == 4 correctly in ProcessPurchase (receipt validation). But implemented both listener and state check now and looks like all is working as expected on an internal test track.

Is it under consideration to push requirements like these (purchaseState == 4) to the Unity API by any chance? It would certainly help us devs greatly.

I've just seen Unity IAP V4 which appears to have a huge number of improvements\changes, some along those lines. So maybe it already has been.

 

We are still discussing purchaseState = 4 handling

 

I've just been working through deferred purchases on iOS and as far as I can tell, Apple's billing system doesn't call ProcessPurchase until the transaction has completed (i.e. monies received). Which makes more sense to me.

So if it were possible, Unity IAP supressing the ProcessPurchase call for Google (when the state is deferred - 4) until it's completed (1?) would get a vote from me.

That way we just need to handle the deferred payment message in the deferred purchase event and that's it. It's a simpler and more consistent approach.

Anyway, that's just my two cents worth

 

That's actually a good idea. But keep in mind that developers are already coding for the current flow and such changes would break their flow. To be clear, that is not a "good reason" to keep it as it is! We have been discussing this and similar issues here, and how to best handle it.

 

Thanks @JeffDUnity3D

That's a fair point.

But assuming developers are checking either purchaseState == 4 or using IsPurchasedProductDeferred then I don't believe it will break that workflow. In-effect that code will never end up being called. Unity IAP will intercept (set the state to pending) then discard the ProcessPurchase and call the deferred event.

Anyway, appreciate that you have it under consideration whatever the resolution. Thank you

 

In your example, developers would never see purchaseState = 4. But agreed, I guess the code wouldn't break, it would just never be called.

 

We do exactly the same in our plugin's IAP billing feature. This is to match with iOS and no doubt, this suggestion is a great one to have.

 

there is any solution for purchaseState = 4 now?

 

The solution is to check the state in the ProcessPurchase method and do nothing when the Google receipt's purchaseState value = 4.

 

@JeffDUnity3D is this fixed in 4.6.0 codeless implementation? Im facing this issue in my new game rn... Can you imagine the loss of income this generates? It's not funny on this level of app development.

 

Thank you agorain. I need to check it, but what if the state value is not equal to 4?
And what exactly means this 4 and other states? There is any docs for this?

 

FWIW

It looks like Unity has finally addressed this 'issue' in 4.6.0, from the changelog...

• GooglePlay - `Deferred` purchases are, by default, no longer sent to `IStoreListener.ProcessPurchase` when fetching purchases. This avoids the possibility of granting products that were not paid for. These purchases will only be processed once they become `Purchased`. This can be reverted with `IGooglePlayConfiguration.SetFetchPurchasesExcludeDeferred(bool exclude)` to not exclude them, but `Deferred` purchases will need to be handled in `IStoreListener.ProcessPurchase`.

I've not tested this though.

But it also looks like 4.6.0 has a number of breaking changes, so it's worth being mindful of that.

 

I just lost ~1000$ value of automatically refunded items. Shame. Still figuring out what happened, but I guess it's Unity.

 

False alarm. Issue was - if right after transaction happens error, IAP can't tell bank that item was successfully bought. And it causes refund.