- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Tue, 08 Dec 2015 09:03:25 -0800
- To: w3c/webpayments <webpayments@noreply.github.com>
Received on Tuesday, 8 December 2015 17:04:18 UTC
Migrated from a thread on the Web Payments IG mailing list: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Dec/0039.html There is not a 1:1 relationship between a payment app and a payment instrument. I will update the documentation because this is misleading. A payment app is more akin to a wallet but by using this terminology we do away with the fact that the wallet metaphor has not worked in our context. For example, a user may register a payment app from their bank and this may support payments using all of the payment instruments they have from that bank. While I recognise the closeness in terminology to EMV apps on a chip but I think the term app is most appropriate for what the component does and is sufficiently generic (and EMV sufficiently specialised a field) that this is not a problem. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/31
Received on Tuesday, 8 December 2015 17:04:18 UTC