Pablo Manalastas writes:
>
> On Thu, 11 May 1995, Mary Christie Generalao wrote:
>
> > Can anybody possibly describe a typical setup
> > and how the following things tie up to my system setup: SSL, secure http
> > (are these built into the usual apache tarball?), certificates, capability
> > to accept visa payments, etc...
>
> For instructions on how to build a secure webserver (apache +
> mod_ssl + openssl) with support for scripting (PHP), database (mysql)
> and mail (IMAP), please refer to the site.
>
> http://www.geocities.com/pablo_manalastas/apache_build.html
>
> I have no experience with credit card payments, so someone else
> will have to answer this question.
To accept credit card payments, you'll need a merchant account with your
bank and a way to validate credit card numbers. Theoretically, it's really
no different from if you were running a real B&M store (salesperson
verifies your credit with the bank, you agree to pay X amount for Y
goods/services).
Of course, banks and credit card companies don't allow merchant
transactions over the network, so these are often left to third parties.
Most of them work using regular phone lines, making them impractical.
Another alternative is to go with one of the real-time online transaction
processors like Cybercash. They provide a server and a C library and API to
perform transactions. Supposedly, you are expected to write your web
software using their API.
Unless you do a huge amount of credit card transactions per day, it may be
best to just store the card numbers in an offline database and do the
processing offline as well, confirming orders via email.
Brian
--
Brian Baquiran <[EMAIL PROTECTED]>
http://www.baquiran.com/
AIM: bbaquiran
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
