
So we have a CardSave account. They allow a gateway option where customers are redirected to their server with lots of re-assuring WorldPay logos around and I guess most people have used WorldPay at some point and know their card details are not going to be ripped off.
Anyway, since I will be taking names and addresses it makes sense to have SSL certificate so I have upgraded my hosting account to have that and then downloaded and installed EB and the EB CardSave Plugin. I'm getting a time out on cURL because the CardSave system uses a crazy port. Port is closed on firewall and host will not open it on my package. So
1. I can spend £500 a year on a higher package (yeh right!) or
2. Move merchant account elsewhere that doesn't use a daft port - looking forward to that delight as it took an age to set up CardSave as needs company director signatures and all sorts or
3. Move host (I actually like my host but they have cheesed me off with this firewall nonsense - they should be able to open a firewall port specific to my account even on shared hosting)
4. Move to a "gateway" based account. Stripe (Stripe.js) does sound interesting. Would be useful to see a screen shot of how that looks and what I can easily add to that to explain to my "customer" that the information they are submitting is sent directly to Stripe. What other (UK) gateway options do you have? PayPal will rip us off in charges! CardSave is cheap. Will need to weigh up costs of Merchant vs Card Charges as we don't pay % on-cost on Debit cards.
5. Re-write the CardSave Gateway? Probably actually re-write the PayPal one as thats the functionality sought! Done it once before for another piece of software.
6. Shout at CardSave and see why I can't use WorldPay's main payment processor which seems to not be on a port!
Frustrated - as I really liked EB - but this might kill it and we have to return to our old payment system for a while.