Issues

• Refund a transaction

  design
  web-payments/web-commerce-api#14 · Filter by author kumar303 opened on Jul 16, 2013

• Let buyers pay with arbitrary payment methods regardless of merchant support

  designquestion
  web-payments/web-commerce-api#13 · Filter by author kumar303 opened on Jul 15, 2013
  1

• Registering preferred payment providers

  designenhancement
  web-payments/web-commerce-api#12 · Filter by author msporny opened on Jun 24, 2013 · Last Call
  2

  

• Expand the JWT format?

  question
  web-payments/web-commerce-api#11 · Filter by author kumar303 opened on May 16, 2013

• Preventing spoofed buyflows

  design
  web-payments/web-commerce-api#10 · Filter by author msporny opened on May 15, 2013 · Last Call
  1

• Security considerations section

  bugdesignenhancement
  web-payments/web-commerce-api#9 · Filter by author msporny opened on May 9, 2013 · Last Call
  1

• Are charge-backs/refunds out of scope?

  designquestion
  web-payments/web-commerce-api#8 · Filter by author msporny opened on May 7, 2013

• .pay() vs. .payment() vs. .initiatePayment()

  design
  web-payments/web-commerce-api#7 · Filter by author msporny opened on May 7, 2013

• User identity

  designquestion
  web-payments/web-commerce-api#6 · Filter by author kumar303 opened on May 6, 2013
  1

• Digital receipt mechanism?

  question
  web-payments/web-commerce-api#5 · Filter by author msporny opened on May 6, 2013 · Last Call
  1

• Application-specific data in a JWT?

  question
  web-payments/web-commerce-api#4 · Filter by author msporny opened on May 6, 2013 · Last Call
  3

• Using multiple payment providers

  designquestion
  web-payments/web-commerce-api#3 · Filter by author msporny opened on May 6, 2013 · Last Call
  2

• Pure chrome-based buyflow

  design
  web-payments/web-commerce-api#2 · Filter by author msporny opened on May 6, 2013 · Last Call
  2

• DOMRequest vs. DOMFuture

  design
  web-payments/web-commerce-api#1 · Filter by author msporny opened on May 6, 2013 · Last Call
  3