Yeah I am still trying to figure out all that can be done through my
merchants API and Online system. Looks like I can do all of what you
mentioned.
Yeah I have some clients that insist on storing there credit card info on
the web server and it really scares me. I have warned them many times that
they need to develop a better system. Oh well, don't have to worry about
anymore as I am my on client now.
Neal Bailey
Internet Marketing Manager
E-mail: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
_____
From: Mary Jo Sminkey [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 8:52 PM
To: CF-Talk
Subject: Re: Credit Cards - Best Practices
>Lastly, you can opt to do it the safest way possible: Don't store the
>cc numbers at all. Collect them on your secure form, send them to the
>card processing gateway and DON'T store them. There are many who will
>say this is the best way, and I think it is. It limits the customer's
>liability and, perhaps as importantly, your own.
Just wanted to add my agreement to Matt's post here...and add that you can
still do authorize at the time of sale and then capture later, at least with
most processors I have worked with. Most will return a transaction ID when
they run the authorization which you can later use to then capture the
funds. You can do returns as well, either through your application or using
their online system, so there really is no need to have the credit card
number at all. Of course, convincing clients of that is another problem
altogether!
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
