Merged
Conversation
danyao
approved these changes
Jan 26, 2021
index.html
Outdated
Comment on lines
+4904
to
+4913
| In particular, the {{PaymentMethodData.data}} and | ||
| {{PaymentResponse.details}} members allow for the arbitrary exchange | ||
| of data. In light of the wide range of data models used by existing | ||
| payment methods, prescribing data specifics in this API would limit | ||
| its usefulness. The {{PaymentResponse.details}} member carries data | ||
| from the payment handler, whether Web-based (as defined by the | ||
| [[Payment Handler API]]) or proprietary. The <a>user agent</a> MUST | ||
| NOT support payment handlers unless they include adequate user | ||
| consent mechanisms (such as awareness of parties to the transaction | ||
| and mechanisms for demonstrating the intention to share data). |
Member
There was a problem hiding this comment.
Suggested change
| In particular, the {{PaymentMethodData.data}} and | |
| {{PaymentResponse.details}} members allow for the arbitrary exchange | |
| of data. In light of the wide range of data models used by existing | |
| payment methods, prescribing data specifics in this API would limit | |
| its usefulness. The {{PaymentResponse.details}} member carries data | |
| from the payment handler, whether Web-based (as defined by the | |
| [[Payment Handler API]]) or proprietary. The <a>user agent</a> MUST | |
| NOT support payment handlers unless they include adequate user | |
| consent mechanisms (such as awareness of parties to the transaction | |
| and mechanisms for demonstrating the intention to share data). | |
| In particular, the {{PaymentMethodData}}'s {{PaymentMethodData/data}} and | |
| {{PaymentResponse}}'s {{PaymentResponse/details}} members allow for the arbitrary exchange | |
| of data. In light of the wide range of data models used by existing | |
| payment methods, prescribing data specifics in this API would limit | |
| its usefulness. The {{PaymentResponse/details}} member carries data | |
| from the payment handler, whether Web-based (as defined by the | |
| [[[payment-handler]]]) or proprietary. The [=user agent=] MUST | |
| NOT support payment handlers unless they include adequate user | |
| consent mechanisms (such as awareness of parties to the transaction | |
| and mechanisms for demonstrating the intention to share data). |
marcoscaceres
approved these changes
Jan 27, 2021
Member
marcoscaceres
left a comment
There was a problem hiding this comment.
This seems reasonable (as far as proprietary/native payment handlers go), but it still puts the onus on the Payment Handler spec to do the "right thing"™️ with regards to privacy. That's going to be tricky with respect to the .details method because it's opaque to both the user agent and the end user.
Collaborator
Author
|
Thank you, @marcoscaceres. I have incorporated your edits into the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#936 (comment)
closes #936
The following tasks have been completed:
Implementation commitment:
Impact on Payment Handler spec: Requires payment apps to ensure adequate user consent mechanisms.
Preview | Diff