- From: ianbjacobs <notifications@github.com>
- Date: Fri, 22 Apr 2016 06:59:06 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Friday, 22 April 2016 13:59:41 UTC
Hi @adrianhopebailie, Thank you for the write-up. Here are some comments on your good list. > Payment method identifiers are keys That's fine with me, but we need to make a normative statement to that effect. > These keys have a many to one relationship with a payment method Yes. > All of the details about how a payment app processes a payment request and builds a payment response and what a website must do with that response is published in the payment method specification or defined somewhere else that publishers can find it. The payment method specification also lists all of the identifiers that are currently tied to the payment method that they describe. Additional semantics MAY be implied by which identifiers (from the set defined in the payment method specification) are used. --- 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/143#issuecomment-213439760
Received on Friday, 22 April 2016 13:59:41 UTC