The Payment Handler API allows payment providers to make their custom payment experience available for merchants, along with the Payment Request API.
The information on this page only applies to websites that use both CSP (Content-Security-Policy) and the Payment Request API. If you use neither or only one of the two, then you can skip these instructions.
To check if your payment provider is using the Payment Handler API, contact them and follow their instructions.
If you are using the Payment Handler API and CSP (Content-Security-Policy) for
better protection, you need to make sure the domains of HTTP requests sent from
the browser are added to the connect-src directive of the CSP header.
For example, if your JavaScript code invokes new
PaymentRequest([{supportedOrigins: ‘https://example.com/pay’}], details), then
your CSP connect-src must include https://example.com or
https://example.com/pay:
Content-Security-Policy: connect-src https://example.com/pay
If https://example.com/pay is a cross-origin redirect, then the destination
origin should be included in the CSP too. For example, if
https://example.com/pay redirects to https://pay.example.com, then both
origins must be included in the CSP:
Content-Security-Policy: connect-src https://example.com/pay https://pay.example.com
Try it out locally
To enable the feature locally before it is shipped:
- Go to
chrome://flags/#web-payment-api-cspon Chrome. - Change "CSP policy for Web Payment API" from "Default" to "Enabled".
- Restart Chrome.
Check the request URLs
To check the URLs of the requests sent from the Payment Handler API:
- Enable
chrome://flags/#web-payment-api-csp. - Go to your checkout page and open Chrome’s Developer Tools.
- Look for error messages like the following:
text RangeError: Failed to construct 'PaymentRequest': https://example.com/pay payment method identifier violates Content Security Policy. - Add the specified method identifier to your CSP.
Photo by Eduardo Soares on Unsplash