[2_ghosts]

My checkout experience:

Enabled the button, clicked it, nothing happened. Looked in Firebug at the Network console, saw a failure come back from the 'Pay' step.

Triple-checked my payment info, clicked the button once more. 25-30 seconds later, I got two consecutive "Something went wrong" javascript alerts. A minute or so later, I got two confirmation emails, lacking any useful details. I'm guessing I was charged twice.

Once it is possible to log into the site, I will see what my order status says. Right now /login continues to time-out.

[jefflinwood]

Just did something similar, saw that I was getting an SSL Error in Safari from their JSONP Callback on https://swish.com/swish-backend/..., opened that link in another Safari window and it appeared to go through.

I have one pending charge on my credit card, not sure if anything else will go through, but I did end up getting an order confirmation.

Maybe whatever they're using to route SSL traffic through is falling over?

[Bradosaur]

Mostly what failed was outbound bandwidth. Users weren't getting the JSON response from the payment page, though sometimes the payments went through. Confirmation emails were very reliable, though, (thanks Amazon SES!).