Digital UK Design Blog

A few months ago a requirement came up in the Land Rover Project to move from Paypal Website Payments Pro (UK) to using Protx.

Both of these systems enable you to take online payments directly from customers’ credit cards, but what’s the difference?

Well Paypal was a great early choice for us. L. R. Series already had a very strong eBay presence as so used Paypal heavily already. They were familiar with the Paypal admin systems and given that their own website was about to be launched there was merit in easing that transition by not changing everything all at once.

Additionally Paypal have one great feature: they don’t require that you have a merchant account. Paypal act as the merchant on your behalf. This was necessary for the Land Rover people because as a new startup they would have been unlikely to get merchant status from their bank.

So Paypal have a lot of positives. The downside to Paypal is that they charge for the privilege of them being your merchant; don’t support Verified by Visa nor Mastercard Securecode and so leave you much more susceptible to chargebacks; we also found that CVV/CV2 failures weren’t being rejected or flagged up clearly in the administration panel.

Enter protx.

To use protx you must have a merchant account – you need to contact your bank and jump through a few hoops so that they can satisfy themselves that you are merchant-worthy.

Once you have this then you can sign up to Protx and let them handle the payment for you.

The best features we found with Protx when compared with Paypal are, in no particular order:

  1. Reduced transaction fees
  2. Quicker to get money from them into your account
  3. Better security – e.g. VBV and MSC are supported; the admin panel is awash with traffic lights about the security of the transaction; you can add more policies to determine which transactions are rejected immediately.
  4. Great customer service

All handy experience to get just before starting with Ebuyer.

I am itching to install the next release of UbuntuHardy Heron.

I tend to break things by getting overly excited and installing betas so I am going to have to be patient and wait until April…

To connect to my work PC I run Bitvise’s Tunnelier on my work PC and SSHD at home. My work PC then connects to my home machine and “asks” it to forward traffic from certain ports over the Internet to work. The idea being that I can then RDP from home to work using the SSH tunnel.

Now this all works fine, but I found that if the connection at work died then when work tried to reconnect the port forwarding failed with Received disconnect from <IP>: 11: Server denied request for client-side server-2-client forwarding on 127.0.0.1:3389.

What this message meant was that my home PC still thought that the old connection was alive and was honouring the old request to forward port 3389.

The only way I had around this was to restart my machine/all the networking services… until now. Now I just do sudo iptables -P FORWARD DROP and life is peachy.

I have not yet worked out fully what this has done – as it is just my machine and no other forwards are in place I am not concerned, but if you are not the sole user of your box then I would not use it as-is without expecting to upset a few people.

After a reconfiguration on our Debian based shared host I was left scratching my head about this error in apache log file:

[Wed Feb 06 21:09:50 2008] [info] [client 84.12.26.107] (70007)The timeout specified has expired: SSL input filter read failed.
[Wed Feb 06 21:09:50 2008] [info] [client 84.12.26.107] Connection closed to child 0 with standard shutdown (server www.blah.com:443)

It occurred whenever we tried to upload an image file (big or small) over HTTPS/SSL. I didn’t have time to debug the app because of other work commitments and waited for our hard working host to sort it out – although a simple standalone script which received a file and copied it to a folder worked fine.

Anyway, it turned out that GD Library hadn’t been re-installed – not that you could tell from that uninformative message! I have posted this here for posterity because searching the Internet for the message did not yield any suggestions.

If you ever have to dismantle a greenhouse please do not just smash it to pieces and let nature take its course – I’m still picking out handfuls of glass after months of working on the soil.

Page 5 of 512345

©2006 - 2009 The Floating Frog