3 ms·
How would it work with not creating an account? Low-friction payment methods are here. Apple and Google Pay for example work pretty well. But if I pay for acce
by criddell 5y ago
How would it work with not creating an account?
Low-friction payment methods are here. Apple and Google Pay for example work pretty well. But if I pay for access to something today, how do you know it's me when I return a year later and want access again?
A good password manager can make creating an account almost effortless. Maybe that's part of the solution.
- phkahler 5y ago>> Apple and Google Pay for example work pretty well. But if I pay for access to something today, how do you know it's me when I return a year later and want access again? Yet another reason why identity verification by default would make the net better. No spam, easy payments, elimination of middle-men for many use cases.
- ghaff 5y agoOf course, now you're talking about essentially eliminating anonymity on the web which not everyone would want.
- ipsi 5y agoMaybe browsers should looking at adding a "create account" API or something? Similar to "Login with Apple ID", but instead password managers could hook into it and create an account semi-automatically. This could also allow automation of "user+sitename@domain.com"-style rules. I know that creating an account isn't adding _much_ friction, but there is some and I could see myself appreciating this.
- fouric 5y ago> How would it work with not creating an account? Notice that they said "yet another account" - I'm pretty sure that they're not objecting to the idea of creating a single account for the micropayments service, but instead creating a separate account for each individual service that they could instead use micropayments for. > A good password manager can make creating an account almost effortless. Maybe that's part of the solution. That was already excluded by their comment - "and giving them my credit card info" - wherein it's made clear that part of the problem is the proliferation of private data among a very large number of individual sites/services/systems. A password manager doesn't do anything at all to help secure your private information from these services that you would be signing up for.
- abacadaba 5y agoNow that you mention it though, there was some service i saw ads for that generates a new cc for each use. i forget the name maybe some here works there :) There is the privacy aspect too. Maybe I don't want [big sketchy data] to be able to buy my CC purchases and see know which creators i support.
- criddell 5y agoApple Pay does this. Merchants get a token which looks like a credit card number but isn't. If you are using an Apple Credit Card, then the processor (Goldman Sachs) is not allowed to use your purchase data in that way.
- criddell 5y agoI don't know about Google Pay, but I believe Apple Pay uses the payment tokenization scheme from EMVCo. Sites don't get your primary account number (PAN), they get a generated number that is linked to that number. SecurityNow did a podcast about it (episode 477).
- fouric 5y agoRight - that's an argument to use a centralized payment service (which Apple Pay, Google Pay, Paypal, etc. (probably) fulfill). I (might have mis-)read that part of your post as being about micro-payment systems not being necessary. I'm not sure whether or not Google & Apple pay are "micro-" enough, though. Do they charge per-transaction fees that are significant enough that 5 cent transactions are infeasible? What's the transaction time like? Can you set up 1-click payments?