I've had a different experience using their Ruby SDK and have not found it as friendly for developers. Their API is decently documented but their implementation for paying is dependent on redirects and URL callbacks. The ruby SDK provides little more than a wrapper for passing and retrieving JSON. Some may prefer this but I felt that I was reinventing the wheel.

I am staying with them for one project because of some services they have that no one else offers.

I am rooting for WePay but they need to work more on their SDKs to be developer friendly.

I'm curious, what more did you expect? Exactly what wheels are being reinvented here?

Their API is pretty brain dead simple (it is just a matter of passing urls and data around) and the documentation is pretty good once you understand the general concepts.

I've given them a bit of feedback on things in the docs that needed improvement, and they've turned around with fixes within minutes sometimes.

I think that if you give them feedback on their apis mailing list about what you'd like to see added or changed, they'd be more than happy to listen. That is what really encourages me about this company.

After using other SDKs from other companies, I expected more than just JSON returned. There are simple things like raising errors that could be in the SDK. I'm sure it will be there in due time but not everyone has the same experience.

I am rooting for them and I am glad to hear others are having better luck than I was.

I'll add my data point as well. I needed a no-brainer payment system. I didn't even have to set up a server - 5 minutes, done.

I've tried on paypal. I can add a PayPal button to my own page but I didn't have a page for my project this time. I would have had to set it all up (again). No, thanks!