UPDATE OCTOBER 13TH 2022:
We've had to delay the release as a last minute issue was detected where it seems that Elavon is sending back an undocumented and unexpected error when 3DS 2.0 authentication fails, and provides no clear reason as to why or how they expect it to be handled. We have reached out to their developer support team with the details of the requests and responses from their system, and are awaiting their reply. While we hate to delay an important release like this, the risk of releasing something with a potential payment impacting issue is simply too great at this time. It is unlikely that this we will receive a response and resolution before the 3DS 1.0 deadline tomorrow, so we would recommend temporarily disabling the "Enable 3DSecure" setting on our module to ensure that your customers are able to make payments tomorrow via the WHMCS order process and client area.
UPDATE OCTOBER 11TH 2022:
Currently in testing, with an expected release on the evening of October 12th (Wednesday) or the morning of October 13th (Thursday). It will be a drop-in replacement with no upgrade procedure to help ensure it is as simple as possible.
Just a quick announcement to let everyone know that we are working to update our module to support 3DSecure 2.0 and aim to have it released as a drop-in replacement before the deadline on October 14th. We had some issues getting required information and account configuration from Elavon - which impeded our work for some time.
We are currently in the process of testing the updated module to ensure that all expected 3DSecure workflows work as intended and all potential responses from card issuers are handled as gracefully as possible.
To ensure a smooth transition, we recommend that anyone using our module to contact Elavon support and have them enable "3DSecure 2.0 with 1.0 fallback" (the fallback is required for some Amex cards that may still require 3DSecure 1.0 after the deadline).
Any updates will be shared here as edits.
We appreciate your continued patience and support!