This specification defines payment method identifiers and how they are validated, and, where applicable, minted and formally registered with the W3C. Other specifications (e.g., Payment Request) make use of these identifiers to facilitate monetary transactions on the web platform.
Please file any issues with this specification in the payment method identifiers repository on GitHub.
A payment method identifier is either a:
A URL-based payment method identifier is a URL that is valid as per the steps to validate a URL-based payment method identifier.
Developers wanting to use a URL-based payment method identifier for a third party payment handler are encouraged to read the Payment Method Best Practice document.
The steps to validate a URL-based payment method identifier are given by the following algorithm. The algorithm takes a url URL as input and returns true if the URL is valid:
User agents MUST perform comparisons of URL-based payment method identifiers using equals. [[!URL]]
A standardized payment method identifier is a string that represents a standardized payment method.
User agents MAY support zero or more standardized payment method identifiers listed in section .
When minting a new standardized payment method identifier for
the purpose of standardization, be sure that it conforms to the
following regular expression: [a-z0-9-]+.
User agents MUST NOT enforce validity or well-formedness of standardized payment method identifiers.
For standardized payment method identifiers, user agents MUST compare strings in a case-sensitive manner (code point for code point).
A standardized payment method is a payment method that has undergone standardization at the W3C, and is listed in this registry.
The Working Group has minted the following standardized payment method identifiers:
basic-card"
There are no known privacy or security concerns to be taken into considerations at this time.