Unsupported Cipher/TLS Version Update
Scheduled Maintenance
Report for Authorize.net
Completed
The scheduled maintenance has been completed.
Update
As we strive to continue offering a secure and up to date method for our clients to utilize our API for processing transactions, we have identified that some merchants are still using unsupported ciphers/TLS versions when connecting to our API endpoints. As a result, we are requiring all merchants using our API for processing to be using our supported TLS/cipher versions.
We are sending you this notice as our records indicate that you may be using unsupported TLS/cipher versions that will need to be updated before our deadline of October 30, 2024. You will need to work with your developer or solution support to ensure that you have the correct cipher/TLS versions.
For more information on our supported TLS/cipher versions, please reference the following documentation we have here: https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001526
Additionally, we encourage you to subscribe to our status page for up-to-date information on up-coming maintenance notices and current states of our Authorize.net services.
We are sending you this notice as our records indicate that you may be using unsupported TLS/cipher versions that will need to be updated before our deadline of October 30, 2024. You will need to work with your developer or solution support to ensure that you have the correct cipher/TLS versions.
For more information on our supported TLS/cipher versions, please reference the following documentation we have here: https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001526
Additionally, we encourage you to subscribe to our status page for up-to-date information on up-coming maintenance notices and current states of our Authorize.net services.
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled
As we strive to continue offering a secure and up to date method for our clients to utilize our API for processing transactions, we have identified that some merchants are still using unsupported ciphers/TLS versions when connecting to our API endpoints. As a result, we are requiring all merchants using our API for processing to be using our supported TLS/cipher versions.
We are sending you this notice as our records indicate that you may be using unsupported TLS/cipher versions that will need to be updated before our deadline of October 30, 2024. You will need to work with your developer or solution support to ensure that you have the correct cipher/TLS versions.
For more information on our supported TLS/cipher versions, please reference the following documentation we have here: https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001526
Additionally, we encourage you to subscribe to our status page for up-to-date information on up-coming maintenance notices and current states of our Authorize.net services.
We are sending you this notice as our records indicate that you may be using unsupported TLS/cipher versions that will need to be updated before our deadline of October 30, 2024. You will need to work with your developer or solution support to ensure that you have the correct cipher/TLS versions.
For more information on our supported TLS/cipher versions, please reference the following documentation we have here: https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001526
Additionally, we encourage you to subscribe to our status page for up-to-date information on up-coming maintenance notices and current states of our Authorize.net services.
This scheduled maintenance affected: API Connection/Endpoints (Accept Suite, Advance Integration Method (AIM), Authorize.net API, Boarding API, OAuth, Server Integration Method (SIM), Webhooks).