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

@adrianhopebailie and @marcoscaceres,

Here is an alternative to Adrian's proposal (and something similar would be included in the canMakePayment() algorithm):

10. For each paymentMethod in request.[[serializedMethodData]]:

    1. Determine which payment apps support any of the payment method identifiers given by the first element of the paymentMethod tuple. For each resulting payment app, if payment method specific capabilities supplied by the payment app match those provided by the second element of the tuple, the payment app matches. Capability matching constitutes an extension point in this specification. User agents will match according to payment app integration approaches and payment method capabilities.


-- 
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-291251439