Our current communication is focused on getting the hard facts out to our merchants - we want to be transparent and clear about what is happening and what expectations our merchants should have around this service outage. It's slow going, careful work with many moving pieces, so our intention is not to be uncommunicative, but to provide details as we have them.
I invite you to contact support@recurly.com if you have any questions - I will handle all inquiries personally. We are committed to making this right and helping our merchants in any way possible.
Good luck! This has to be tough (I've seen a fair number of HSM and key management related failures; sucks how security and reliability are sometimes at odds...)
Please put a full postmortem on the Internet (and ideally describe what hardware went wrong AND how you'll prevent it in the future) once you've finished immediate recovery. I'd suggest it come from VP Eng, CEO, or Founder level people.
If you can make a credible case for why this won't recur, it shouldn't have a long-term negative effect on the business. (A vendor who had a problem and learned from it is often safer than a vendor who had no problems and has just bene lucky...)
Thank you for your support! We will absolutely be posting details as they become available - keep an eye on blog.recurly.com, and our existing merchants will be notified via email.
VAT is a tricky area with a lot of special rules - this is why most recurring billing providers don't take it on.
After hearing additional requirements from dmarinoc and a few other merchants located in Spain, we have since implemented a solution for merchants using VAT.
Diego - I'll follow up with you directly about the changes :)
We certainly appreciated the efforts you contributed to the v1 version of our API Python library. As we had mentioned to you in our support exchanges, we realized our old Python library was not up to our standards, and that we had been working on a new client library - because this is such a large project with many working pieces, we were keeping it slightly under wraps to allow for flexibility in the release cycle.
That being said, we know many merchants will opt to stay in v1 of our API for some time, and your client library will be very much appreciated.
well to be honest that client library was written to address the shortcomings of the previous Python library, which didn't support Recurly.js (arguably the best part of Recurly), but the new Python client library does and my library wasn't completely finished yet. Even though I have to move some code on my project over, it frees me from having to finish writing that client library, which is honestly about as interesting as waiting for paint to dry so you can watch it chip. It's don't exactly wake up in the morning and think "I wonder what kind of XML I'll get to parse today".
I'm annoyed that I did a bunch of throwaway work that could have been easily avoided, but the API updates are a significant improvement and they solve a bunch of problems for me that I was previously forced to solve myself (especially the new support for multiple subscriptions), so it all comes out in the wash.
If the charge was $1.00 (the charge formatting was a little unclear), this is likely a typical verification charge used to verify that your credit card information is correct. Most services void these charges as soon as they get a success/decline message from payment gateway processing the transaction, and you should see this charge removed from your statement in about 24 hours.
This charge is vaguely referred to in their payment TOS: http://www.facebook.com/payments_terms/
"If you pay by credit or debit card we may obtain a pre-approval from the issuer of the card for an amount up to the amount of the purchase...", although not clear that this also happens when there is no actual purchase, when the card is just being used as a verification method. Definitely an opportunity for Facebook to clarify the behavior when adding credit card information for different reasons.
Check out http://www.prometheusreg.com/. We moved to Sunnyvale from Minnesota and leased our apartment sight unseen. We later moved to another one of their complexes in San Mateo and they transferred the lease. They offer month-to-month leases, I think they manage a lot of corporate housing.
The apartments are a bit on the pricey side, but they're so nice. Good luck, and welcome to San Francisco!
I am very excited about this bundle. I've previously used Olark at other companies, and it's a great tool. Can't wait to introduce it at my current company!
Our current communication is focused on getting the hard facts out to our merchants - we want to be transparent and clear about what is happening and what expectations our merchants should have around this service outage. It's slow going, careful work with many moving pieces, so our intention is not to be uncommunicative, but to provide details as we have them.
I invite you to contact support@recurly.com if you have any questions - I will handle all inquiries personally. We are committed to making this right and helping our merchants in any way possible.