I'd like to see a wiki page about payment gateways in NZ. Chris I see nothing wrong with your posts at all.
I would not feel bad that it went pear shape on your watch. From what you have said you had no proof that it wasn't a good plan other than a gut feeling. I think your job is to sort it out as quickly and painlessly as possible. Your ability to get back on track is what I'd be measuring your performance on. I think you've also done the community a good service by giving us the heads up that: 1. Flo2cash have a 'spike detector' in their system that they clearly haven't made customers fully aware of. 2. We should all be talking to our payment gateway providers in advance is we know of anything that may spike traffic. 3. A site that has a mission critical component such as a payment gateway needs to have a good disaster recovery plan in place so as to NOT miss out on business. Cheers Don Chris Burgess wrote: > On Sep 18, 1:52 pm, "chris burgess" <[EMAIL PROTECTED]> wrote: >> Pricewise, you might look at Web2Pay / Flo2Cash, who I recently set up a >> couple of systems with for a client. They seem very well placed for cost, >> and their support team are quite responsive. >> >> I'd be interested in other peoples experiences with Web2Pay / Flo2Cash >> (sorry, I get confused which is their brand and which the product). Anyone >> else have a report? > > Excuse me! May I withdraw my recommendation that people risk using > Flo2cash please? > > A nonprofit I work with (established user of Flo2Cash before asking me > to help set up a CiviCRM payment processor for them) ran a successful > targetted email campaign to their members yesterday. > > Flo2Cash, incredibly, mistakenly had a set limit of 100 daily > transactions on said client's account. Campaign was a roaring success, > but after the first 100 transactions the payment processor threw its > toys out of the cot and went to sleep. Result: furious client, staring > at the hole where their money stopped mid morning. > > Putting a hold on a sudden spike in transactions, perhaps. But just > failing them? Wow. > > Flo2Cash staff are indeed friendly and helpful in the extreme, but > well-meaning doesn't cut it when you make mistakes like this. My > experience to date had me already asking questions of their > professionality (perhaps detectable in the tone of my post above). I'd > seen bugs in the supplied sample code, erratic checksum failures, > undocumented "product name too long" errors causing transactions to > fail, that sort of thing. Foolishly I thought we'd ironed that all out > in testing. I should have spotted the pattern for what it meant. > > Worst part (for me, anyway) is that, despite my reservations (and > those reported to me by a volunteer developer working on an Ubercart > processor for same charity), I didn't put my foot down and say "look, > these guys can't get it right, let's use someone who we know works". > My job as a consultant is to prevent this crap by refusing to go for > second best. > > Non-profits can be very cost-conscious, but saving pennies on a less > professional service provider rarely pays dividends. (As I type this, > I can see the first line of James's next post in this thread says "you > get what you pay for". Ouch.) > > Ok, rant over, lesson learned. Hope you don't mind me sharing. I'm > still looking for field reports from other Flo2Cash customers :) > --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
