WhiteKnight

Well after some testing on our end and at our host and finding nothing, things started working again. We are using the exact same files as before this all started so it must have been fixed by First Data on their end. Of course they say they changed nothing.

I am not sure that all's well that ends well (if you can count being unable to process cards online for 3 days ending well).

The "CC DEBUG OUTBOUND" message that comes back from PREAUTH looks fine. Identical to those from a few days ago when sales worked and identical to the ones that come back from SALE except for the dollar amount and whether they say sale or preauth for ordertype which is exactly what you would expect. So I am lost as to where any extra characters are getting into the XML string. They do not show up in Linkpoint as preauthorizations since it is rejecting the XML string.

WhiteKnight, on 06 March 2011, 03:37, said:

Tsport, on 06 March 2011, 15:46, said:

If you use most web editing tools (like Dreamweaver) you will have a search or find function and usually options on how it does that.

So you search or find for "base64_decode" (for example) and select entire site. Then you will get a list of files with that code in them.
In the case of this example it is usually at the top of every php file in the site and it is usually easier to upload a clean copy of your files than fix every file.
Search the forums or Google for how to fix your system to prevent specific things you find.

If you have a way to get a files count on your host (maybe 400-several thousand files) you can check that and when no users are on it should only change when you add something. If it changes without you adding something than someone else added some file somewhere.
Sometimes you can find those by sorting by date/time on the host and seeing what the "new" files(s) are.

Of course do all the regular security measures detailed elsewhere on the forums, like file/dir permission, htaccess, etc.

Good luck.

I uncommented the 2 lines and that got me past the first error but now good cards come back with "Preauthorization Failed" messages (for bad AVS address) to customer (including me) and a return email (CC DEBUG INBOUND) from LinkPoint with an r_error of 'SGS-020003: Invalid XML".

Did something else change that I did not update but now needs to be?

Thanks for any suggestions.