-
Notifications
You must be signed in to change notification settings - Fork 63
Agenda 20170810
ianbjacobs edited this page Aug 9, 2017
·
9 revisions
- Regrets: NickTR
- The transition requestion is ready, but we need to identify the fate of these issues before sending it.
- Ian would like to talk about architecture of various requirements.
- What does PR API need to say (e.g., default matching behavior in show())? PR API could usefully say that matching starts with a set of PMIs then removes payment apps based on a variety of considerations: manifest, capabilities, security.
- What does PMI need to say (e.g., "guidance about looking for manifests)
- What does Payment Method Manifest need to say (e.g., in case of error, what is secure behavior?)
- What does Payment Handler need to say (if anything)?
- What issues need to be resolved before FPWD? Those that we choose not to address before FPWD should show up as issue markers as we have done previously.
- Need help with Bikeshed for FPWD formatting.
- 24 Aug?
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