- From: ianbjacobs <notifications@github.com>
- Date: Fri, 08 Feb 2019 10:21:07 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 8 February 2019 18:21:28 UTC
ianbjacobs requested changes on this pull request. > algorithm. </li> + <li>Let <var>handlers</var> be a <a>list</a> of registered + <a>payment handlers</a> that are authorized and can handle + payment request for <var>identifier</var>. + </li> + <li>For each <var>handler</var> in <var>handlers</var>: + <ol> + <li>Let <var>hasEnrolledInstrument</var> be the result of + running <var>handler</var>'s <a>steps to check if a payment I have a question here: Instead of "steps to check if a payment can be made" should this be "steps to check if the handler has an enrolled instrument"? And does this mean that a payment method also needs to define those steps? Does a revised basic card spec need to change the steps to be about enrolled instrument? (I don't have answers to these questions yet.) [1] https://www.w3.org/TR/payment-method-basic-card/#steps-to-check-if-a-payment-can-be-made -- 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-request/pull/833#pullrequestreview-201720590
Received on Friday, 8 February 2019 18:21:28 UTC