Domain Whitelist

Security is our top priority. Access is SOC 2 Type 1 accredited and maintains stringent, best-practice control over the member data you share with us. The iframe integration is equally important, and we use a strict Content Security Policy to ensure that no one can cross-script our application.To ensure a secure integration that will pass PCI Scans, Access Development requires a list of each domain that will be including our travel.client.v2.js script. Each domain will be added to our allowed iframe-ancestors configuration to ensure that no bad actors can impersonate our clients.Note that the Access Travel Platform will not resolve in your web application until we have added the host domain to our CSP configuration. Your Client Success Representative will help you work with our Security team to setup this configuration.Note: Due to this restriction, be aware that the travel.client.v2.js script will not load on localhost.

Your Content Security Policy

Clients integrating with the Access Travel Platform may need to update their Content Security Policy (CSP) to allow access to our domain. For example, booking.accessdevelopment.com should be added to the script-src , frame-src , and frame-ancestors nodes. Other attributes may require an update as well, depending upon the client’s CSP configuration.Access also uses familiar tools to provide essential services such as website analytics, user experience, A/B testing, maps, and payment gateways. You'll want to ensure that the following domains are not excluded from the Content Security Policy.*.accessdevelopment.com *.adcrws.com *.mapbox.com translation.googleapis.com cdn.heapanalytics.com heapanalytics.com *.auryc.com *.visualwebsiteoptimizer.com app.vwo.com js.stripe.com qqc-api.worldnomads.com *.braintreegateway.com *.braintree-api.com Please contact us with any questions.