- From: Dave Longley <notifications@github.com>
- Date: Wed, 03 Feb 2016 09:47:30 -0800
- To: w3c/webpayments <webpayments@noreply.github.com>
- Cc: webpayments <public-payments-wg@w3.org>
Received on Wednesday, 3 February 2016 17:48:13 UTC
I have a lot of agreement with Shane (keep it simple and only optimize when needed), but I also like @adrianhopebailie's latest suggestion of defining a root (common) set of parameters at the top-level and then including payment method specific data and overrides in the `acceptablePaymentMethod` section. I think that approach might be simple enough to understand and it addresses redundancy concerns. I'd like to hear more opinions from others on these two approaches. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/77#issuecomment-179371460
Received on Wednesday, 3 February 2016 17:48:13 UTC