Email with middle cc numbers for Auth.net?

The Zen Cart credit card module sends the store owner an email after a completed transaction with the middle 8 digits of the credit card number - which is a GREAT feature. Is there any way to incorporate this into the Authorize.net AIM module?

Thanks.

No. You should never have need for the full credit card number, esp when it's already been processed.

Why do you think you need it ?

Thanks again for quick reply! This client rents refrigerators/microwaves to college students. They're delivered to the students' dorm rooms in August, then picked up in May. If picked up units are dirty, broken or missing, client would like to charge credit card with appropriate fees as outlined in "Acceptaqnce Required" T&C page. Auth.net allows transactions against a credit card (via their transaction id) for up to 120 days only, so access to cc info after that would be nice.

Any ideas?

This would be a violation with authorize.net terms and conditions, with thier fraud protection etc.

However the card can still be charged within authorize.net merchant account have you looked in there?

Actually, I know little about Authorize.net, although just downloaded their manual so I can start to learn. I'm relying on the client's interpretation of what he can/can't do with cc info.

I appreciate the quick responses to this - let me dig into this Auth manual and see what I can find as the best legal, ethical and practical option(s) to respond to this issue.

Thanks again!

You might find that a dialog with an auth.net representative may help you answer your questions quickly also.

Yes, however that very much depends on the level of expertise of the support person. I've talked with them several times now, and all except one had fairly limited knowledge - at least about ecom systems.

Interesting discovery - while we were waiting for our SSL cert to be installed, but anxious to test the system, everybody at Authorize.net told us that non-SSL transactions would be rejected. Our host support guy said they wouldn't. So we tested Authorize.net AIM with real data and no SSL and ...

... everything worked just fine!

Not that I would ever recommend using non-SSL on a production site, but good to know for testing.

Thanks so much for your quick responses and productive help. Since my first Zen Cart site is now live (and seems to be working very nicely, indeed!), I will start a monthly contribution to the Zen Cart team, and announce my intent in the appropriate forum with the hope that others may agree with my logic and take similar action.

The system is great, your team is TERRIFIC! Thank you.