-
Notifications
You must be signed in to change notification settings - Fork 63
Spec_Notes
ianbjacobs edited this page May 18, 2016
·
45 revisions
Status: These are notes from Ian Jacobs on Web Payments WG spec organization. These are intended for discussion and do not represent group consensus. See also:
- Input data
- Supported payment method identifiers and payment method specific data
- Amounts (variable per payment method)
- Security
- Top-level or with "parent" consent
- Browser as Payment Mediator
- Payment app registration, updates, and unregistration
- Payment app display for selection
- Data caching (shipping address, etc.)
- User selection of payment app
- Interaction with payment app (invocation, sending input data
- Interaction with Web app (sending payment app reponse to Web app)
- Extensibility
- Feature detection
- Unsupported payment methods as input data
- This is only useful if we support grouping/subclassing
- Secure data through encryption and signatures (issue 141)
- Input data (Issue 157)
- Formatting response for mediator
- Capabilities
- Make available information about supported, enabled payment methods
- Make available information about how to enable invocation of payment app when selected
- Data required by the merchant (which may be a subset of all data specified by the payment method). (Issue 97)
- Explicit statement of unsupported payment methods
- This is only useful if we support grouping/subclassing
- Standard mechanism for payment apps to communicate with Web sites (issue 109)
- Payment apps provide app version information
- Identifier Syntax
- The group has decided to use absolute URLs
- Identifier Matching Algorithm
- Rationale: This algorithm must be understood by both browsers/mediator developers and payment app developers (who announce what they support).
- Grouping/Subclassing semantics
- If we support those, consider explicit "Unsupported" semantics as well, including in matching algorithm.
- Short aliases
- Dereferencing
- Input data
- Output data
- Mint identifiers in those specs?
- Flow diagram?
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