3 ms·
You as the user don't ever give the site a token. The site gives you a token. You then (via the browser) authorize your micropayment platform to pay that token.
by sokoloff 6y ago
You as the user don't ever give the site a token. The site gives you a token. You then (via the browser) authorize your micropayment platform to pay that token. They pay them. They can track what you're paying (but because they had to pay anyway, that information was already present). The site can't [via this information channel] track you.
- gpm 6y agoAh, so this only works on "pay per page load"? You're right, I agree that that could work in the sense of preventing the site tracking me via payment information. I don't think that's as likely a business model as "pay per month", but ok. It still comes with the previously mentioned problem of the payment provider tracking me. It also comes with the problem that that sounds really latency inducing. > but because they had to pay anyway, that information was already present Already since when? When I wasn't paying that information wasn't present.
- sokoloff 6y agoSince the time in the future if this became a standard.