Many of us who get paid to Perl have at least dabbled with e-commerce. If you have a specific or even general question why not ask it here? You don't have enough time to set up a new portal and write a fully blown e-commerce app, even if you could get a useful number of users. The only thing particularly specific to e-commerce (as opposed to general CGI stuff) is handling secure credit card tansactions and the like. All the rest is just vanilla CGI and database stuff.
There are really only three parts to secure transactions:
- Protecting the CC data in transit (use HTTPS with Apache and Open SSL) and securing your server to protect the back door.
- storing CC details securely. My advice is don't store the CC details. You cant hack CC details off a server if they are simply not there. Make the user re-enter CC details for every transaction (they will feel more secure about this anyway) Of course by all means remember all the other account details.
- Handing off to the 3rd party CC processor - they will supply the interface API spec and generally sample software in a variety of langs - and waiting on the response.
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|