Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684)

I am hearing you say:

 * How duplicates are handled is payment method specific. This implies that third party payment handlers will need access to all of the PMI/data tuples (including duplicates) in order to respond to canMakePayment().
 * Basic Card is expected to define an algorithm for handling duplicates, with a "last one wins"  approach when all modifiers are equivalent.
 * The PR API spec will explain that handling duplicates is payment method specific and for consistency with basic card, new payment methods should define a "last one wins" approach.

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/payment-request/issues/684#issuecomment-405612400