Hi, We are running into a 3D Secure error when placing an order in SCA. The user fills out the Checkout form, clicks the Place Order button, the 3D Secure runs, in the pop up modal after the text/email authentication is done, it shows a ‘Continue’ button in the iframe which on click results in ‘Unexpected Error’. If the ‘Continue’ button is not clicked, the order is submitted successfully. It usually takes 5 secs for the ‘Continue’ iframe to disappear when not clicked.  We have observed this across major browsers and have noticed it post the 2021.1 release. The error is originating from the “threedsecure.ssp” script.  Has anyone observed this of late? Any clues as to what or why this is happening?

3DS performs a callback to Netsuite at the end of the authentication process. It sounds as though the Netsuite callback handler is getting a duplicate submission, calling order.submit twice and throwing an error (I've built a custom 3DS handler on Netsuite before now and seen this occur). The underlying issue with Netsuite is the very slow order finalisation. On most systems, it'd never be an issue as the order finalises in milliseconds, so the user never gets a chance to interact with the process - but Netsuite takes substantially longer. Have you got "Asynchronous AfterSubmit Sales Order Processing" switched on? If not, enabling may at least help mitigate the issue.

Hi @Dominic B   Thank you for your reply. We do have Asynchronous AfterSubmit Sales Order Processing switched on.  Based on the order of the log messages, the order appears to be successfully created in NetSuite and later an exception is thrown that is caught by the surrounding try/catch block. Instead of passing the order confirmation number to the frontend, the “Unexpected Error” is passed to the front end. Is it possible that the “Unexpected Error” is due to a user event script error that’s occurring in an asynchronous after submit event script?

It could be a user event, but I'd think that's probably unlikely if the order is completing successfully if the button is not clicked.

the error screen grab

I spent several weeks resolving a similar (commerce API/non-SCA) issue, including a lot of discussion with support. The ultimate solution was to point the 3DS callback at an intermediary script which caught the threedsecurekey, then responded almost instantly, redirecting the user away from 3DS and on to another Netsuite page. That page then did the final order submission. I documented the issue and sent details to Netsuite, asking them to forward onto SCA devs, as there were similar issues going on at the time with SCA customers.

Thanks Dominic. We have raised a Support ticket and have escalated with our Account Manager. Hope to make headway soon.