FYI, I've updated this pull request with a compromise to filter standardized payment methods (e.g., "basic-card") using `capabilities`, but fire `CanMakePaymentEvent` in payment handlers that support only URL-based payment method identifiers (e.g., "https://android.com/pay"). One interesting edge case to consider is when a merchant request payment via either type of payment method (e.g., both "basic-card" and "https://android.com/pay") and the payment handler also has support for both of these. In this case, I propose that the user agent does not fire the `CanMakePaymentEvent` and behaves as if the payment handler returned "false" for the URL-based payment method. The standardized payment method can still be used in this case. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-handler/pull/170#issuecomment-335266028
Received on Monday, 9 October 2017 19:44:25 UTC