[YamaDan]

Hi,

If I'm setting up an e-commerce site for a client

What do they have to set up & what can I assist in setting up?

Paypal can add users but they would have to set it up 1st?
Not sure about Sagepay and others.

And have I got this right:
If payment is wanted onsite I need the follwing:

Dedicated IP
SSL
Payment gateway (sagepay etc.)
Merchant acount (sagepays own or unsure on others)
Clients Business bank ac

And again does the client have to set up these payment accounts?


Thanks

Any help appreciated.

[T_break]

Just been dealing with this myself recently,

to take onsite payments you will need all the things you mention, but I would consider long and hard about advising your client to take "onsite" payment as they will fall well and truly into PCI compliance territory, which can be very expensive and time consuming experiance.

"offsite" payment does absolve your client of some of the responsibility under the PCI regulations.

As for your client having to take out these accounts, yes they will, ifthey are the ones being paid via the site they will have to set up the accounts for the gateway, merchant account in their or their business's name.

[YamaDan]

I'd better look up PCI?

What is the best payment set up then?
paypal, sagepay or other...

And how do you explain what to do to your client?

[T_break]

YamaDan, on 14 March 2010 - 08:20 PM, said:

I'd better look up PCI?

What is the best payment set up then?
paypal, sagepay or other...

And how do you explain what to do to your client?

The best payment set up is really going to be decided on what your client is doing, is the main priority cheap fee's, or is there specific types of payment that they need to cater for, there are no easy ways of answering that, it will have to be researched either by you for your client, or by your client.

Have a look at PCI compliance but keep in mind that depending on how you take payment over the site, it may not be applicable, but its best to thoroughly research it at the outset.

There is no easy way of explaining what a gateway and merchant account is to a non web developer, keep it simple and point them in the direction of some of the providers of gateways and merchant accounts, aswell as talking to web developers all day their customer services also deal with people who are taking the plunge and trying to set up stores on their own with limited tech knowledge, so they are use to putting things in basic terms.

Put simply, if you explain that they need a payment gateway to take payments from their website.
then they need a merchant account to receive the money they are taking from their site.
and as with any financial product this must be set up by the person who is going to be using it.

[Gareth Daine]

Hi,

Are you developing this solution from scratch or using some sort of shopping cart system?

If you're using a shopping cart solution such as Magento or osCommerce most of the major payment gateway's integrate seamlessly in to the solution. You just need to enter account data and the like. You won't need to worry about PCI compliance. To be fair, unless the website itself will actually be holding customers personal financial information, such as card numbers, csv's, expirary dates, addresses etc then it won't affect you. This sort of thing is dealt with by the payment gateway.

[YamaDan]

Hi Gareth,

I'm using CubeCart.
I want to know the best payment options available.
I'm thinking of using Sagepay & Paypal.

And what I need to get the client to do.
What details do they need to give me
when they have set up their bit.

Sorry if these questions seem a bit obvious,
I just can't get my head around payment systems.

Thanks for helping out..

[YamaDan]

T_break, on 15 March 2010 - 11:08 AM, said:

The best payment set up is really going to be decided on what your client is doing, is the main priority cheap fee's, or is there specific types of payment that they need to cater for, there are no easy ways of answering that, it will have to be researched either by you for your client, or by your client.

Have a look at PCI compliance but keep in mind that depending on how you take payment over the site, it may not be applicable, but its best to thoroughly research it at the outset.

There is no easy way of explaining what a gateway and merchant account is to a non web developer, keep it simple and point them in the direction of some of the providers of gateways and merchant accounts, aswell as talking to web developers all day their customer services also deal with people who are taking the plunge and trying to set up stores on their own with limited tech knowledge, so they are use to putting things in basic terms.

Put simply, if you explain that they need a payment gateway to take payments from their website.
then they need a merchant account to receive the money they are taking from their site.
and as with any financial product this must be set up by the person who is going to be using it.

Thanks T-Break,

If asked "what do you recommend"?

What's your answer..

[rallport]

Would personally go with Sagepay - there's a lot more checking and it's definately more secure than Paypal. E.g. data can only be posted from your websites IP address. They also have a UK based helpline you can call.

[YamaDan]

rallport, on 17 March 2010 - 09:42 AM, said:

Would personally go with Sagepay - there's a lot more checking and it's definately more secure than Paypal. E.g. data can only be posted from your websites IP address. They also have a UK based helpline you can call.

Thanks rallport,

Does offering both options make sense.(sagepay & paypal)
Or is that just making more work for myself & client?

[techwork]

Hi folks i'm about to be in the same situation and would also like to know about the payment gateways. Is it better to stick with one gateway or offer a couple like YamaDan asks? I was looking at autherized.net as it seems to be present in most shopping carts. is this one a good choice or are sage and paypal better?

Thanks

[BlueDreamer]

YamaDan, on 18 March 2010 - 08:41 PM, said:

Does offering both options make sense.(sagepay & paypal)
Or is that just making more work for myself & client?

Not everyone likes using their credit card online and will opt for a Paypal option if it exists. On the other hand many people don't use Paypal so you need an alternative.

The clue is in giving customers a choice - when you go to a real world shop you usually have many ways to pay, cash, credit card, cheques, credit/direct debit etc. Imagine if the shop only took credit cards and you wanted to pay in cash, wouldn't you just go elsewhere?

As far as your customer is concerned you need to discuss all the options with them and let them make an informed decision as to what will be best for their own business.

[techwork]

BlueDreamer, on 24 April 2010 - 07:51 PM, said:

Not everyone likes using their credit card online and will opt for a Paypal option if it exists. On the other hand many people don't use Paypal so you need an alternative.

The clue is in giving customers a choice - when you go to a real world shop you usually have many ways to pay, cash, credit card, cheques, credit/direct debit etc. Imagine if the shop only took credit cards and you wanted to pay in cash, wouldn't you just go elsewhere?

As far as your customer is concerned you need to discuss all the options with them and let them make an informed decision as to what will be best for their own business.

Hi BlueDreamer, when you put it like that it makes a lot of sense. Cheers

[rallport]

Gareth Daine, on 15 March 2010 - 12:29 PM, said:

Hi,

Are you developing this solution from scratch or using some sort of shopping cart system?

If you're using a shopping cart solution such as Magento or osCommerce most of the major payment gateway's integrate seamlessly in to the solution. You just need to enter account data and the like. You won't need to worry about PCI compliance. To be fair, unless the website itself will actually be holding customers personal financial information, such as card numbers, csv's, expirary dates, addresses etc then it won't affect you. This sort of thing is dealt with by the payment gateway.

Depends what method of Sage Pay integration you're using. E.g. Direct requires you to be PCI DSS compliant as your transfering sensitive data from your website to SagePay.

[rallport]

YamaDan, on 18 March 2010 - 08:41 PM, said:

Thanks rallport,

Does offering both options make sense.(sagepay & paypal)
Or is that just making more work for myself & client?

Well it's obviously more work.

But one of the great things about SagePay is the support they provide, espeically their integration kits.

E.g. with the direct integration kit you have a basic template on how to add paypal as an option.

However, from my experience, getting customers to leave your website to pay (and using Paypal in the first place) is a way to kill your conversion rates.

Paypal really does suck if your a seller.