Upgrade to SecurePay authentication platform
-
Received the following from Securepay: -Can you please advise whether whether this plugin will still work once this upgrade occurs?
When you initially integrated with SecurePay API you would have implemented a Legacy authentication code. The authentication code makes a call to the SecurePay API where two separate pieces of information are passed – the ‘grant type’ and ‘scope’ for the given ‘authentication url’.
This ‘authentication code’ implementation will no longer be in service from the 1st November 2021. All merchants using SecurePay API are requested to migrate to the new authentication code link. (https://click.email.auspost.com.au/?qs=9bd8e42ce2ce6bd033905aed45d79ff6ff8abb0af7619b82c3b144bf17b24e28fb16c3bbd93e808f345f41d17edfb46506fee0270691f553)
To migrate to the new authentication code, you will need to:
Change the ‘Authentication URL’ as per the documentation linkOnce the authentication url has been updated, you will need to pass a valid ‘audience’ value in the ‘request body’ as per the ‘Request Parameters’ section in the documentation link. The ‘audience’ value will replace the ‘scope’ value you previously passed.
There is no change to the authentication code response object. Your authentication credentials (i.e., client id & client secret) currently in use will not change and continue to work as they do today.
To avoid any impact to your checkout page, please ensure you have done this before the 1 October 2021 in test and the 1 November 2021 in production.
- The topic ‘Upgrade to SecurePay authentication platform’ is closed to new replies.