1 of 8

Web Payments

Core Messages and HTTP API

2016.7 Web Payments WG Face-to-Face

Manu Sporny - Digital Bazaar

2 of 8

Goals of Session

  • Brief review of Web Payments Core Messages
  • Brief review of Web Payments HTTP API
  • Demo of both specifications
  • Request to publish as FPWD specifications

3 of 8

Web Payments Core Messages

Payment Response

type

string

description

string

paymentTerms

PaymentTerms

paymentOptions

PaymentOptions

Payment Request

type

string

description

string

paymentTerms

PaymentTerms

paymentDetails

PaymentDetails

paymentOptions

PaymentOptions

4 of 8

Other Things in Web Payments Core Messages

​

  • Pointers on how to express Core Messages in:
    • JSON, WebIDL, and JSON-LD

​

  • Security (and Privacy) Considerations

5 of 8

Payee

1. Access Resource

2. 402 Payment Required

Payment App

Mediator

operated by Payer

7. Payment Response (tokenized)

8. Payment Response (tokenized)

6. Payment Request

Payment Network

9. Payment Instruction

10. Payment success

11. Purchase successful

5. Select Payment App and transaction details

3. GET Payment Request

4. Payment Request

optional first step

12. Access resource

13. Access granted

Web Payments HTTP API

6 of 8

Other Things in Web Payments HTTP API

​

  • HTTP API Payment App Registration
  • Extensibility
  • Security (and Privacy) Considerations

7 of 8

Web Payments Core Messages and HTTP API

Technical Demo

8 of 8

Request to Publish First Public Working Drafts

  • Questions?
  • Concerns?
  • The Ask: Publish the Web Payments Core Messages and HTTP API specifications as First Public Working Drafts