[UPHPU] eCommerce with PHP
lists at strictlyrockymountain.com
Fri Oct 22 11:35:12 MDT 2004
Just for reference, I know I don't know everything, and there may be
others here with differing experiences. And I'm not claiming to hold all
of the pieces, just note that I'll give you what I have.
>From my experience the CC Processors can vary greatly. You might pay a
$20 fee monthly and then 0.02 cents per transaction on up. One site I
heard about was charging a much larger like a few hundred dollars to use
their "API" interface, but we didn't go that route so I can't quote it for
Using client side digital certificates is one way to get the
communications secured, but it seems easier to use cURL which can handle
the https: of a server side certificate instead.
Here is what the curl home pages says:
Curl is a command line tool for transferring files with URL syntax,
supporting FTP, FTPS, HTTP, HTTPS, GOPHER, TELNET, DICT, FILE and LDAP.
Curl supports HTTPS certificates, HTTP POST, HTTP PUT, FTP uploading,
kerberos, HTTP form based upload, proxies, cookies, user+password
authentication, file transfer resume, http proxy tunneling and a busload
of other useful tricks.
But everyone of the processors that I've run into have documentation and
often will have demo's or examples in the most common webprogramming
languages. So make sure to check with them first. I've called them
before having an account, telling them I'm creating a "CART" and want to
know how to communicate with them. They are always willing to help if
they are going to get some money out of it. :)
> On Fri, 22 Oct 2004 08:56:40 -0600 (MDT), John
> <lists at strictlyrockymountain.com> wrote:
>> I have done a few stores and credit card processing myself. And I
>> could help answer some of your questions. The basic rule that I have
>> found is that it's pretty simple. Most "real" bank types (as opposed
>> to paypal types) require that you have 1) a valid bank account. 2)
>> have an "Internet Merchant Account" setup on the bank account (not
>> just a merchant account, it has to be an internet merc). 3) Once you
>> have those, find a credit card processor who works with your bank.
>> Often the bank will suggest one or more credit card processors with
>> which they work.
>> (Authorize.net, Iongate-Now defunct, YourPay, etc).
>> I've mentioned those because the processing companies have different
>> ways of communicating. Also you will need "cURL" installed as a
>> module into PHP. "cURL" is a program that can send an "https" POST,
>> which from what I've seen is the most common need to communicate with
>> a CC
>> Processor. The in return to you will receive either an webpage/xml
>> doc/or simple csv (key=var) type of response back. And you'll be
>> looking for either "APPROVAL" or "DECLINED", in that response.
>> >From there you can either tell your script to notify the user of a
>> processing error, or accept the order and begin shipment.
> How much do those services usually cost, what are the common/good
> scripts out there that handle carts, shipping, etc, and what about SSL
> certificates? I've worked with one single eCommerce job which involved
> working with LinkPoint Cart, and Card Service International, but
> that's about the extent of my eCommerce experience.
> Bryan Petty
More information about the UPHPU