4 ms·
https://www.w3.org/TR/payment-request/ https://www.w3.org/TR/payment-request/ On paper it looks kinda nice. I've seen some discussion about implementing it fro
by dzikimarian 3y ago
https://www.w3.org/TR/payment-request/ https://www.w3.org/TR/payment-request/
On paper it looks kinda nice. I've seen some discussion about implementing it from the payment method perspective.
Problem is that Google would be massively privileged, as browser orchestrates the process and payment methods aren't necessarily looking for the fair compromise either.
- Nars088 3y agoWhat if network tokenization becomes more mainstream? If that happens browsers would't be able to vault users' card details
- dzikimarian 3y agoI'm not sure if I fully understand your point. In this solution browser is not expected to vault card. It should just be intermediary between payment methods and payment gateways (of course saving card inside browser can be one of the payment methods). Also depends what do you mean by more mainstream. Google Pay and Apple Pay both support tokenization. So do many other payment methods - I would say that it's mainstream. Next step would be refusing plain cards at all. Google Pay is everything that Google needs for Chrome to have full solution.