Spec_Notes

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:

• Payment App Notes
• Payment Method Identifier Notes

Payment Request

Requirements

• Input data
  • Supported payment method identifiers and payment method specific data
  • Amounts (variable per payment method)
• Security
  • Top-level or with "parent" consent
• Payment Mediator (browser)
  • 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)

Potential Requirements

• Unsupported payment methods
  • This is only useful if we support grouping/subclassing

Good practice

• Secure data through encryption and signatures (issue 141)

Payment Apps

Requirements

• Input data (Issue 157)
• Formatting response for mediator
• Capabilities
  • Expression of supported and enabled payment methods
  • Information to enable invocation of payment app when selected

Potential Requirements

• Mandatory data (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)

Good practice

Payment Method Identifiers

Requirements

• Syntax
  • The group has decided to use absolute URLs
• Matching Algorithm
  • Rationale: This algorithm must be understood by both browsers/mediator developers and payment app developers (who announce what they support).

Potential Requirements

• Grouping/Subclassing semantics
• Short aliases

Good Practices

• Dereferencing

Payment Methods

Requirements

• Input data
• Output data

Potential Requirements

Good Practices

• Mint identifiers in those specs?