Forum Moderators: buckworks
I would like idealy to use a cms (such as wordpress or movable type) to manage a site as this is already something I can do. If I got an off the shelf ecommerce package, could I manage the store side with a cms like these?
Why do some designers have completely intergrated shops while others use external sites to take payments?
Would I be better off starting with a blog like site and intergrating a shop, or the other way round?
And could someone explain exactly what the relationship is between a site and a payment proccessor?
I appologise for asking so many questions at once
[edited by: GGR_Web at 1:36 pm (utc) on Oct. 2, 2008]
Did you review Ecommerce 101 [webmasterworld.com] and Shopping Carts 101 [webmasterworld.com]?
Why do some designers have completely intergrated shops while others use external sites to take payments?
Couple of reasons...skill, budget and preference would be the main ones I can think of. An integrated payment system will be a bit more expensive and more difficult to implement.
My preference is for the integrated system. Keeps the flow of ordering (they don't have to leave your site). You also get more control, particularly in the look and feel of the ordering process.
Would I be better off starting with a blog like site and intergrating a shop, or the other way round?
Depends on your skills, the products, the niche/industry...quite a bit to consider. Would users benefit from original content? Or will they typically know exactly what they are looking for and need little information to order? Is it even something you could blog about and create quality original content? Will your time be best spent writing blog entries or tending to other aspects of the site?
And could someone explain exactly what the relationship is between a site and a payment proccessor?
Water to a fish, my friend. :o)
I'm afraid I don't quite understand this question, so I'll give you a general answer. The payment processor enables you to accept credit card and other electronic payments via your website. Think of it as the machine you swipe your credit card through at a brick and mortar store. It's one piece of the puzzle required to accept payments.
Check out Authorize.net for more information.
Prehaps I'd be better off with a book recommendation!
My last question: What I really meant to ask is what php ect I would need to have in place (in general). Also is this generally a paid for service?
While I'm thinking about this, does that mean the payment proccessor is all you need? Or do you need a payment gateway as well? (They could be the same thing, it seems)
I like the analogy by the way.
One last thing, what steps (in general) would you take to secure customer/order details?
Thanks for all your replies by the way!
I have a lot more clarity already.
You will save yourself a lot of hassle in the long run.
Most of the gateways will provide you some type of API to process the transaction on your secure website or they will provide you with a secure website on the gateway's servers. Some will allow some simple editing to maybe add your logo (but the logo will need to be called securely).
At the end of the day, the gateway batches the transactions to let the merchant account provider get the money. The money is then received from the issuing bank, transferred to the acquiring bank, then to the merchant account provider and then finally into your bank account.
You might have heard of third party processors, maybe (some versions of) Paypal. You basically use their merchant account to accept credit cards. And Paypal offers many "flavors" for you to choose from.
