- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 14 Dec 2016 13:14:24 -0800
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Wednesday, 14 December 2016 21:15:21 UTC
> The user agent shows the user all of the Payment Apps that could be used to fulfill the PaymentRequest. This is the key step that is missing some detail. From what I understand from https://github.com/w3c/browser-payment-api/issues/307#issuecomment-267156994 , finding out what Payment Apps can be used to fulfill that payment request requires asking the payment method to do some preprocessing first. E.g. for basic card, trying to convert data (which at this point is a string) to a BasicCardRequest. Only if this succeeds will basic card then ask the payment app if it can handle the payment request. In the payment app spec that would be by calling canHandle(supportedMethods, shoppingCart) where supportedMethods contains a PaymentMethodData containing the parsed BasicCardRequest. -- 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/issues/338#issuecomment-267158477
Received on Wednesday, 14 December 2016 21:15:21 UTC