FISGlobal.com / Certegy review: would not cash my federal tax retun check 5

I went to Wal-mart today to cash my Federal tax refund check. The clerk input the information they need to cash the check. It was denied, and I was given a little slip, from Certegy Check Services, with reason number 3 as the reason they denied the check. The clerk entered it again, and same result. So I called Certegy (ultimately 3 times), and was told by the first guy, that this happens sometimes and he gave me instructions to give the clerk to try again. I hung up, we tried his way with the same result; reason 3. I called them again, got a different guy, and he said the problem was that my social security number did not match my name. Keep in mind, I've had this name (and of course SS # lol) for 16 years. I was told by him the problem was with Equifax (they provided the information), and that I should call them. I called, and was unable to talk to a live person unless I requested a credit report. So I came home, got online and did my annual free credit report to see if I could figure out the problem. Everything there was correct, so I called Certegy AGAIN, and got a different woman this time. She looked at everything and could NOT find a reason that my refund check was denied. I was then connected to a supervisor, who ultimately told me the reason the check was denied, was because SOMEthing about the check had sent a red flag up and tripped their fraud procedures and denied the check. I asked how could this be as it is from the US Treasury? He told me that somewhere in their database, someone passed a fraudulent/bad check that had SOMEthing in common with my check. So they refuse to cash my check, and that's that! After doing some thinking, the only thing I can think of, is that when Walmart enters the check #, their program (Certegy) only asks for the last four digits of the check #. I think if they had been able to enter the entire check number, all would have been ok. But because it was only the last four digits, someone, somewhere in the world probably passed a bad check with those (the last 4) numbers on their check, so it spit mine out as fraudulent, based on that. Of course, the supervisor could NOT tell me what the exact reason was as it would jeopardize their fraud safety measures. So I am surmising it had something to do with the check number. That's the only thing it COULD have been. So I think Certegy needs to ask for the ENTIRE check number, so that this doesn't happen again. It was a horrible experience, as whenever a check is refused, all anybody sees is your red face walking away with no money...as though it is your fault. I hope this experience is helpful to anyone else out there, and will help change Certegy's practices (though we know THAT'S a pipe dream).