Storing credit card data

[Eric Chatonet]

Hi Richard,

We have solved a similar problem.
It supposes:

. A text file in the public section of the website where are stored  
current login/password and main address to a private and protected  
part of the website using salted SSL encryption.
. Actually login, password and main address (IP root address you can  
append to what you want) are never stored in the Rev client but only  
in RAM at request into a script local var that is immediately deleted  
when done.

Then this allows to retrieve or post any data from the user place to  
the server.
That's the first part.

On the other hand it does not seem difficult to build a Rev app to  
handle data stored encrypted on your server.
Hope this helps.

If you need more info, write me off-list.

Le 14 déc. 06 à 13:39, Richard Miller a écrit :

> Looking for suggestions on how to safely store credit card data. It  
> needs to be an automated process so that the card can be charged  
> monthly and it needs to happen from within Rev (i.e. can't use a  
> browser). Here's the scenario.
>
> 1. User enters their card number in our Rev app (from their home or  
> work computer)
>
> 2. For most of our services, we securely process their service  
> charge and immediately discard the card number.
>
> 3. We're now starting up an optional monthly service. We need to  
> take that card number, store it, then bill the user each month. It  
> should be a fully automated system, not requiring our staff to  
> enter a password or anything else for the periodic charges to be  
> billed.
>
> 4. We're using our own servers for data storage.
>
> Thanks.
> Richard Miller
> Imprinter Technologies

Best Regards from Paris,
Eric Chatonet
------------------------------------------------------------------------ 
----------------------
http://www.sosmartsoftware.com/    eric.chatonet at sosmartsoftware.com/