Did anyone else using CyberSource get this notice ...
# general
d
Did anyone else using CyberSource get this notice last month? Did you do update your key successfully? I performed the prescribed change today (update the P12 key with a new one) and it completely broke our Credit Card processing. We're an ecommerce business so it's destroying our sales today. Now I fear for the weekend. I've been getting the standard run-around from NS Support for 5 hours now. I know the key is generated correctly, and had support watch me do it start to finsih to validate. Also, the key works..... but ONLY for my specific user. (No other user or context outside of my user in the UI can get a response from CyberSource). It smells of file permissions type problem on the new P12 key, but Support is scratching their heads on this.
t
Are you on the new SuiteApp version of Cybersource? If not you could upgrade and then use a REST key.
d
Hi Tim. I am not. We are on the older "Legacy" integration, which I was told will cease to work after February 28, 2026. My plan was to migrate to the SuiteApp version during our off-peak season of January. I've done the install on my Sandbox account, but had troubles with some aspects which I was still working out. So today's incident has me in a very bad place. Doing the changeover on a production account over the weekend scares the hell out of me. I had a perfectly working key this morning that didn't expire until 2/27/2026. But according to NetSuite there's no way to put that key back in place. I'm in a world of hurt at the moment.
t
Unless you have a copy of the old key then you are stuck. I will look to see if I have a guide from my team on installing the SuiteApp version but that is the one we use on our merchant accounts.
The SuiteApp version can be installed in Prod without affecting the legacy profile you have.
d
That's the funny thing. I do have a copy of the old key. But now that the Payment Profile configuration page requires a passphrase, I have no way of putting the old key back in place. I've asked if there's some backend way they can just put my old P12 key back in, just to get me going, and they said there is no way to do that. I began working on the SuiteApp, and just as I started getting my plan laid out I got a message from NS Support. They said an engineer made an adjustment and wanted to know if the issue with the new key was fixed. It was indeed fixed! I asked what they did.... dead serious, this is a cut/paste of their reply: "Our engineers performed a restart on the server." 😑 Appreciate your input and replies, Tim! Rest assured, I'll be moving up my scheduled upgrade to the SuiteApp.
t
Wow! So glad it got fixed! Whew!