https://netsuiteprofessionals.com logo
Join Slack
Powered by
3D Secure bug in 2022.1: Any clever people got a s...
# suitecommerce
g
3D Secure bug in 2022.1: Any clever people got a solution for this one? When creating an order with a new card and 3D secure. The 3D secure process fails because the id of the credit card is “-temporal-“. I guess meaning the card doesn’t exists in NetSuite yet or something like that. Note: It’s fine if the card already exists. For reference, fails here: CardHolderAuthentication.Model.js - line 31: cardholderAuthenticationRecord.setFieldValue(‘paymentoption’, options.paymentOption); ERROR: Invalid paymentoption reference key -temporal-
f
Hi, do you have a support case number I can check? thanks
g
Hi @Flo . I tried NS support but this customer only has basic support so they wouldn’t look at it. The details should be on the case though. Support Case #: 4977960.
f
Thanks, i will take a look
g
@Flo in the meantime I managed to code a workaround by forcing the card to always be saved.
👍🏻 1
f
Thanks. I´ve created an issue record so the team can take a look at it.
could you please let me know which Payment Processing Profile / Gateway is the customer using?
g
@Flo Worldpay (Access). They’ve recently updated it. So that it supports 3DS
f
thank you
g
@Flo Thanks for looking into this.
👍🏻 1
@Flo Any news on this? Got a company waiting to add payment to their site.
f
Hi Gordon, QA team has not been able to reproduce it on our test accounts
g
@Flo I’m assuming you tested with 2022.1 and added a new card during checkout? That’s annoying then 😞 Wonder why it fails for me.
f
Yes, 22.1
g
Any suggestions?
f
We can not test in your customer account as they only have basic support
So we do not have access
g
I guess I am stuck then. I will have to think what to do.
f
Have you tried contacting the payment gateway?
g
Yes, I had them on a call, they said it was clearly a SCA code issue and I agreed.
I’m not sure how it could be anything else.
The checkout starts, the id of the payment is “-temporal-” and then it tries to set that value as the payment method on cardholderAuthenticationRecord. I’m not sure where in that process it could be anything else, unless the plugin can somehow change the id to a real value. But that would mean saving the card.
f
The problem is that if we can not reproduce it on our test accounts and can not test in you customer account there is not much we can do
g
Yep, I know. How could I allow you to test in the customer account? Is that an option?
Open in Slack
PreviousNext
Powered by