More Info On ProductPurchaseDecision Behaviour

[RuizuKun_Dev (Kitsune)]

I made a thread about this a long time ago, but it is time to do it again because now we have this Sub Category

@RuizuKun_Dev

I already did a quick search and I found no documentation on

Enum.ProductPurchaseDecision.NotProcessedYet

Enum.ProductPurchaseDecision.PurchaseGranted

My question is what happens when the Player leaves the game and re-enter?
There is no documentation on “Enum.ProductPurchaseDecision.NotProcessedYet” Behaviour as I already mentioned I think that it would be useful if more information can be provided .

I have no problem with the current Behaviour nor my scripts are broken because of this however I want to know if there is a way to Cancel the purchase?

@Corecii

We need documentation on the whole process, what the guarantees are, and all of its behavior. We need a fully-implemented example, not a partial example like the ProcessReceipt wiki page has. We need a list of best practices for handling developer products. All of this information should be linked to from the ProcessReceipt wiki page, the ProductPurchaseDecision wiki page, the wiki pages for the decision enums, and the MarketPlaceService wiki page.

The example at Handling multiple developer products is much better, but I don’t think it’s complete and it’s not clear enough. I think the example on the ProcessReceipt wiki page should be removed entirely – incomplete examples will lead to improperly programmed ProcessReceipt functions. An incomplete example is a bad example.

Also, the Developer Products page has an even worse example. Purchases are too complex to tell developers “figure it out yourself” or “dissect this example that lacks clear steps and reasoning”.