Stupid Web Payment Systems
by Kieran- Published:May 16th, 2008
- Comments:No Comment
- Category:Pages
I have a serious hate towards web payment systems that fail to load on the final booking page. It’s happened to me before, then I’ve ended up making two payments. Tonight I booked our boat trip back home for when I finish university only to find the final page didn’t load up. After waiting for quite a while it was obvious nothing was going to happen, so I just closed the page. I then checked my e-mails to see if I had got a confirmation and waited a while to make sure the mail server retrieved everything that was most up-to-date and nothing came through. Knowing it hadn’t confirmed it I re-booked the trip (they’re not cheap either), which went very smoothly and I was presented with the "success" page for the payment. I then check my e-mails to find two confirmations, one for the previous attempt, and one for the one that worked without a hitch.
I understand what it’s like to code web systems, I’ve had to do it before, but there needs to be something more rock-solid in there checking against pages which don’t load. Otherwise, customers have to look at it, know it didn’t complete successfully and either phone up the company they’re dealing with the next day, or phone their bank to see if any charges have been made. It all causes unnecessary hassle. Perhaps the web systems should notice payments made with the same details and give the user a warning that a booking under the same name / card has been made in that evening?
Either way, we’re going to have to phone up on a high-tariff line just to cancel a booking which their system screwed up. These things annoy the crap out of me.

