Does anybody in this channel use Adyen as a payment provider? If so, are you experiencing any issues with payments?

We use Adyen and haven't noticed any issues with payments - though we haven't updated the bundle from 1.20.06 to 1.20.08 yet

We are also on Adyen, and are experiencing problems since last nights NetSuite update. Maybe different data centres? Ours in UK.

Curious question for the ones using Adyen, what do you use it? It is related to the support of your region/country? Is it related to the cost? I'm just curious, I'm more familiar with other Payment Processing Providers and the other day I came with a client using it. It was from Canada, so I'm curious about it.

We used to use CyberSource, but was forced to move when 3DSecure v2 came in to place as they did not support it. Adyen was on the list of supported plugins that had 3DSecure v2. In fairness to Adyen, we have not had any issues using them, their backend and risk setup is easy to use. The most recent payment issues were both to do with NetSuite, not Adyen.

Exactly the same reasons as @Chris Geast. We were with Cybersource. It was down to cost and 3D Secure V2 compatibility. It looks like recent payment issues have been linked to NetSuite eFix updates. It took NetSuite 12 days to resolve the previous issue, hopefully it doesn't take as long to resolve this one.

Just started getting payment issues with error of "Unexpected token in object literal (ES_Adyen_Constants.js$8648833$lib#108)".... is this what you all are receiving?

Hi @Shelby Owens, yes, that's the error. NetSuite have created a defect for it.

I'll open up a case then, thanks for the quick response!

Where are you based @Shelby Owens?

No worries, mention defect number 792848 so you can get add on to it.

North Carolina in the US @GWilliams

Not just UK based businesses affected now

Seems very much system wide.

Looks like it is affecting other payment processors as well - there was a post in the performance channel about the same token error for braintree

Back up and running this morning at around 7:30am.