Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634)

Hi @chinnagogulapati,

Card data is only available after the user has selected a payment app and approved payment. At this point, the party that called the API can evaluate the response data and determine what action to take, including sending a message to the user and relaunching Payment Request API.

Receiving user data before the user has agreed to pay seems problematic from a privacy and security perspective. 

One way to approach this might be to create a new payment method where there is additional data (from the merchant or their service provider) that is made available to the payment app. The payment app could then do some sort of back end validation and try to improve the user experience in the payment app, before returning the final (validated) data back to the merchant side.

Would that make sense and be useful? If so, what would the additional input data be for this payment method?

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/634#issuecomment-333643329