Thanks, That sounds like solid advise... In a shared server environment, I was not ever going to store the card number in the DB.
Jeff On 10/18/05, Ken Ferguson <[EMAIL PROTECTED]> wrote: > > Depends on their processor. This is similar to a recurring charge type > of situation. You could charge their card a nominal reservation fee and > then hit it up for the balance if they no-show (kind of like a bar > hitting your card for $50 when you start a tab and then ammending the > transaction when you tab out). I used to do something similar for > meeting registrations. I'd charge a small reservation fee up front and > then if they attended the meeting, I'd charge the balance of the cost. > Our rule was that no-shows were charged a $75 fee and for them, I'd only > hit them up for the balance of the $75. They key here is allowing the > processor to store the card details and you just store the transaction > number/code... Don't store the number and the exp... As has been pointed > out a million times on this list, it's just a bad idea. Also, call the > processor and talk with someone. They're likely to know more about how > their specific system could handle such a process that any of us. > Remember, your client is their customer and they should be able to > provide some customer service to help them get it all set up. > > --Ferg > > > J W wrote: > > >I have a client that that is in the tourism biz. The have trips that they > >fill that have a limited number of seats for. The problem is that they > have > >people reserving seats and not showing up at the last minute. They now > want > >to reserve seats using a credit card number and a sepcialized reservation > >system (that I will be developing). That way they can use that credit > card > >number to charge the customer (who is AWARE that cancelling past a > certain > >time will result in a charge) for the reservation. > > > >Now here are my questions. > > > >How do I/IS it possible to safely get and save this information via a > >private SSL on a shared hosting server. My sql is my only DB option, > >although if I push it I probably could get (read: fund by client) SQL > Server > >2000? > >What do I do with it safely, since they do not actually want to charge at > >the time of reserevation, but want to keep it incase of no show? > >They want to use their current processor to run the credit card number > >through (Some card companies frown on this) upon no shows. they really > don't > >want to have the added expense of another processor. > > > > > >Anyone ever run into this type of thing? Any suggestions? Legal > >implications?? > > > >Thanks, > >Jeff > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:221340 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
