- From: Dave Longley <notifications@github.com>
- Date: Thu, 21 Apr 2016 14:27:37 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Thursday, 21 April 2016 21:28:06 UTC
@adrianhopebailie, > The implementers of the payment method logic (payment apps and websites) are not going to be able to dynamically support new payment methods by merely fetching a machine readable payment method specification. That isn't the only thing you can get from machine readable data. What if you just want to get descriptions or icons? What if there are terms of use or rules that indicate you must display brand image X (found at a URL specified in the machine readable data) when offering a payment method? --- 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/browser-payment-api/issues/150#issuecomment-213120662
Received on Thursday, 21 April 2016 21:28:06 UTC