Purchasing the same developer product calls 'ProcessReceipt' one more time each time it is purchased

[1waffle1 (Waffle)]

I wouldn’t be comfortable returning that the purchase was granted until it was actually processed successfully.

[TheGamer101]

@LifeInDevelopment

Ah right I didn’t read the sample code properly, anyway, I was trying to point out how the callback would get invoked multiple times if the callback were to yield, but that isn’t really documented on the wiki anywhere.

Yeah, this could definitely use more clear documentation about what guarantees are made.

@1waffle1

Is it necessary to use datastores to record the fact that the purchase was granted? Is it actually possible for ProcessReceipt to be called for the same exact purchase over multiple servers? It seems like just storing the record in a table that goes away when the server ends (and doesn’t yield when written to) would be fine.

It is possible for ProcessReceipt to the called for the exact same purchase over multiple servers, but if you have returned PurchaseGranted the chances of this happening would be insanely small (only would happen if the web was not able to receive the purchase granted request). I think recording purchases in this way is reasonable because worse case you just give someone a little more than they paid for.

[RuizuKun_Dev (Kitsune)]

More Info On ProductPurchaseDecision Behaviour

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

YES! we need more Documentation!