ProcessReceipt seems to have a weird web page

[Den_S]

You will get it when it triggers for the second time, your own code realizes you’ve already handled the receipt (for whatever reason – but clearly MarketPlaceService did not know yet you handled it!), so you tell it again “yep I’ve handled it!”

Rare exception to this:

@Den_S

Only issue you can experience with the approach outlined above is that if you credit the transaction in-game (UpdateAsync succeeds), but the Enum.ProductPurchaseDecision.PurchaseGranted return value does not get processed properly (MarketPlaceService dead or so). In that case the player can get their Robux refunded while the receipt is still (already) processed in the game itself if the ProcessReceipt does not get re-triggered in time, which is not avoidable at all as far as I know… Seems very rare, though, and does not cause unhappy players.

[ZhaoDan]

Doesn’t it seem far more likely that DS will go down than MarketplaceService? It seems weird to sacrifice the less likely one for the more likely. From what I understood, MarketplaceService itself is a fairly simple service, and it just makes calls to the ones that do the networking, so it itself should never fail (assuming perfect programmers)

[Den_S]

More likely is that the DataStore call succeeds, then everything falls apart and all services are suddely broken, I’d say. But in the end, it can (and will!) definitely go down while it should process PurchaseGranted!