I'm 99% sure we're using FPS and not Simple Pay. We're using the Remit gem (tylerhunt-remit on github), and I helped write portions of it. This was a while ba

I'm 99% sure we're using FPS and not Simple Pay. We're using the Remit gem (tylerhunt-remit on github), and I helped write portions of it. This was a while back, before they even announced Simple Pay or broke the API doc up into N separate docs. Man, that's irritating. It just irritates me that pretty much everything has to be done via the API. Like I said, 5-10% of our transactions fail, meaning like 1 or 2 a week. If I could inspect the error and handle it from the console it would be much simpler than writing a ton more code for it. FPS-related code is brittle and takes a long time to test, since there are so many error/failure conditions to account for. Sure, manually handling everything doesn't scale, but I'll deal with that when we're processing 1000s of payments instead of 10s. Plus, I think it's pretty ridiculous that they won't give out the reason why it failed. Sure, I can write some more code to query the transaction status and error messages, but that means more code That's what I've found with FPS. Everything I do requires way more code than seems reasonable. If the PayPal API can do even 1/2 of what it claims and is friendlier than FPS, I would drop FPS like a hot potato.