the good news is that the PC Charge version they have IS supported (whew!)
I think we resolved the issue and in case anyone else searches on this, here is what we found.
The IT staff had launched the PC Charge payment server a second time using an RDP connection. You can't have PC Charge running twice, it confuses the heck out of itself and Sage100 while assigning and updating those TroutD numbers. I knew it can't be running under 2 different logins. If I had looked in task manager I would have seen the active charge executable running twice. and could have saved myself a whole lot of frustration over this.
The fun part was the level one tech who first tried to push me off to Sage then after 45 minutes she suggested that I call the Merchant Service Provider. REALLY????