3 ms·

There has probably been a lot of thought into problems like this, and it would be interesting to hear any real solutions used. My addition would be to pre-calc

by Cogito 7y ago

There has probably been a lot of thought into problems like this, and it would be interesting to hear any real solutions used. My addition would be to pre-calculate a checksum for the encrypted blob, and only send the decryption key after receiving the checksum from the downloader. You would then have a clear audit history showing that the user had downloaded the file completely, though you still have the possibility that they would claim the encryption key wasn't sent, or similar. I also wonder what the impact of (presumably) having to encrypt the file for each downloader individually.

zxcvbn4038 7y ago
The trick is that it’s not really a technical problem, the people receive the download just fine, they just don’t like the game, or get tired of it after a few minutes, or never had any intention of paying in the first place - so they do a charge back via their credit card issuer. That is successful just about all the time unless the cardholder and merchant have the same bank, or it is an oil/gas transaction (petroleum companies have some special arrangement where the card has to be reported stolen in order for a chargeback to be successful). I always thought that giving away a couple level demo of the game was the best way to weed out the first two categories of people. I don’t think there is much you can really do about the third. As much as it gets abused I’m glad the chargeback system exists, I’ve needed it a few times.