- From: Tomasz Błachowicz <notifications@github.com>
- Date: Wed, 19 Jun 2019 11:09:58 -0700
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 19 June 2019 18:10:20 UTC
@rsolomakhin: OK. I understand your point. Would you consider embedded Payment Handler e.g. an implementation of the basic card also as a wallet? I just double checked the current version of the specification to compare the approaches. In the initial section [2. Overview of Handling Payment Requests](https://w3c.github.io/payment-handler/#model) there is a description of the flow that assumes that payment handler sets a list of payment instruments, such as individual cards, that are used by the user-agent to facilitate selection of payment credentials by the consumer. I understand the flow that the payment instrument is presented to the end-user by the browser, not the wallet or payment handler. I wonder if my reading of the specification is in line with the intent of the authors. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-handler/issues/337#issuecomment-503670256
Received on Wednesday, 19 June 2019 18:10:20 UTC