-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify the displayItems
are not shared with payment handler
#626
Comments
It is already the case that Payment Handler API does not include displayItems. Do we need to say more in Payment Request API? |
It's more about things like native apps acting as payment handlers (not really concerned about tech we control at w3c). It's unclear what happens there. |
Android payment apps don't get display items.
|
That's awesome to hear and see. Note that I want to add the note because I know it's going to keep coming up as a question (someone already asked me about this on the twitters). I want developers and users to feel at ease with the API (hence adding a note). I'm not worried that anyone is actually leaking this info out of the browser. |
@marcoscaceres thanks 👍 |
@markalanrichards, no problem. Sorry, was about to ping you on twitter to let you know I'd filed this. I'll ping you for review once I draft somethings... or if you are feeling up to it, and want to propose some text, that's also very welcomed! |
Ah, just saw you sent a pull request also. Excellent. Will make comments there. |
You may run into issues here. Showing line items in native apps is going to be a standard feature. Sending them to the bank is an entirely different thing. |
Closed via #670 |
People are concerned about their purchases being sent to third-party payment handlers (via
displayItems
) .In the privacy section, we should make it crystal clear that these don't get sent to third-party payment handlers. We might also want to tighten text around that in a normative sense.
The text was updated successfully, but these errors were encountered: