KEMBAR78
Add privacy protection to MerchantValidationEvent's validationURL by marcoscaceres · Pull Request #850 · w3c/payment-request · GitHub
Skip to content

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Mar 12, 2019

Part of PING discussions.

The following tasks have been completed:

  • Confirmed there are no ReSpec errors/warnings.
  • Not testable Modified Web platform tests.

Optional, impact on Payment Handler spec?

If handlers will have a means of handling merchant validation, that spec should include a privacy note.


Preview | Diff

Copy link
Collaborator

@rsolomakhin rsolomakhin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the clarification. I will be sure to include this in the PH spec when adding the merchant validation feature and will add you the the PR for review.

Copy link
Collaborator

@ianbjacobs ianbjacobs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @marcoscaceres

I agree with the sentiment, but two things make me uncomfortable:

  • Imposing a normative requirement on payment handlers in this specification.
  • It would probably be ok for the URL to include some information about a person for an authorized server; we don't want that information to be visible to unauthorized parties.

Proposed:

"It is important that the validationURL in a MerchantValidationEvent
does not expose personally identifying information to unauthorized parties."

I am avoiding creating a normative requirement, but do want to stress the importance.

@ianbjacobs ianbjacobs changed the title Add privacy protenction to MerchantValidationEvent's validationURL Add privacy protection to MerchantValidationEvent's validationURL Mar 12, 2019
@marcoscaceres
Copy link
Member Author

@ianbjacobs, your suggestion sounds good. Could you please update this branch with your new text?

@ianbjacobs
Copy link
Collaborator

Hi @marcoscaceres,

I made the change and also did a tidy; I think some of the changes shown are due to tidy.

Ian

It is important that the <a>validationURL</a> in a
<a>MerchantValidationEvent</a> does not expose personally
identifying information to unauthorized parties.

to e13799f

without doing a tidy first
@marcoscaceres marcoscaceres merged commit 26fbcf9 into gh-pages Mar 14, 2019
@marcoscaceres marcoscaceres deleted the merchant_validation branch March 14, 2019 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants