.acs-side-bar {background-color: #FFFFFF;} |
What is happening?Starting in December 2015, we will begin disabling the TLS v1.0 and v1.1 encryption protocols. This approach will prevent any TLS v1.0 and v1.1 connection to access Qvalent/Westpac services. No access from any TLS v1.0 and v1.1 connection will allowed after June 30, 2016. |
Why is this happening?At Qvalent we treat the protection of our customers' data very seriously. Sometimes we need to make security improvements and retire older encryption protocols. This allows us to maintain the highest security standards and promote the safety of your data. To maintain alignment with these best practices and updated compliance requirements from the PCI Security Standards Council, Qvalent will disable the use of TLS v1.0 and v1.1 for connections to Qvalent/Westpac services. |
After Quickstream disables TLS v1.0 and v1.1, any connection to Qvalent/Westpac services must use the TLS v1.2 encryption protocol.
This change also impacts access to Westpac web sites and products such as:
There two are different channels that need encryption to access Qvalent/Westpac services. These channels are:
An overview of each are below:
When using most browsers, you will not have trouble accessing Qvalent/Westpac services. But you may have trouble if:
To quickly test your browser compatibility, you can visit our test page, which has TLS v1.0 and v1.1 disabled.
If you are able to view the site without errors, access to services via your browser should not be impacted by this change. If you receive an error, the page displays Steps for Resolution. Following these steps will help you change the settings in your browser, or upgrade to a newer version.
Find out more about TLSv1.2 Browser Compatibility. If you have Microsoft Internet Explorer, refer to the Internet Explorer Support for TLSv1.2 page for additional information. |
After Quickstream disables TLS v1.0 and v1.1, any connection to Qvalent/Westpac services must use the TLS v1.2 encryption protocols
API integrations are interfaces to Qvalent and Westpac services that are separate from, but use Qvalent and Westpac data.
Examples of API integrations are:
If you have implemented any of these features, make sure you have enabled the TLS v1.2 encryption protocol.
API integrations that use Java will generally need to use Java 8 or higher to enable TLS v1.2 by default. You may also use Java 7 and enable TLS v1.2 using the https.protocols Java system property. You may also need to make code changes to enable TLS v1.2. Services that run on Windows Server systems and use Microsoft Secure Channel for TLS must run on Windows Server 2008 R2 or higher. This generally includes most .NET applications and Microsoft Internet Information Server (IIS). Earlier versions of Windows Server do not support TLS v1.2. Refer to the Internet Explorer Support for TLSv1.2 page for additional information. API Integrations using NSS will need to use 3.14 or newer (preferably 3.15.1 or newer). Versions before 3.15.1 do not support TLS 1.2. |
To test the compatibility of an API integration to communicates with a Qvalent/Westpac service:
PayWay
Quickstream
To maintain access to Qvalent and Westpac services make sure your browsers and integrations have TLS v1.2 enabled.
If your browser or integration does not have TLS v1.2 enabled after we make this change, then your users will NOT be able to access Quickstream.
We recommend that you begin planning to support TLS v1.2 as soon as possible. If you are in a corporate environment, contact your I.T. administrator.
To maintain seamless access to Qvalent and Westpac services, make sure that browsers connecting to Quickstream have TLS v1.2 encryption or higher enabled.
Your end user can visit our test page, which has TLS v1.0 and v1.1 disabled to test their browser compatibility. Your end users do not need to update their browsers if they pass the test.
We plan to disable TLS v1.0 and v1.1 encryption according to the following schedule:
Find out more about TLSv1.2 Browser Compatibility.
If you have Microsoft Internet Explorer, refer to the Internet Explorer Support for TLSv1.2 page for additional information.
If you have any additional questions, please contact our Quickstream Technical Support team.