First draft of Payment Request FAQ - feedback encouraged

Hi all,

Based on questions formulated by Ken and Andrew, I have taken a first pass at a FAQ:
 https://github.com/w3c/payment-request-info/wiki/FAQ

I have not reread my own writing so it is probably choppy. However, I wanted to start to get
feedback.

Below is the current Table of Contents and questions. 

Comments welcome, as well as new ideas for questions.

I’d like to share this with the Web Payments Working Group around 16 March, and then discuss
any issues people raise at the face-to-face meeting.

Ian

[1] https://lists.w3.org/Archives/Public/public-payments-strategy/2017Feb/0007.html

==================

1. General Questions

- What is the purpose of the Payment Request API?
- In one sentence, how does it work?
- In a few sentences, how does it work?
- What are the primary benefits of the API?
- What are the primary risks of the API?

2. Payment Method Questions

- What is the difference between a Payment Method and a Payment App?
- Can any payment method be used with the API?
- How are payment methods identified?
- What payment methods is W3C defining?
- What payment methods are available today to be used with the API?
- Can merchants express preferences for payment methods?

3. General Payment App Questions

- Is a payment app just a digital wallet?
- How do users get payment apps?
- Are payment apps native mobile apps or Web apps? 
- How do browser know which payment apps the user has?
- How does the browser determine whether a payment app "matches" for a particular transaction?
- What payment apps should a merchant support?
- What payment apps work with this API today?

4. Payment App Display and Ordering Questions

- How are matching payment apps displayed to the user?
- How do merchants know which payment apps the user has?
- Can merchants recommend payment apps to the user?
- Can merchants affect the order of matching payment apps displayed to the user?
- How do browsers determine the display order of matching payment apps?
- Does Payment Request API give merchants with a way to influence which payment app the user selects?
- Does Payment Request API give payment app providers a way to influence which payment app the user selects?
- Does Payment Request API give browsers a way to influence which payment app the user selects?

5. Checkout Page Questions

- How will checkout pages change as a result of this API?
- What does the button look like that merchants will use with this API?
- What is the impact on other buttons one typically sees on a checkout page?
- How does Payment Request API affect the flow of payment methods I already support?
- Can a checkout page use the Payment Request API even though it is not yet supported by all browsers?

6. Backend Questions

- What does a merchant need to do to accept a particular payment method?
- How does a merchant handle payment response data it receives?

7. Security Questions

- How does the browser store information securely?
- How do payment apps store information securely?
- Does the API include user authentication?

8. Deployment Status Questions

- Which browsers implement this today?
- How do I know whether a given browser has implemented Payment Request API?
- How interoperable are implementations today?
- When do you expect broad interoperability?
- Which merchants use this today?
- When does W3C expect the standard to be completed?
- Is Payment Request API just for the Web?

9. Relationship to Other Standards

- What is the relationship to ISO 20022 messages?

--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447

Received on Friday, 3 March 2017 20:22:47 UTC