[w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567)
[w3c/payment-request] Don't understand how to support outsourced payment providers using CNP + basic card (#566)
- Re: [w3c/payment-request] Don't understand how to support outsourced payment providers using CNP + basic card (#566)
- Re: [w3c/payment-request] Don't understand how to support outsourced payment providers using CNP + basic card (#566)
Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532)
Re: [w3c/payment-request] Should user agent validate currency? (#490)
- Re: [w3c/payment-request] Should user agent validate currency? (#490)
- Re: [w3c/payment-request] Should user agent validate currency? (#490)
[w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565)
Re: [w3c/payment-request] Add Guidance Text for User Consent (#229)
Re: [w3c/payment-method-id] Add ignore example (#37)
[w3c/payment-handler] Chore: Removed duplicate issue 173 (#195)
- Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195)
- Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195)
- Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195)
- Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195)
- Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195)
[w3c/payment-method-basic-card] editorial: cleanup, tidy, ReSpec warns, etc. (#37)
- Re: [w3c/payment-method-basic-card] editorial: cleanup, tidy, ReSpec warns, etc. (#37)
- Re: [w3c/payment-method-basic-card] editorial: cleanup, tidy, ReSpec warns, etc. (#37)
[w3c/payment-method-basic-card] Unclear what happens when there are duplicates (#36)
- Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)
- Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)
- Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)
- Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)
- Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)
- Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)
[w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
- Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)
Re: [w3c/payment-request] Drop invalid PMIs in PR ctor (closes #557 #464) (e3893b3)
[w3c/webpayments-methods-tokenization] multiuse flow (#20)
[w3c/webpayments-methods-tokenization] Need for environment parameter (#19)
[w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18)
[w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17)
[w3c/payment-handler] Add missing </section> after #188 PR. (#193)
- Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193)
- Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193)
- Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193)
- Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193)
[w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16)
[w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15)
[w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14)
Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541)
Re: [w3c/payment-request] editorial: set CR end date to 31st oct (#562)
Re: [w3c/payment-request] editorial: fix CR exit date, add exit criteria (#563)
Re: [w3c/payment-request] chore: rename repo to match shortname (#564)
- Re: [w3c/payment-request] chore: rename repo to match shortname (#564)
- Re: [w3c/payment-request] chore: rename repo to match shortname (#564)
[w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192)
[w3c/payment-handler] "PaymentRequestEvent dictionary" makes no sense (#191)
[w3c/payment-handler] respondWith behavior not specified (#190)
[w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
- Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189)
Re: [w3c/payment-request] Recipient and payerName are lacking i18n support (#471)
Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480)
- Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480)
- Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480)
Re: [w3c/payment-request] Populate implementation report (#560)
Re: [w3c/browser-payment-api] validate supportedMethods (#464)
Re: [w3c/browser-payment-api] Reject acceptedPromise if payment method identifer is invalid (#557)
Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480)
[w3c/browser-payment-api] chore: rename repo to match shortname (#564)
- Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564)
- Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564)
- Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564)
- Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564)
[w3c/payment-method-id] Auto-publishing failing on bad token (#43)
- Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43)
- Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43)
- Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43)
- Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43)
- Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43)
[w3c/payment-method-id] editorial: add CR exit criteria (#42)
[w3c/browser-payment-api] editorial: fix CR exit date, add exit criteria (#563)
- Re: [w3c/browser-payment-api] editorial: fix CR exit date, add exit criteria (#563)
- Re: [w3c/browser-payment-api] editorial: fix CR exit date, add exit criteria (#563)
[w3c/payment-method-id] Clarify validation of standardized PMIs (#41)
- Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41)
- Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41)
- Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41)
- Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41)
[w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40)
- Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40)
- Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40)
- Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40)
[w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13)
[w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
- Re: [w3c/payment-handler] Remove wallets, clean up issues (#188)
Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
- Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)
Re: [w3c/payment-handler] Multiple payment apps per origin (#98)
Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
- Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
- Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
- Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
- Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
- Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
- Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)
Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/payment-handler] Add .clear() to map-likes (#129)
Re: [w3c/payment-method-id] CR checklist (#39)
- Re: [w3c/payment-method-id] CR checklist (#39)
- Re: [w3c/payment-method-id] CR checklist (#39)
- Re: [w3c/payment-method-id] CR checklist (#39)
[w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562)
- Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562)
- Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562)
- Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562)
- Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562)
Re: [w3c/payment-method-basic-card] Rename repo to match shortname (#33)
Re: [w3c/payment-method-basic-card] chore: fix links from rename (#35)
[w3c/webpayments-methods-card] chore: fix links from rename (#35)
[w3c/webpayments-methods-card] Processing note should be normative text (#34)
[w3c/webpayments-methods-card] Rename repo to match shortname (#33)
Re: [w3c/browser-payment-api] Move examples to top of document (#456)
Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553)
- Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553)
- Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553)
- Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553)
- Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553)
- Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553)
Re: [w3c/payment-method-id] Rename repo payment-method-id (#38)
- Re: [w3c/payment-method-id] Rename repo payment-method-id (#38)
- Re: [w3c/payment-method-id] Rename repo payment-method-id (#38)
- Re: [w3c/payment-method-id] Rename repo payment-method-id (#38)
- Re: [w3c/payment-method-id] Rename repo payment-method-id (#38)
- Re: [w3c/payment-method-id] Rename repo payment-method-id (#38)
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511)
Re: [w3c/browser-payment-api] WIP: move+rework examples (#553)
Re: [w3c/browser-payment-api] RFC2119 keywords in informative sections (#439)
[w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12)
- Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12)
- Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12)
Re: [w3c/payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
[w3c/browser-payment-api] Make privacy section normative (closes #439) (#561)
- Re: [w3c/browser-payment-api] Make privacy section normative (closes #439) (#561)
- Re: [w3c/browser-payment-api] Make privacy section normative (closes #439) (#561)
Re: [w3c/browser-payment-api] editorial: Clarify wording to not imply 'pull' only payments (#474)
Re: [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (#541)
[w3c/webpayments-method-identifiers] CR checklist (#39)
- Re: [w3c/webpayments-method-identifiers] CR checklist (#39)
- Re: [w3c/webpayments-method-identifiers] CR checklist (#39)
[w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38)
- Re: [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38)
- Re: [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38)
- Re: [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38)
Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327)
Re: [w3c/webpayments-methods-tokenization] Payment Method declaration may show duplicate card descriptions (#9)
[w3c/browser-payment-api] Add implementation report (#560)
- Re: [w3c/browser-payment-api] Add implementation report (#560)
- Re: [w3c/browser-payment-api] Populate implementation report (#560)
- Re: [w3c/browser-payment-api] Populate implementation report (#560)
Re: [w3c/browser-payment-api] CR check list (#520)
- Re: [w3c/browser-payment-api] CR check list (#520)
- Re: [w3c/browser-payment-api] CR check list (#520)
[w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11)
- Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11)
- Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11)
- Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11)
- Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11)
Re: [w3c/webpayments-methods-tokenization] Should we keep the IIN/BIN or drop it from the spec? (#10)
- Re: [w3c/webpayments-methods-tokenization] Should we keep the IIN/BIN or drop it from the spec? (#10)
- Re: [w3c/webpayments-methods-tokenization] Should we keep the IIN/BIN or drop it from the spec? (#10)
[w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
- Re: [w3c/browser-payment-api] Editorial changes (#559)
Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549)
- Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549)
- Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549)
Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5)
Re: [w3c/payment-handler] Pictures would help! (#49)
Re: [w3c/payment-handler] Missing question mark, (#163)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506)
Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
[w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
- Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
- Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
- Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
- Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
- Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
- Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187)
Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
- Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170)
Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)
- Re: [w3c/browser-payment-api] UX guidance article (#558)