3 ms·
Seems like this shouldn't be the default. As accepting and then refunding a payment is so uncommon, it should require extra code for that case instead.
by gibolt 7y ago
Seems like this shouldn't be the default. As accepting and then refunding a payment is so uncommon, it should require extra code for that case instead.
- derefr 7y agoI think it’s for the case where the app crashes after accepting payment but before writing the granted asset token to the user’s profile. No real way around that other than two-phase commit.
- tedunangst 7y agoIf you don't deliver the purchased good, a refund seems like a reasonable default. Want to keep the money? Acknowledge you've delivered the good.
- ShinTakuya 7y agoThe issue is that if you have a bug where the feature isn't activated even if they pay, the user would lose money. It's natural that as you activate the feature you should acknowledge the purchase. Otherwise you could have bugs like double charging and such. It was an unfortunate mistake by the author, but it makes perfect sense why it happened. The person who made the mistake should lose out.