├── .github
    └── workflows
    │   ├── auto-publish.yml
    │   └── tidy.yml
├── .pr-preview.json
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE.md
├── README.md
├── echidna-manifest.txt
├── errata.html
├── index.html
├── reports
    └── implementation.html
├── tidyconfig.txt
└── w3c.json


/.github/workflows/auto-publish.yml:
--------------------------------------------------------------------------------
 1 | # See https://w3c.github.io/spec-prod/
 2 | name: Node CI
 3 | 
 4 | on:
 5 |   push:
 6 |     branches:
 7 |       - gh-pages
 8 |   pull_request: {}
 9 | 
10 | jobs:
11 |   validate-and-publish:
12 |     name: Validate and Publish
13 |     runs-on: ubuntu-latest # only linux supported at present
14 |     steps:
15 |       - uses: actions/checkout@v2
16 |       - uses: w3c/spec-prod@v2
17 |         with:
18 |           TOOLCHAIN: respec
19 |           W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN }}
20 |           W3C_WG_DECISION_URL: "https://www.w3.org/2016/04/14-wpwg-minutes.html#item02"
21 |           W3C_NOTIFICATIONS_CC: "${{ secrets.CC }}"
22 |           W3C_BUILD_OVERRIDE: |
23 |             specStatus: CRD
24 | 


--------------------------------------------------------------------------------
/.github/workflows/tidy.yml:
--------------------------------------------------------------------------------
 1 | name: Tidy document
 2 | on:
 3 |   workflow_dispatch: {}
 4 |   push:
 5 |     branches:
 6 |       - gh-pages
 7 | 
 8 | jobs:
 9 |   tidy:
10 |     name: Tidy up
11 |     runs-on: macos-latest
12 |     steps:
13 |       - uses: actions/checkout@v2
14 |       - run: brew install tidy-html5
15 |       - run: tidy -config tidyconfig.txt -o index.html index.html
16 |       - uses: peter-evans/create-pull-request@v3
17 |         with:
18 |           title: "chore(tidy): tidy up document"
19 |           commit-message: "Tidied up document using tidy-html5"
20 |           branch: html-tidy
21 | 


--------------------------------------------------------------------------------
/.pr-preview.json:
--------------------------------------------------------------------------------
1 | {
2 |     "src_file": "index.html",
3 |     "type": "respec"
4 | }
5 | 


--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 | 
3 | All documentation, code and communication under this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/).
4 | 


