Hi all, Does anyone know what enabling strong consumer authentication within a Cybersource payment processing profile actually does? Also, is this different from 'customer' authentication? I am hoping it issues a 3DS challenge when someone adds a credit card to their account on our SCA site, but the Netsuite-specific documentation seems to be practically non-existent. We've had issues with orders being cancelled ever since we migrated from the CS legacy app to the new SuiteApp. On the old version, a customer couldn't create a sales order with bad credit card info. Now, as long as you pass the Luhn algorithm, you can place an order (that then immediately gets cancelled) with bogus info. This has complicated our order processing quite a bit. If anyone had any tips or solutions, that would be greatly appreciated. Thanks in advance for the help!

Hi Jack, Yes, I believe strong consumer authentication triggers 3DS challenges. Enabling it when saving cards should help with your issue because 3DS first verifies the card is valid and enrolled with an issuing bank before authenticating the cardholder. Fake card numbers that just pass Luhn shouldn’t make it through that process.

Thanks Matt, I'll update this thread once I get a chance to actually try it out.

Happy to help. Keep me updated if it works!