Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: buckworks
The answer to that is that it depends on the site's audience and geographic location. The key is to have content that brings in people with an interest in purchasing those products.
When you want to start a ecommerce site, and you have to choose a provider like auth.net, chase.com, etc.
Now you have to program the link between your ecommerce store and the CC provider to perform operations like charge/void/refund/auth/etc.
Their are products that come pre-packaged that handle these functions for you, and they have a list of paymnt gateways that they support.
I'm asking for some recommendations on this type of software that work in a php environment.
There are products that come pre-packaged that handle these functions for you, and they have a list of payment gateways that they support.
I'd work this the other way around: choose your gateway, then apply the interface. Every gateway I've worked with provides sample code to integrate with your web site, but to answer your question, they also provide lists of shopping carts and other products that have tested integration with their systems.
I'd do it this way because in the end, the merchant account/gateway you choose is going to determine the cost and ease with which you perform transactions, and you may be limited by the requirements of your merchant account.
For example, wife's in-store merchant account would only allow certain gateways and methods used with their account, all at a cost much higher than needed. As a programmer, I was aware of some of the more difficult caveats of integrating these systems, just another difficulty to overcome, in some cases. We eventually selected a second merchant account that is a combination of the bank account with the gateway, saving us loads of money on online transactions.
You don't want to use something that is sending all the data out a back door and into a waiting van to be used for who knows what.
You also don't want something that is vulnerable to XXS or other attacks. Make sure whatever you use is tried tested and true.
[edited by: Demaestro at 9:24 pm (utc) on May 1, 2008]