Quoth BeenThereDoneThat
View Post
My employers' sites would take orders, auth against the API at the payment processor; get a response code and then the order system would continue or stop processing the order (initial auth) at which point if it succeeded, as the order batch closed, the next process was queued to finalize the transaction.
I got phone calls asking to change CC info, re process it, figure out why it was being declined (shipping vs billing address 99% of the time) etc. I had access to the human-accessible GUIs.
So, its not entirely unreasonable to be asked questions such as this; unfortunately your company does not choose to make the user interface accessible to CSRs, probably due to volume and potential fraud issues.
Comment