Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77)

I am also towards keeping each method's properties completely separate.
Data common to more than one method may be duplicated, but I believe it'll be simpler to build the request this way (from the website's point of view).

If we go for the initial proposal ("merging" data common to more than one method into a single object) we assume that the website have this capability, which it may not (if modules handling payment methods are separate, maybe provided by different companies..). 

Also, how to decide 'what' to merge: properties having the same key goes into the common object? Can we safely assume that there won't be properties with the same name but different meaning in two different payment methods?

Reply to this email directly or view it on GitHub:

Received on Thursday, 4 February 2016 02:24:08 UTC