public-payments-wg@w3.org from January 2016 by subject

3DS 2.0

[Minutes] 7 January 2016 call

[paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46)

[paymentrequest] CurrencyAmount description has exponent sign wrong (#39)

[paymentrequest] Minor spec changes based on implementation experience and feedback (#44)

[paymentrequest] Need a "really closed" event (#45)

[paymentrequest] Refactor PaymentDetails. (383c224)

[paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)

[paymentrequest] Support for "enrollment" use of API (#43)

[paymentrequest] Use navigator.payments rather than creating a new object instance (#42)

[web-payments-browser-api] Step 6 of the payment flow is incomplete/unclear (#5)

[webpayments] ACTION: Summarize arguments for/against shipping address capture (#72)

[webpayments] Added Cross Border, minor revisions to RealTime payment (#47)

[webpayments] Added Skin file, participant name changes to ISO20022 (#69)

[webpayments] Adding ISO 20022 definitions highlights for W3C Web Payments WG (#56)

[webpayments] Capture proposed work changes in wiki (#50)

[webpayments] Gh pages (#46)

[webpayments] How can the API support enrollment (future payment) use cases? (#65)

[webpayments] Moved skin from realtime payments into include file (#70)

[webpayments] Patch 1 (#54)

[webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67)

[webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62)

[webpayments] PROPOSAL: Hold WG meetings every week until further notice. (#58)

[webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73)

[webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabilized. (#73)

[webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64)

[webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64)

[webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64)

[webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63)

[webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57)

[webpayments] Refactor flows to use common terminology and entry/exit points (#49)

[webpayments] Security and Privacy Self-Review (#61)

[webpayments] SEPA SDD one-off e-mandate Version 01 28 2016 (#74)

[webpayments] Separated PayPal flow into standard and PSP intermediated following discussions with Dave (#53)

[webpayments] Should a Payment Request API have shipping address APIs? (#39)

[webpayments] Should a payment request be just data, or a programmable object? (#36)

[webpayments] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#66)

[webpayments] Should list of accepted payment methods be strings or objects? (#37)

[webpayments] Should the payment request contain line item details? (#38)

[webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60)

[webpayments] Should we be publishing a specification for an HTTP API? (#17)

[webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76)

[webpayments] Some amendmends (#75)

[webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59)

[webpayments] Update Apple Pay flow and add Bank Mobile Wallet (#45)

[webpayments] Updated 3DS flow with extra detail (#68)

[webpayments] Updated Authentication to read Authorisation (#51)

[webpayments] Updated PayPal to correct redirect and add notifications (#48)

[webpayments] Updated PayPal with annotation based on Dave's feedback (#52)

[webpayments] Updated skins for taskforce reviewed flows (#71)

[webpayments] What is the appropriate conversational pattern for the API? (#55)

Additional agenda item for 21 January call

Agenda - 21 January - 17:00 UTC

Agenda 28 January 17:00 UTC

Agenda: 7 Jan 2016 Web Payments WG call

Concerns around Web Payments HTTP API de-prioritization

Dashboard

European Banking Authority (EBA) Discussion Paper on strong customer and secure communication under PSD2

FYI: European Banking Authority (EBA) Discussion Paper on strong customer and secure communication under PSD2

FYI: W3C Member review of Web Authentication Working Group Charter until 25 January

FYI: Web API Design Cookbook

Labels and Milestones on GitHub

Meta-issues for the group

Polyfills/Wireframes for the browser API proposals

Process question

Progress rapidification (was Re: Labels and Milestones on GitHub)

SCAI - update with Credit Transfer and Direct debit flows

Updated Agenda for 21 January call

Web Payments Community Group Browser API Polyfill Released

Weekly Web Payments Working Group Meetings - Update your Calendars

wpwg-ACTION-11: Ping mountie about samsung and escrow flows

wpwg-ACTION-12: Contact the ig chairs about taking up the terms

Last message date: Sunday, 31 January 2016 18:16:34 UTC