[thelist] Specific Ecommerce Requirements

[ontheroad at frii.com]

Even with the split storage option, do you all concur that a secure 
certificate is a must as well?  I'm just finishing setting up a client 
with zen-cart, at least finishing what I can.  She "hates" PayPal and 
refuses to pay "Authorize.net" fees.  The cc storage option is door #3.

Followup question - zen-cart has limited payment options.  How much 
effort (programming, PHP - me probably) will it take to incorporate a 
choice not on their list?  - or - what are the chances that the other 
services (she might choose) will already have the development ready, 
ready for plug-n-play?

-Bob

 Christy Collins wrote:

>On Jun 28, 2006, at 6:57 AM, John Handelaar wrote:
>
>  
>
>>Hershel Robinson wrote:
>>    
>>
>>>But that's the answer--put in the MySQL DB. Many ecommerce  
>>>packages do
>>>this by anyway--even if they do place the charge automatically at
>>>checkout time.
>>>      
>>>
>>And they shouldn't.  You don't keep people's CC
>>numbers any longer than is absolutely necessary
>>(unless you want to comply with the processors'
>>data security reqs [tip: you don't] and/or get
>>ejected by your card company).
>>
>>At the very least make damned sure you both
>>deliver the checkout form, *and* receive it, over
>>SSL.
>>
>>There's code in some of the Drupal payment modules
>>(you'll want to copy one and edit it for your
>>own rather weird requirement) to switch protocols
>>at the right moment.  My own Linkpoint_API one
>>does it but isn't converted to 4.7 yet;
>>Authorize_net does it too and may be worth a look.
>>    
>>
>
>I think the way Zen Cart's credit card module works is it stores part  
>of the number in the database and emails part of it to you - this is  
>the module that comes with the standard installation and  you would  
>use for manual credit card processing.
>
>-C
>  
>