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.

Sign up for GitHub

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

Jump to bottom

Why are payment ids restricted to [a-z0-9]? #298

Closed
steveatkin opened this issue Dec 15, 2016 · 1 comment
Closed

Why are payment ids restricted to [a-z0-9]? #298

steveatkin opened this issue Dec 15, 2016 · 1 comment
Labels
s:payment-method-id https://w3c.github.io/payment-method-id/

Comments

@steveatkin
Copy link

steveatkin commented Dec 15, 2016 •
edited by stevenatkin
Loading

w3c/payment-method-id#20

4.1 Syntax
https://w3c.github.io/webpayments-method-identifiers/#syntax-1

Is there a specific requirement that identifiers be restricted to [a-z0-9-]? Are there any international card issuers that may require characters outside this range?
@r12a r12a added the s:payment-method-id https://w3c.github.io/payment-method-id/ label Dec 15, 2016
@aphillips aphillips added the pending Issue not yet sent to WG, or raised by tracker tool & needing labels. label Dec 15, 2016
@steveatkin steveatkin changed the title Need to define URL equivalence rules Why are payment ids restricted to [a-z0-9]? Jan 5, 2017
@stevenatkin stevenatkin removed the pending Issue not yet sent to WG, or raised by tracker tool & needing labels. label Jan 5, 2017
@steveatkin
Copy link
Author

Received a reply from Ian Jacobs that the ids are not intended for humans to read and will only be used in automated processing. Additionally they have not encountered any need to support identifiers outside the a-z and 0-9 range of characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
s:payment-method-id https://w3c.github.io/payment-method-id/
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@aphillips @stevenatkin @r12a @steveatkin