--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
 1 | # Web Payments Working Group
 2 | 
 3 | Contributions to this repository are intended to become part of Recommendation-track documents governed by the
 4 | [W3C Patent Policy](http://www.w3.org/Consortium/Patent-Policy-20040205/) and
 5 | [Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software). To make substantive contributions to specifications, you must either participate
 6 | in the relevant W3C Working Group or make a non-member patent licensing commitment.
 7 | 
 8 | If you are not the sole contributor to a contribution (pull request), please identify all 
 9 | contributors in the pull request comment.
10 | 
11 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows:
12 | 
13 | ```
14 | +@github_username
15 | ```
16 | 
17 | If you added a contributor by mistake, you can remove them in a comment with:
18 | 
19 | ```
20 | -@github_username
21 | ```
22 | 
23 | If you are making a pull request on behalf of someone else but you had no part in designing the 
24 | feature, you can remove yourself with the above syntax.
25 | 


--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
1 | All documents in this Repository are licensed by contributors under the [W3C Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software).
2 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | 
2 | # Web Payments - Payment Method Identifers
3 | 
4 | This repository contains a draft specification from the [W3C Web Payments Working Group](https://www.w3.org/Payments/WG/).
5 | 
6 | This is the Payment Method Identifers sepcification
7 | The editor's draft is available at: http://w3c.github.io/payment-method-id/
8 | 


--------------------------------------------------------------------------------
/echidna-manifest.txt:
--------------------------------------------------------------------------------
1 | index.html?specStatus=CR&shortName=payment-method-id respec
2 | 


--------------------------------------------------------------------------------
/errata.html:
--------------------------------------------------------------------------------
 1 | <!DOCTYPE html>
 2 | <html>
 3 |   <head>
 4 |     <meta charset="utf-8" />
 5 |     <title>Payment Method Identifiers Errata</title>
 6 |     <script
 7 |       src="https://www.w3.org/Tools/respec/respec-w3c"
 8 |       class="remove"
 9 |     ></script>
10 |     <script>
11 |       var respecConfig = {
12 |         specStatus: "base",
13 |         latestVersion: null,
14 |         editors: [
15 |           {
16 |             name: "Marcos Cáceres",
17 |             company: "Apple Inc.",
18 |             companyURL: "https://apple.com",
19 |             w3cid: 39125,
20 |           },
21 |         ],
22 |         format: "markdown",
23 |         logos: [
24 |             {
25 |                 alt:"W3C", 
26 |                 src:"https://www.w3.org/StyleSheets/TR/2021/logos/W3C", 
27 |                 width: "72", 
28 |                 height:"48"
29 |             }
30 |         ]
31 |       };
32 |     </script>
33 |   </head>
34 |   <body>
35 |     <section id="abstract">
36 |     ## Abstract
37 |     This document catalogues errata for the [<cite>Payment Method Identifiers</cite>](https://w3.org/TR/payment-method-id/) W3C Recommendation. 
38 |     </section>
39 | 
40 |     ## Process for submitting errata
41 | 
42 |     Please [file an issue](https://github.com/w3c/payment-method-id/issues) on Github.  
43 | 
44 |     ## Unaddressed errata
45 |     None.
46 | 
47 |     ## Errata approved by the Working Group
48 |     None.
49 |   </body>
50 | </html>
51 | 


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
  1 | <!DOCTYPE html>
  2 | <html>
  3 |   <head>
  4 |     <title>
  5 |       Payment Method Identifiers
  6 |     </title>
  7 |     <meta charset='utf-8'>
  8 |     <script src='https://www.w3.org/Tools/respec/respec-w3c' async class=
  9 |     'remove'></script>
 10 |     <script class='remove'>
 11 |     var respecConfig = {
 12 |       shortName: 'payment-method-id',
 13 |       github: "w3c/payment-method-id",
 14 |       specStatus: "ED",
 15 |       group: "payments",
 16 |       formerEditors: [
 17 |         {
 18 |           name: "Adrian Bateman",
 19 |           company: "Microsoft Corporation",
 20 |           w3cid: 42763,
 21 |         },
 22 |         {
 23 |           name: "Domenic Denicola",
 24 |           company: "Google",
 25 |           w3cid: 52873,
 26 |         },
 27 |         {
 28 |           name: "Zach Koch",
 29 |           company: "Google",
 30 |           w3cid: 76588,
 31 |         },
 32 |         {
 33 |           name: "Roy McElmurry",
 34 |           company: "Facebook",
 35 |           w3cid: 88345,
 36 |         },
 37 |       ],
 38 |       editors: [
 39 |         {
 40 |           name: "Marcos Cáceres",
 41 |           company: "Apple Inc.",
 42 |           companyURL: "https://www.apple.com/",
 43 |           w3cid: 39125,
 44 |         },
 45 |       ],
 46 |       crEnd: "2019-10-01",
 47 |       prEnd: "2021-10-28",
 48 |       previousMaturity: "PER",
 49 |       previousPublishDate: "2021-09-30",
 50 |       errata: "https://www.w3.org/Payments/WG/errata.html",
 51 |       implementationReportURI: "https://w3c.github.io/test-results/payment-method-id/all.html",
 52 |       // We can only indirectly test conformance, so we rely on certain tests
 53 |       // in the Payment Request API.
 54 |       testSuiteURI: "https://wpt.live/payment-method-id/",
 55 |       xref: ["URL", "HTML", "FETCH", "INFRA"]
 56 |     };
 57 |     </script>
 58 |   </head>
 59 |   <body>
 60 |     <section id='abstract'>
 61 |       <p>
 62 |         This specification defines payment method identifiers and how they are
 63 |         validated, and, where applicable, minted and formally registered with
 64 |         the <a href="https://www.w3.org/">W3C</a>. Other specifications (e.g.,
 65 |         the [[[payment-request]]]) make use of these identifiers to facilitate
 66 |         monetary transactions on the web platform.
 67 |       </p>
 68 |     </section>
 69 |     <section id='sotd' class="updateable-rec">
 70 |       <p>
 71 |         The working group demonstrates implementation experience by producing
 72 |         an <a href=
 73 |         "https://w3c.github.io/test-results/payment-method-id/all.html">implementation
 74 |         report</a>. The report shows two or more independent implementations
 75 |         passing each mandatory test in the <a href=
 76 |         "https://wpt.live/payment-method-id/">test suite</a> (i.e., each test
 77 |         corresponds to a MUST requirement of the specification).
 78 |       </p>
 79 |       <p>
 80 |         There has been no change in dependencies on other workings groups
 81 |         during the development of this specification.
 82 |       </p>
 83 |     </section>
 84 |     <section>
 85 |       <h2>
 86 |         Payment method identifiers (PMIs)
 87 |       </h2>
 88 |       <p>
 89 |         A <dfn data-abbr="PMI" data-export="">payment method identifier</dfn>
 90 |         is either a:
 91 |       </p>
 92 |       <ul>
 93 |         <li>[=URL-based payment method identifier=],
 94 |         </li>
 95 |         <li>or a [=standardized payment method identifier=].
 96 |         </li>
 97 |       </ul>
 98 |       <section>
 99 |         <h3>
100 |           Validity
101 |         </h3>
102 |         <p>
103 |           Specifications that rely on [=payment method identifiers=] MUST
104 |           specify their own rules for handling invalid payment method
105 |           identifiers.
106 |         </p>
107 |         <p>
108 |           The steps to <dfn data-export="">validate a payment method
109 |           identifier</dfn> with a string |pmi:string| are given by the
110 |           following algorithm. It returns true if the |pmi| is valid.
111 |         </p>
112 |         <ol class="algorithm">
113 |           <li>Let |url:URL| be the result of running the [=basic URL parser=]
114 |           with |pmi|.
115 |           </li>
116 |           <li>If |url| is failure, [=validate a standardized payment method
117 |           identifier=] with |pmi| and return the result.
118 |           </li>
119 |           <li>Otherwise, [=validate a URL-based payment method identifier=]
120 |           passing |url| and return the result.
121 |           </li>
122 |         </ol>
123 |       </section>
124 |     </section>
125 |     <section>
126 |       <h2>
127 |         URL-based payment method identifiers
128 |       </h2>
129 |       <p>
130 |         A <dfn data-export="">URL-based payment method identifier</dfn> is a
131 |         [=URL=] that is valid as per the steps to [=validate a URL-based
132 |         payment method identifier=].
133 |       </p>
134 |       <div class="note">
135 |         <p>
136 |           Developers wanting to use a URL-based payment method identifier for a
137 |           third party payment handler are encouraged to read the <a href=
138 |           "https://github.com/w3c/payment-request-info/wiki/PaymentMethodPractice">
139 |           Payment Method Best Practice</a> document.
140 |         </p>
141 |       </div>
142 |       <section>
143 |         <h2>
144 |           Validation
145 |         </h2>
146 |         <p>
147 |           The steps to <dfn data-export="">validate a URL-based payment method
148 |           identifier</dfn> are given by the following algorithm. The algorithm
149 |           takes a [=URL=] |url:URL| as input and returns true if the URL is
150 |           valid:
151 |         </p>
152 |         <ol class="algorithm">
153 |           <li>If |url|'s [=url/scheme=] is not "https", return false.
154 |           </li>
155 |           <li>If |url|'s [=url/username=] or [=url/password=] is not the empty
156 |           string, return false.
157 |           </li>
158 |           <li>Otherwise, return true.
159 |           </li>
160 |         </ol>
161 |         <pre class="example js" title="valid and invalid URL-based PMIs">
162 |           const valid = [
163 |             {
164 |               supportedMethods: "https://example.com/pay",
165 |             },
166 |             {
167 |               supportedMethods: "https://example.com/pay?version=1",
168 |             },
169 |             {
170 |               supportedMethods: "https://example.com/pay/version/1",
171 |             },
172 |           ];
173 | 
174 |           const invalid = [
175 |             {
176 |               // ❌ Uses http://, a username, and a password.
177 |               supportedMethods: "http://username:password@example.com/pay",
178 |             },
179 |             {
180 |               // ❌ Uses unknown URI scheme.
181 |               supportedMethods: "unknown://example.com/pay",
182 |             },
183 |           ];
184 |         </pre>
185 |       </section>
186 |       <section>
187 |         <h2>
188 |           Comparison
189 |         </h2>
190 |         <p data-tests="payment-request-ctor-pmi-handling.https.sub.html">
191 |           User agents MUST perform comparisons of [=URL-based payment method
192 |           identifiers=] using [[URL]]'s [=URL/equal=].
193 |         </p>
194 |       </section>
195 |       <section>
196 |         <h2>
197 |           Fetching (dereferencing)
198 |         </h2>
199 |         <p>
200 |           It is OPTIONAL for user agents to [=fetch=] a [=URL-based payment
201 |           method identifier=].
202 |         </p>
203 |       </section>
204 |     </section>
205 |     <section>
206 |       <h2>
207 |         Standardized payment method identifiers
208 |       </h2>
209 |       <p>
210 |         A <dfn data-export="">standardized payment method identifier</dfn> is a
211 |         string that represents a [=standardized payment method=].
212 |       </p>
213 |       <p>
214 |         The <dfn>syntax of a standardized payment method identifier</dfn> is
215 |         given by the following [[ABNF]]:
216 |       </p>
217 |       <pre class="ABFN">
218 |         stdpmi = part *( "-" part )
219 |         part = 1loweralpha *( DIGIT / loweralpha )
220 |         loweralpha =  %x61-7A
221 |       </pre>
222 |       <p>
223 |         User agents MAY support zero or more [=standardized payment method
224 |         identifiers=] listed in section [[[#registry]]].
225 |       </p>
226 |       <section>
227 |         <h2>
228 |           Validity
229 |         </h2>
230 |         <p>
231 |           The steps to <dfn>validate a standardized payment method
232 |           identifier</dfn> are given by the following algorithm. The algorithm
233 |           takes a |string:string| as input and returns true if the identifier
234 |           is valid:
235 |         </p>
236 |         <ol class="algorithm">
237 |           <li>Return true if |string| conforms to the [=syntax of a
238 |           standardized payment method identifier=]. Otherwise, return false.
239 |           </li>
240 |         </ol>
241 |         <aside class="note">
242 |           <p>
243 |             When used in an API, the following method identifiers are all
244 |             ignored by the user agent. Some user agents might inform developers
245 |             that identifiers are invalid to help them fix issues.
246 |           </p>
247 |           <p>
248 |             The example below refers to the "basic-card" standardized payment
249 |             method identifier. Although the Web Payments Working Group has
250 |             discontinued that work, the identifier serves here as an example.
251 |           </p>
252 |           <pre class="example" title="Valid and invalid identifiers">
253 |             const valid = [
254 |               {
255 |                 supportedMethods: "basic-card",
256 |               },
257 |             ];
258 | 
259 |             const invalid = [
260 |               {
261 |                 // ❌ Contains Unicode character outside the valid ranges.
262 |                 supportedMethods: "basic-💳",
263 |               },
264 |               {
265 |                 // ❌ Contains uppercase characters.
266 |                 supportedMethods: "Basic-Card",
267 |               },
268 |               {
269 |                 // ❌ Contains Unicode characters outside the valid ranges.
270 |                 supportedMethods: "¡basic-*-card!",
271 |               },
272 |             ];
273 |           </pre>
274 |         </aside>
275 |       </section>
276 |       <section>
277 |         <h2>
278 |           Comparison
279 |         </h2>
280 |         <p data-tests="payment-request-ctor-pmi-handling.https.sub.html">
281 |           For [=standardized payment method identifiers=], user agents MUST
282 |           perform string comparisons using [=string/is=].
283 |         </p>
284 |       </section>
285 |     </section>
286 |     <section class="informative" id="registry">
287 |       <h3>
288 |         Registry of standardized payment methods
289 |       </h3>
290 |       <aside class="note">
291 |         <p>
292 |           There is no need to register a [=URL-based payment method
293 |           identifier=].
294 |         </p>
295 |         <p>
296 |           Organizations seeking to mint a new identifier for a payment method
297 |           are encouraged to <a href="https://www.w3.org/Consortium/join">join
298 |           the W3C</a> and follow the <a href=
299 |           "https://www.w3.org/Consortium/Process/">W3C process</a>.
300 |         </p>
301 |       </aside>
302 |       <p>
303 |         A <dfn>standardized payment method</dfn> is a payment method that has
304 |         undergone standardization at the W3C, and is listed in this registry.
305 |       </p>
306 |       <p>
307 |         At this time there are no [=standardized payment method identifiers=].
308 |       </p>
309 |     </section>
310 |     <section class="informative">
311 |       <h2>
312 |         URL-based PMI and third-party payment handlers
313 |       </h2>
314 |       <p>
315 |         Developers wanting to use a URL-based payment method identifier for a
316 |         third party payment handler are encouraged to read the
317 |         [[[payment-method-manifest]]] specification and the <a href=
318 |         "https://github.com/w3c/payment-request-info/wiki/PaymentMethodPractice">
319 |         Payment Method Best Practice</a> wiki page. Together, these documents
320 |         describe how to manage the ecosystem of authorized payment handlers for
321 |         a payment method, including just-in-time payment handler installation
322 |         by the browser.
323 |       </p>
324 |     </section>
325 |     <section>
326 |       <h2>
327 |         Security considerations
328 |       </h2>
329 |       <p>
330 |         This specification does not introduce any new security considerations.
331 |       </p>
332 |     </section>
333 |     <section>
334 |       <h2>
335 |         Privacy considerations
336 |       </h2>
337 |       <p>
338 |         There are no known privacy or security concerns to be taken into
339 |         considerations at this time.
340 |       </p>
341 |     </section>
342 |     <section id="conformance"></section>
343 |     <section id="index"></section>
344 |   </body>
345 | </html>
346 | 


--------------------------------------------------------------------------------
/reports/implementation.html:
--------------------------------------------------------------------------------
1 | <h1>Coming Soon</h1>


--------------------------------------------------------------------------------
/tidyconfig.txt:
--------------------------------------------------------------------------------
1 | char-encoding: utf8
2 | indent: yes
3 | wrap: 80
4 | tidy-mark: no
5 | 


--------------------------------------------------------------------------------
/w3c.json:
--------------------------------------------------------------------------------
1 | {
2 |   "group": ["83744"],
3 |   "contacts": ["sideshowbarker"],
4 |   "repo-type": "rec-track"
5 | }
6 | 


--------------------------------------------------------------------------------