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

Add SRC user recognition use case #260

Merged
merged 7 commits into from Aug 24, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 6 additions & 6 deletions privacy/use-cases/src.md
Expand Up @@ -16,12 +16,12 @@ See more [information about EMV®SRC](https://www.emvco.com/emv-technologies/

The desired user experience is that the user pushes the Click-to-Pay button and is presented with a list of registered cards.

This user recognition by SRC systems happens in a third-party
context. If third-party cookies are unavailable, an SRC system will
not be able to recognize the user across different merchant
sites. This means that the user will need to enter the SRC identity
(e.g., via a form field) and possibly other information on each
merchant site.
This experience today relies on user recognition by SRC systems
in a third-party context. If third-party cookies are unavailable, an
SRC system will not be able to recognize the user across different
stephenmcgruer marked this conversation as resolved.
Show resolved Hide resolved
merchant sites. This means that the user will need to enter the SRC
identity (e.g., via a form field) and possibly other information on
each merchant site.

### Possible Alternatives

Expand Down