Newbie with a couple of queries.....

[ccjo]

Morning all,

Just signed up for a BP retail package with a view to moving over to BP for our main website later in the year if it really is as good as it looks

I wondered if you guys could help me with a two questions which have come up straight away.


Firstly, I keep getting certificate errors/warnings when looking at the site. I don't have this issue on my current set up & have never bought an SSL cert in the past. I have payments set to be collected via Paypal atm as I haven't got round to linking my Sagepay account yet. Can anyone advise me on why this is happening?

Secondly, I currently use Sagepay server - will the above issue be resolved by changing to Sagepay direct? Anyone with any experience of going between the two your thoughts would be appreciated!

Thanks very much in advance for any replies - I may be needy now but will return the favours when I can

Jo

[Dave]

Hi Jo,

Welcome to Bluepark and the Forum.

I suspect your certificate errors are because you have SSL Mode enabled in Site-->Configuration-->Payment Tab

If SSL is enabled it looks for an SSL Certificate which you have not got!

Try switching the SSL mode off.

If you want to use SagePay Direct you will need a SSL Certificate.

Hope this helps.

[ccjo]

whoa - quick or what

Thanks Dave. SSL is unticked now but I was as they say 'fiddling' last night so that may well have been the problem!!

Am I right in thinking Sagepay direct is the way to go if you do not want the customer to be taken to a new secure window hosted by Sagepay? A more seamless checkout experience is something I want to achieve going forward.

Thanks again,

Jo

[Adam]

As dave said, turn off the SSL mode and keep using Sage pay server..

and yes using direct the sage pay screen loads inside your web template, so does not take them to the sage pay page. most customers are used to being re directed though and we have not found a problem with using server

[Dave]

Hi Jo,

Yes , SagePay Direct allows you to take payments on your site and will give you the seamless checkout expericence you are looking for.

You have made the right decision to go for Bluepark and will not be disappointed.

It is a very good package and the forum is very useful in helping with both the building and marketing of sites.

[ccjo]

Fab guys - thanks v much. I think I'll get Sagepay server working for now & go read some of the set up instructions - something I hate doing!

No doubt be back here v soon........

Jo

[Adam]

happy to help Jo,

have fun reading the set up instructions...

Adam

[KayJay]

Here's something to bear in mind re SagePay Server vs Sagepay Direct that we have experienced on a provider other than Bluepark. We originally used Direct so our website handled all the payments and everything looked seamless. This was okay until a transaction didn't complete properly between SagePay and us. What then sometimes happened was we would think an order had gone through okay, send the products out then discover when we came to do our bank recs that we had not been paid. I know the easy answer would be to reconcile SagePay to our total orders each day but that isn't always practical. We would then have to contact the customer and ask them to pay for goods they had already received a while ago.

Anyway, we now use SagePay Server and customers go to a Sagepay hosted page. If a transaction fails, things happen the right way round for us, the payment is taken but the order does not complete properly and shows up as 'In Progress' This way, we can either contact the customer to see if there was a problem or we can manually check the order to SagePay and see that a payment has indeed gone through and complete the order ourselves.

Hope this helps!

[Dave]

Here's something to bear in mind re SagePay Server vs Sagepay Direct that we have experienced on a provider other than Bluepark. We originally used Direct so our website handled all the payments and everything looked seamless. This was okay until a transaction didn't complete properly between SagePay and us. What then sometimes happened was we would think an order had gone through okay, send the products out then discover when we came to do our bank recs that we had not been paid. I know the easy answer would be to reconcile SagePay to our total orders each day but that isn't always practical. We would then have to contact the customer and ask them to pay for goods they had already received a while ago.

Anyway, we now use SagePay Server and customers go to a Sagepay hosted page. If a transaction fails, things happen the right way round for us, the payment is taken but the order does not complete properly and shows up as 'In Progress' This way, we can either contact the customer to see if there was a problem or we can manually check the order to SagePay and see that a payment has indeed gone through and complete the order ourselves.

Hope this helps!

This was obviously a failing with the system you used before and I am fairly confident this would not happen in Bluepark.

If the payment fails or the order is not completed the order will remain as order in progress. Only when the order has been successfully placed and payment taken or authorized will the order be shown in the order manager.

We have been using SagePay Direct with Bluepark on two sites for many years and have had no problems.

[KayJay]

This was obviously a failing with the system you used before and I am fairly confident this would not happen in Bluepark.

If the payment fails or the order is not completed the order will remain as order in progress. Only when the order has been successfully placed and payment taken or authorized will the order be shown in the order manager.

We have been using SagePay Direct with Bluepark on two sites for many years and have had no problems.

That's good to know. The Bluepark versions of our sites are their 3rd incarnation and so far Bluepark has shown itself to be a much more robust and reliable system. Maybe we will investigate going Direct sometime in the future as I have to say, our past experience put us off completely!

[Dave]

That's good to know. The Bluepark versions of our sites are their 3rd incarnation and so far Bluepark has shown itself to be a much more robust and reliable system. Maybe we will investigate going Direct sometime in the future as I have to say, our past experience put us off completely!

KayJay,

You won't have any problems with Bluepark in terms of reliability. It's pretty much bullet proof and the most stable and robust package we have ever used and we tried many before finding Bluepark.

Good luck with your sites.

[icegems]

Something to bear in mind when you are looking at hosting your own payment pages is that you need to be fully PCI compliant. At least when you use the third party servers generally the PCI compliant bit is handled by them (unless you are taking telephone payments then the responsibility flips back to you).

[ccjo]

Have to say after a mornings research on PCI compliance I think I'll stay with Sagepay server for now!

[petad]

Something to bear in mind when you are looking at hosting your own payment pages is that you need to be fully PCI compliant.

My understanding was that as Bluepark are PCI compliant, we are covered by this? The following is a quote from Rich:

"There’s nothing to worry about there....... We have our servers PCI tested on a quarterly basis, furthermore none of your customers’ credit card details are stored on the server."

[icegems]

That is good! It seems Bluepark is covered for all eventualities. We had a nightmare with my previous provider because about 6 months or more ago they took down their own payment pages at 5.45pm on a Friday night as they had a problem with PCI compliance. No notice just gone, luckily I only used that method on one out of three sites but I was mighty pee'd off at the time.