[objclxt]

> All this feature actually does it give you the users credit card, phone number, and billing/shipping addresses. You still have to give that information to someone like Stripe.

I used to sit on the working group for Payment Request - the primary intention of Payment Request is to get rid of checkout forms and parallel implementations of the same logic. Right now most for most implementations that means credit card entry, but the standard is designed to support any type of payment.

So if I'm running an eCommerce site and want to support PayPal, Apple Pay, and Android Pay I shouldn't need to implement three discrete SDKs and APIs - I can instead implement Payment Request (although you'll still need to process the payment information output by each of those payment mechanisms separately. Ultimately for many merchants the implementation of Payment Request will be abstracted away by their payment processor, such as Stripe).

However, there is a parallel standard to Payment Request, called Payment Handler, which is designed to allow third party payment providers to write service-worker-esque plugins to browsers to take payment directly. They're intended to work together, but it's possible for a browser to implement just Payment Request to replace autofill if they so choose.

There's also a lot of other work going on at the W3C around payment, but Payment Request and Payment Handler have the most support from browser vendors and are as such the most actively developed.