Agenda 20161117

• Status of pull request about Detecting Payment Method Availability
  • Link to pull request
  • Seeking support for canMakeActivePayment(), including implementer perspective.
• Status of pull request about push payments
  • Transaction ID next steps
  • Callback URL next steps
• Basic Card
  • For values of supportedNetworks, propose managing those outside the specification (as the list may be more dynamic than the specification) and linking to that list from the specification.
• Payment Method Identifier Specification
  • Updated PMI specification based on recent discussions
  • Questions from AdrianHB for discussion
• Manifest Specification
  • Max is going to work on this starting from Zach's proposal
  • Should Manifest spec be included as part of the PMI spec?
  • Question: Hard code path to manifest or something else (e.g., content negotiation).
  • Any optimization desirable for the case where someone wants to say "I have a URL for my payment method and want to allow any payment app to implement it; but don't want to host a manifest file."
• Payment app implementation discussions (Ian quick summary)
• Communications
  • Who would like to work with Nick and Ian on updated communications around the benefits (to merchants (and merchant service providers)) of the payments APIs?
• Check in on priorities:
  • PR API issues
  • Payment app spec reviews
  • Push payment proposal
  • Test suite
• Next meeting: 1 December