Progress has been swift since my last post, beta users can now pay for their invoices via Google Checkout and that order is then processed via Google.
I’m currently mulling over a few problems caused by the fact that when a user comes to Settleup, their “order” is already waiting for them, unlike a more traditional store where they would construct a basket and then pay for it there and then. I need to engineer a robust system whereby users don’t end up quitting half way through Google’s checkout, leaving their invoice in limbo between new, and paid. Depending on how that’s done, there are occasions where a user could end up paying for the invoice twice if it isn’t flagged as soon as they are passed over to Google.
As well as writing the Settleup side of things, I’ve also been implementing some of the missing functionality in Google4R, a Ruby plugin that encapsulates the Google Checkout API, I’ve been working with an old colleague of mine, Doooks, and he has my changes ready to merge with his own and be submitted for inclusion in the main trunk on the project
It all makes for a very interesting set of problems, and I’ll fill you in on the solution when I have implemented it, but that’s going to be at least a week away because I’m on holiday next week.
Also, if I may plug a demo I’ll be giving on one of my older apps, TrafficJammr … I’ll be making a presentation at Barcamp Sheffield, so make sure you say Hi! if you’re going to be there.
Recent Comments