PayFlow Pro down?

[d_host]

Re: PayFlow Pro down?

Is Payflow going the way of Linkpoint now or is it believed this was just a temporary glitch and hopefully somebody did the rug dance ??

Well, calling it "going the way of LinkPoint" after _one_ incident in the last couple of years is hardly fair. LinkPoint has the undisputed reputation for being down on a weekly basis, so Payflow Pro still has a long way to catch up to those standards! :-)

Considering we, as Payflow partners, have yet to receive an official explanation of what happened on the 21st, and the tone of voice of our account rep there, I have a feeling some heads did roll, though.

And for what it's worth - we did not see or hear of any outages yesterday (28th), and have not received any tickets from our clients. If there was an outage that lasted more than a a few minutes I'm sure we would have heard something, considering the number of Payflow clients we have. We had signups and orders placed in our own store during the window someone mentioned that they may have been down, so I have to say this may have been an isolated incident, problems connecting from their location or server, or something else we don't know for lack of more detailed info.

[apanda]

Re: PayFlow Pro down?

I am a little irritated that my new thread about payflow going down on 2/28 got combined with this one. That makes it confusing. This thread was about a different outage last week and it had turned into a discussion about a fallback method. (I guess every time Payflow has a problem, we have to add it to this thread, until it's so long no one can possibly read it all to find what they need to see?)

Back to the 2/28 topic - Just because you didn't receive tickets from your clients doesn't mean it didn't go down. This outage was a little different because there were no failed error messages in Manager. I missed six orders and would have missed them if a loyal customer who thought it was odd that she couldn't place an order had not contacted me. I looked at the basket history and found that they were getting stuck at the OPAY screen. During the same time, customers were placing orders for free items just fine. I also had two orders go through with PayPal Web Accept.

[apanda]

Re: PayFlow Pro down?

I'm not sure what error customers were getting... only that they hit the OPAY screen multiple times. I wonder if this could have been related to the fraud detection service. Who else is using it? It has gone down multiple times since June 2006.

[1st Ergo]

Re: PayFlow Pro down?

I think there are intermittent problems that aren't being reported because people don't know about them. I had a customer call me the other day asking why his card wouldn't process. He uses it all the time on other sites. I am also missing large numbers of baskets. Is there a program that shows when a basket was abandoned?

David

[Leanne]

Re: PayFlow Pro down?

Weiland has a Lost and Found orders module that shows all baskets that have been assigned an order number, whether or not the order was completed. You can't always tell where someone abandoned a basket, but you can figure out what general part of the shopping process they were at when it happened, depending on whether the basket shows tax and shipping, etc.

[UltimateNourishment]

Re: PayFlow Pro down?

I think PayFlow Pro is down again!

[UltimateNourishment]

Re: PayFlow Pro down?

PFP is definately having issues. Every order being placed is getting a 'select failure'. Every order!

Argh.

[ILoveHostasaurus]

Re: PayFlow Pro down?

We've got a customer who's compiled MM4 store just started throwing this error:

Unable to authorize payment: Parameter list format error: name, name = PWD

anyone seen that before?

[Barrett]

Re: PayFlow Pro down?

So where were we and or Miva in coding an automatic fallback solution ???
Pretty common sense imo........

[ILoveHostasaurus]

Re: PayFlow Pro down?

We've got a customer who's compiled MM4 store just started throwing this error:

Unable to authorize payment: Parameter list format error: name, name = PWD

anyone seen that before?

Turns out this error was caused by a bug in the 4.x Payflow mod where it doesn't properly escape the password field which causes passwords with & and = to break the checkout.