And the parentheses are in the raw request? Funny... it seems as if CYBSC themselves aren't validating according to their requirements... Because I doubt Netsuite is displaying it in their raw request but hiding it when they send it over to CYBSC!

Great, if it indeed does. I spoke with Netsuite support again earlier in the week (or last) and they definitely had a good understanding of what the issue was. Let's hope they can work this out once and for all!

There's now a new defect #245767

I just spoke with support, and a very courteous supervisor went over the issue with me. Apparently, Defect 243163 was not to fix the problem, just to put in the first step of solving this issue. Basically, Netsuite is ensuring that any customers with the Cardholder Name field as blank are filled in. So, they populated the…

Correct. Cybersource is ultimately at fault here in my opinion as well. I am still baffled, however, that Netsuite is removing parentheses from the IDs, yet it won't do the same for the dash (-)? They told us yesterday the same; they asked Cybersource to turn off validation for all Netsuite customers. However, since ours…

I take it back! Netsuite is still sending the dashes along with the bill to company name!!! I do not understand why they insist on saying that it is fixed, when they keep bringing me proof from the fact that my transaction succeeded. CYBERSOURCE REMOVED VALIDATION FROM OUR ACCOUNT TEMPORARILY UNTIL NETSUITE FIXES THE ISSUE…

Well, there actually should be a way: Cybersource set it up so that their validation would occur in the Test mode. So, late at night sometime I can go ahead and determine if it has been fixed by turning our account onto Test mode and verifying that it worked. If I can a) remember and b) find some time tonight, I'll let you…

I think Netsuite themselves are majorly confused, and for sure their front line customer service reps do not have a clue of what is going on. I got an update to the case yesterday stating that if we simply correct the Cardholder Name on the Financial tab of the customer record, everything will work fine. I proceeded to…

Really? Because they claimed to fix mine, but that was only because it was in Production, which CBSC deactivated from validation. In Test Mode it fails...

Wow, good find jschneller... I wonder what Cybersource has to say to that???

Fixed! Wow, I cannot believe my own words... I turned on the Test Mode for one of our Cybersource accounts, ran an order through, and voila - even though the name of the customer was: AB 999-999-9999 The Bill-to customer name passed to Cybersource from Netsuite was: AB 999 999 9999 That passes validation, because the name…

I cannot believe that this issue still has not been resolved. Cybersource wants to turn validation back on (they suspended it for a little while now) and I tested just now and it is still not validating names with dashes in the following format: 999-999-9999 AARRGGHH!!! What is wrong with Netsuite support? Do they really…

Defect # 245767 CyberSource: Remove restricted characters and insert blanks to ensure requests meet new field validation SUMMARY: Error 102 when processing Sales Order Transaction with invalid characters Alternate Solution: None Your defect has been prioritized as an S2. From another email: You are correct that the Bill To…

Yes - though I wasn't 100% sure what that meant. "Mostly supplying Card Holder field" - whatever. From what I gather, they are adding logic to pull from the Card Holder field, where available. I guess we'll see in a week's time!

An update I just received from Netsuite: This is to update you that defect has been fixed for some characters only and these are below: "!", "@", "#", "^", "&", "*", "(", ")", "-", ":", "'", "/", "?", ".", "," A new defect has been filed (241573) to fix defect for below characters: "`", "~", "_", "=", "+", "[", "]", "{",…

jschneller, Agreed! Actually, I think they are using the Customer ID for us as well. The arbitrary breaking of first names vs last names is bizarre. The parentheses should also be scrubbed by Netsuite before going into the request. They really have to fix this fast.

The "fix" didn't seem to be working for us. Cybersource is bypassing validation for us, and so the only way to verify is to turn on test mode and see if it works - and it doesn't....

We had issues with the Bill To Company Name - which oddly enough is not feeding from any field in the Payment method "sublist" or "subtab" - it is taking the Customer Name from the transaction record. I guess that would be a logical thing to do, however, we use telephone numbers in our IDs which include two dashes…

Yes, when I spoke with them earlier they gave me the same line. Great, that helps us a lot!

Not solved! Shocker! We have been upgraded to 2013.1 as of 3/8, I went in to test it just now and it is still not working. I have no idea how Netsuite can get this wrong, and lie straight out telling us that it has been dealt with. Support has really hit rock bottom here. I must say, they had me going, too. I really…

This had better not be true...

I think that Netsuite says there is a fix - ours is coming with the new release.

???? For parentheses they are able to modify the data being sent over, but not for dashes? Does this make any sense to anyone? Come on, Evan, let's hear you, please? Or, any Netsuite employee for that matter. . .

A Miller, I believe that the reason the name was being split out is because they treat the first space in the name as the first name, and everything thereafter is treated as the last name. I am not sure if you had different results after changing the ampersand to "and" but that is how they have traditionally been breaking…

aaron5678, I suggested to Netsuite to change the field that they are sending to Cybersource in one of two ways: 1. Send the Customer InternalID instead of the Customer ID 2. Scrub the data, as suggested by jschneller above, and remove offending characters Of course, Cybersource themselves claim not to know which characters…

Thanks! I just got off the phone with them as well and it turns out that I need to submit a ticket and they will get back to us. They were looking for a time frame on when we would be able to resolve the issue on our end, because they are not going to turn off the validation forever. . . We'll see when that defect gets…

Agreed. In Netsuite's defense, though, there was no clear roadmap or requirements document released until after the rollout of these new validation procedures. Even Cybersource themselves were saying that they were not quite sure what the specific validation requirements were, when we originally called them as card charges…

It turns out that the last I heard from them a few days ago, they claimed it was fixed once again. I tested in Test mode / Sandbox, and the validation failed. It turns out that they left the dashes in, despite multiple requests of mine to remove them per Cybersource documentation. So, with the dashes in, apparently…

I don't get it - so Cybersource isn't keeping to their specs? They shouldn't be accepting parentheses!

Yes, I agree - we need to know what the "fix" was that was issued by Netsuite. The notifications I received did not specify...