Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63)

Hi @rsolomakhin,

Good comments and observations. It seems like there are two pieces of information the payment app should tell the user agent:

 1) Here are my options that you should display. These are the ones that match given the filter from
     the merchant. So one value returned by the lambda function is a list of option ids.

 2) Here are the relevant parts of the payment request data that you should display in light
    of the match. So a second value returned by the lambda function is some sort of index 
    identifying the matching paymentDetails or paymentDetailsModifiers. 

If I understand your comment correctly, you are suggestion there's a third piece of information:

 3) Here is the mapping of payment request details to payment options. I hadn't thought about
     that before, and still am not sure that's a requirement. 

Please confirm these are the three bits of information you think are necessary for the payment
app to tell the user agent. Thanks!

Ian

-- 
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-payment-apps-api/issues/63#issuecomment-264292892