Rather than a new "cardbinchange" could we leverage "paymentmethodchange" [1]? Also: Suppose I could store the card in my browser twice: once with "Visa" as the supportedNetwork, once with CB as the supportedNetwork. The browser could show me one or both (according to what the rules require and what the merchant expresses through PR API). There would have to be some UI tests to see whether seeing the same card twice with two different networks is confusing. Then the question is: how does the browser know all the supportedNetworks? Ian [1] https://github.com/w3c/payment-request/pull/695/files -- 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-method-basic-card/issues/49#issuecomment-388907130
Received on Monday, 14 May 2018 17:58:10 UTC