Re: [w3c/browser-payment-api] Add extension point (#492)

Three payment method specifications so far (Basic Card, Tokenized Card, Credit Transfer) involve filters. The decision was to have browsers do the filter matching, but to leave the spec underspecified as to how that happens. We have proposed concrete algorithms for string set matching (so that we would know moving forward exactly what behavior to rely on) but the preference of implementers was to not specify an algorithm at this time.

The key conclusions we reached are: filter/capability matching will happen in the browser, that payment handler API will talk about how to register capabilities with the browser, and that W3C payment method spec writers can define filters. 

-- 
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/browser-payment-api/pull/492#issuecomment-300778420