Hi @marcoscaceres,
I changed the title back to the original title. The original use case from @mattsaxon was for the merchant to say to the browser (or other payment handler): don't collect the CVV; I would rather the user have less friction and I accept the increased risk.
One proposal had been that each payment method might support an array in request data where the merchant could specify which response fields to exclude when building the response.
Since the original use case ("don't collect CVV due to friction") other use cases have arisen:
* The user doesn't want to share information for privacy reasons.
* The merchant doesn't want to collect information for liability reasons.
I would prefer that this issue remain merchant-focused (rather than user-focused). The original issue is that the merchant wants to indicate which payment method response fields it wants the payment handler to exclude.
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-method-basic-card/issues/5#issuecomment-442219747
Received on Tuesday, 27 November 2018 21:16:06 UTC