Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37)

> Should list of accepted payment methods be strings or objects?

They should be objects for at least the following reasons:

1. Different schemes require different data from the payee, which means that a strings-only approach cannot easily express all the metadata that goes along with a request.
2. Scheme metadata is usually bound very tightly to the payment request, so decoupling scheme metadata to a different parameter in the API call is probably a bad idea as that would make it more likely that the accepted schemes and the necessary data that is supposed to be used with them would get out of sync via developer error.
3. Structuring the information that goes along w/ an accepted scheme helps reduce the cognitive load on a developer.

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