- From: ianbjacobs <notifications@github.com>
- Date: Tue, 13 Jun 2017 08:03:23 -0700
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/payment-handler/issues/173/308146114@github.com>
Hi Adrian,
Using your example as a starting point, here is what I had in mind:
- I install BobPay which allows me to identify a default payment instrument. BobPay explains to me that when I am am presented with the default payment instrument and select it, payment will be super fast with minimal friction.
- Via Payment Handler API BobPay registers three payment instruments;
* Blue-when-displayed-as-default with instrument key k1, identified as the default
* Blue with instrument key k2
* Green with instrument key k3
Note that this happens under the hood and the user doesn't have to do anything
special other than identify that blue is the default. There's a bit of redundancy
in the registration, but that's a feature.
- Payment Handler API states that the browser displays either k1 or k2+k3.
Thus:
* Some details for the blue payment instrument will be common to k1 and k2.
* Some information could usefully be different, such as the displayed string
* Because the instrumentKeys differ, the handler knows which one the user selected.
* The behavior for k1 and and k2 could differ even if the card number (etc.) is the
same.
I should have provided this example in my post; thanks for prompting it.
Ian
--
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/173#issuecomment-308146114
Received on Tuesday, 13 June 2017 15:04:02 UTC