-
Notifications
You must be signed in to change notification settings - Fork 63
Agenda 20170824
ianbjacobs edited this page Aug 24, 2017
·
11 revisions
- Regrets: NTR, AHB
- Introduction
- Testing update?
- Request to move payment apps issues to this venue after PR API goes to CR
- Issue 173 on default instruments (see below)
- Reminder: Rechartering discussions to start in September. Please begin to think about what you would like the WG to do that is new (or whether you think the WG should merely finish current deliverables).
- Note that the WPWG (not the IG) determines its next charter.
- A payment handler may keep track of multiple instruments for the user.
- When presented to the user, there is an opportunity to speed up the user experience by showing a "default" instrument. (How the default instrument is determined is a valuable conversation but not the focus of this discussion.) When the user selects that payment handler, it launches knowing the user selected that instrument, and the user experience for that instrument could be streamlined.
- During this conversation, others suggested that the user still needs a way to get at the remaining payment instruments controlled by the payment handler (e.g., through a "more" link). I've written down some scenarios.
- The task force would like to hear from the broader WG to see whether there is interest in this sort of feature.
Mailing list archives
Issues
- Secure Payment Confirmation
- Payment Request API
- Payment Method Identifiers
- Payment Handler API
- Payment Method Manifest
- General
- Tokenized Card
- 3DS
- SRC
Tests
Adoption
Previous Topics