Forum Moderators: buckworks

Message Too Old, No Replies

osCommerce and the transaction process

Is it a good idea to use it even if I'm not handling the transaction?

         

The Cricketer

2:46 pm on Apr 11, 2005 (gmt 0)

10+ Year Member



I'm looking at using osCommerce on my php website. I've never dabbled in shopping carts and the like before, but I'm starting to get an idea of what it all entails.

I'm just a bit confused when it comes to the transaction process of an ecommerce site.

I was thinking that if I go with my bank as a merchant the easiest option is for them to host the transaction process and deal with the user's private data and security.

The only pitfall to this is probably the changing of the url when it goes to the bank's secure web server (that's how it looks anyway) ie. an issue of trust, although it is a large and reputable bank.

My question is would osCommerce be easily integrated with this process? Or is it more honed to work with transactions on your own website using SSL and the like?

lorax

2:54 pm on Apr 11, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Two things come to mind.

First: Transactions are processed BY the processor BUT without your web visitors actually having to visit their website. The way it works is your cart contacts the transaction processor's server, passes the transaction information, gets a yay or nay on the sale, and then receives any follow up code (errors or messages). Your cart then decides what to do with these.

Second: the osCommerce community has built several modules for most of the popular CC Processors. If you go with one they don't have a module for then you'll need to build it yourself or have someone build it for you. Not overly difficult but you'll want to be sure it's done right to preserve security and privacy.

The Cricketer

1:47 pm on Apr 12, 2005 (gmt 0)

10+ Year Member



First: Transactions are processed BY the processor BUT without your web visitors actually having to visit their website. The way it works is your cart contacts the transaction processor's server, passes the transaction information, gets a yay or nay on the sale, and then receives any follow up code (errors or messages). Your cart then decides what to do with these.

The actual bank service that I was looking at offers the use of their technology etc to accomodate the entire transaction process. So I assume you pass the product, prices etc to the bank and then the user enters their confidential info on the banks secure web space.

However I'm also aware of the method which you have just stated. And this method seems to be the one which most use. So if I want the user to have a similar shopping experience to previous experiences then it looks like I will have to purchase an SSL certificate? I can then use the bank's other service which seems to do what you said above. Is this the better option?

lorax

8:00 pm on Apr 12, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Making the checkout process as seemless and painless as possible is always the better way to go. Avoid the off-site transaction processors (PayPal et al) as it breaks the checkout process and can kill the sale. The more professional your cart looks and functions, the more confidence your buyers will have and the more likely they will be to complete the sale with you.