Re: [w3c/browser-payment-api] Supporting push payment methods (#224)

Hi @adrianhopebailie,

Here are some comments on your three proposals.

> 1. Payment Requests should all be generated with a universally unique identifier.

Do you mean: For the purposes of payment app / browser communication
about transactions (e.g., to learn state following a network outage), the payment
app specification will define how browsers MUST provide browser-generated identifiers
per transaction when they launch a payment app?

I phrase it this way to see whether it makes sense as a requirement in scope for the payment app spec. I want to distinguish the purpose of these identifiers from other identifiers that might be circulating in the system (e.g., merchant generated identifiers that they use for their own internal
purposes, e.g., for returns).

> 2. Payment Requests for push payments should include a callback URL

In spec terms, I hear: The payment request API specification should be modified to include
a standard field for payees to (optionally) specify a callback URL for payment apps to contact
the merchants directly. While I understand the idea, how would this work in practice?
Because of the standard, all payment app developers would know that they could reach
a merchant through a service identified by that URL. But how would payment app developers know how to interact with that service (e.g., what the parameters and responses would be)? What
would be the interoperability gain in practice?

> 3. The browser should raise an event when a payment app is invoked

> When the browser passes the flow control to the payment app it should notify the website which 
> payment app was selected (and therefor which payment methods may be used to process the 
> payment).

I don't understand this requirement. It seems to me that when the promise resolves, the merchant gets back data. It seems appropriate at that time to identify the payment method, so that the response data can be routed appropriately. But why does the merchant need to know which payment app was used? 


---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/224#issuecomment-238373382