- From: ianbjacobs <notifications@github.com>
- Date: Fri, 31 Mar 2017 07:41:30 -0700
- To: w3c/webpayments <webpayments@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 31 March 2017 14:42:27 UTC
Hi @kayakalan, Would you be able to expand on the use cases in more detail? Here are some questions and thoughts that occurred to me: * Where will the browser get the country information used to make a determination? Will it depend on the user's browsing context, the transaction context, or something else? * I think one way to dispatch by country without adding data to the manifest file would be to publish different payment method identifiers: https://example.com/bobpay https://example.com/bobpay-kr I don't claim that's a good design, but it might be useful as a backup. * The revised proposal [1] has a supported_origins field for delegating authority. I am guessing there are times when delegation might vary by country. So it might make sense to be able to scope manifest blobs by country. But I am still interested in how the browser learns what the relevant country is, and look forward to your additional info. Ian [1] https://github.com/zkoch/zkoch.github.io/blob/master/pmi-v2.md -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/224#issuecomment-290730997
Received on Friday, 31 March 2017 14:42:27 UTC