Re: [webpayments] Abstract payment architecture (#11)

Hey Adrian,

A few random remarks/questions:
1/ The examples definitely help. I think the "Browser with remote Payment Apps" and "Mobile platform" are the most two common cases considered and should be first.

2/ Love the renaming of the components. We might be missing one type of component that describes the various sources (and destination) of funds in a single payment method. Payment Account could work?
For instance, for bitcoin payment method, that would be bitcoin addresses, for Visa payment method, that would be credit card numbers.

3/ What's the impact of describing methods through a manifest? In particular, is it easy to add a new payment method / account after install if we use manifests?


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/11#issuecomment-158116788