-
Notifications
You must be signed in to change notification settings - Fork 63
prapi deployment faq
ianbjacobs edited this page Sep 25, 2018
·
15 revisions
Status: This is a draft document. It may be incorrect and does not represent consensus. Questions? Contact Ian Jacobs <ij@w3.org>.
The purpose of this FAQ is to help merchants and service providers understand the status of Payment Request API deployment as of the end of 2018, and to provide practical guidance on the use of the API for some payment methods.
See caniuse.com information about Payment Request API.
- The primary benefit is a streamlined and faster user experience. Users quickly reuse cards stored in the browser. Major browsers support it already (or will support it) except for Safari.
- Because basic card data is not tokenized or encrypted when it leaves the browsers, merchants and PSPs need to take into account PCI-DSS as they would if they were accepting the same data through a Web form.
Mailing list archives
Issues
- Secure Payment Confirmation
- Payment Request API
- Payment Method Identifiers
- Payment Handler API
- Payment Method Manifest
- General
- Tokenized Card
- 3DS
- SRC
Tests
Adoption
Previous Topics