Creating a "Wallet" using PaymentHandler?

[cyberphone]

It is clear that PaymentHandler should work for major payment providers like PayPal who have their own payment button in checkout forms.

Now, imagine a world with potentially thousands of independent payment providers. Using the current specification this would force merchants relying on the browser's built-in selection mechanism. Since each provider would need to supply their own PaymentHandler code, this scheme will likely contribute to fragmentation rather than standardization.

This contrasts to native payment handlers like Apple Pay where a single instance of the client software can support multiple payment providers.

Example running on desktop browsers: https://cyberphone.github.io/doc/saturn/ui-demo

Disclaimer: I'm not an expert on PaymentHandler or ServiceWorker.

[ianbjacobs]

Closing this as this is not an issue on the specification.

[cyberphone]

If my findings are correct (which I don't know for since I'm not an expert on this), the specification suffers from limitations that may need to be dealt with.
@marcoscaceres @rsolomakhin @danyao

[cyberphone]

As a comparison, the payment method the WG started with (basic-card), has all the characteristics of an issuer- and domain-independent wallet, at least as implemented in Chrome.
@adrianhopebailie