Incomplete Orders

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   From many years of experience with PC and Authorize.Net...

...most of the time the information coming back through Authorize.Net is extremely generic, and card-type dependent,   For example, most declined AMEX charges I encounter are for a mismatched card code (people use the 3-digit code on the back instead of the 4-digit code on the front), are merely logged as "Declined (contact card issuer to determine a reason)".

If the same person were to mismatch on a Visa or MC, it would actually report the card code mismatch as the declined reason.

I think any store manager using Authorize.Net should have access to the Authorize.Net control panel.  While I can understand why it would be nice if the info did get passed back to the shop, I actually prefer that it not.  I like to keep the credit card transaction history (of which the shop I run has a lot) separate from the data in the shop.  The last thing I need is an extra pile of data to keep intact in my shop db. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
amgqmp1 Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 01-November-2005 Location: United States Status: Offline Points: 0	Post Options Post Reply Quote amgqmp1 Report Post Thanks(0) Quote Reply Posted: 27-April-2010 at 5:15pm
	From many years of experience with PC and Authorize.Net... ...most of the time the information coming back through Authorize.Net is extremely generic, and card-type dependent, For example, most declined AMEX charges I encounter are for a mismatched card code (people use the 3-digit code on the back instead of the 4-digit code on the front), are merely logged as "Declined (contact card issuer to determine a reason)". If the same person were to mismatch on a Visa or MC, it would actually report the card code mismatch as the declined reason. I think any store manager using Authorize.Net should have access to the Authorize.Net control panel. While I can understand why it would be nice if the info did get passed back to the shop, I actually prefer that it not. I like to keep the credit card transaction history (of which the shop I run has a lot) separate from the data in the shop. The last thing I need is an extra pile of data to keep intact in my shop db.