Skip to content
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

Maybe avoid mention of hasEnrolledInstrument for now? #33

Open
marcoscaceres opened this issue Apr 30, 2020 · 1 comment
Open

Maybe avoid mention of hasEnrolledInstrument for now? #33

marcoscaceres opened this issue Apr 30, 2020 · 1 comment

Comments

@marcoscaceres
Copy link
Member

The architecture doc says:

Furthermore, the "hasEnrolledInstrument" method enables merchants to determine whether the user can support SRC payments, especially valuable in a guest checkout scenario. Merchants do not have access to this type of information through other means.

but "hasEnrolledInstrument" remains controversial from a privacy perspective.

@ianbjacobs
Copy link
Contributor

I'm ok to remove it from the benefits section. However, I think it's important to leave elsewhere in the document (e.g., in the flow descriptions). If we change the spec we should update these materials.

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

No branches or pull requests

2 participants