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

Wording of tokens used #5

Closed
MasterKeyur opened this issue May 12, 2017 · 3 comments
Closed

Wording of tokens used #5

MasterKeyur opened this issue May 12, 2017 · 3 comments

Comments

@MasterKeyur
Copy link
Collaborator

MasterKeyur commented May 12, 2017

Tokens issued before payment authorization:
[kp] - we can call it Token generated by physical card as all tokens do require payment authorization in form of user offering the card or entering pin.
Tokens stored in physical cards that are communicated via point of sale devices.
Tokens stored or generated in user devices and returned by native mobile payment apps.
Tokens issued after payment authorization
[kp] - we can call it Tokens issued by PSP to merchants. Here also user performs authorization by sign in merchant portal. Just want to make sure authorization is not taken in a different meaning.
After the merchant (or their PSP) has collected user credentials, the credentials are stored in a secure vault and the merchant receives a token for subsequent business activities (e.g., customer tracking).

@ianbjacobs
Copy link
Contributor

Thanks @MasterKeyur, I have made edits based on your comments. Let me know if you are satisfied.

Ian

@ianbjacobs
Copy link
Contributor

@MasterKeyur, in light of recent edits to the mission statement, are you satisfied with the text and can we close this issue?
https://github.com/w3c/webpayments-methods-tokenization/wiki
Ian

@ianbjacobs
Copy link
Contributor

Closing for now given no further comment (and mission statement continues to evolve).

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