Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Westpac Quickstream (including QuickWeb, QuickConnect, QuickVault, QuickView, QuickTerminal, QuickGateway, REST etc.)

  • Westpac PayWay (including PayWay Net, API, Virtual Terminal etc.)

  • Westpac iLink

  • Westpac QuickSuper

  • Westpac Payments Plus

  • Westpac Invoice Finance

  • Westpac BankRec

There two are different channels that need encryption to access Qvalent/Westpac services. These channels are:

...

  • Secure token request for QuickWeb, QuickConnect, QuickVault, and PayWay Net.

  • API requests for QuickGateway, QuickVault, PayWay API, REST API or iLink HTTPS/SOAP

If you have implemented any of these features, make sure you have enabled the TLS v1.2 encryption protocol.

...

  1. Perform a API request to the test environment. 

    • If you do not receive a TLS handshake error message then the underlying TLS connection was successful using the updated ciphers.

PayWay

  1. Point your test environment to connect to the PayWay. You may have implemented

    • PayWay Net with a secure token request, or

    • PayWay API

  2. Perform a secure token request or API request using the TEST merchant. 

    • If you do not receive a TLS handshake error message then the underlying TLS connection was successful using the updated ciphers.

...

Services

CBC disablement and TLSv1.3 enablement schedule

Test environments (all)

*.staging.qvalent.com was implemented 20th May, 2024.

*.support.qvalent.com will be disabled on 3rd of July 2024.

Production environments (web browser access)

October 2, 2024

Production environments (REST API integration):

October 8, 2024

Production environments (API integration):

October 15, 2024

Production environments (Token Requests):

October 22, 2024

Production environments (file transfer):

October 29, 2024

...