- From: ianbjacobs <notifications@github.com>
- Date: Thu, 17 Nov 2016 06:51:40 -0800
- To: w3c/webpayments-method-identifiers <webpayments-method-identifiers@noreply.github.com>
Received on Thursday, 17 November 2016 14:52:18 UTC
ianbjacobs commented on this pull request. > + <ul> + <li>Parties may mint payment method identifiers to + represent different conditions. This scalable approach may work + well for a small number of independent conditions, but + may not scale well for complex relationships.</li> + <li>Payment methods may define "filters." Merchants provide Your original suggestion had two parts: (1) filtering is defined in payment method specs. I think that is covered by the existing text. (2) support is not a normative requirement of this spec. I think silence on the matter is equivalent in this case. Your last comment is to say "why" there is no filtering behavior defined here. Do you have suggested text for that rationale? 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/webpayments-method-identifiers/pull/16
Received on Thursday, 17 November 2016 14:52:18 UTC