> over-hyped
For the past 5-6 years or so I've been working extensively with Stripe, Braintree, WePay, and PayPal, on a number of different eCommerce and marketplace platforms. Some supported only one of these gateways, other platforms I've been heavily involved with support each of those 4 gateways in parallel depending on their merchants' needs.
Stripe wins, hands-down, for the best documentation and well-thought-out API architecture. It's not even fair to call it a race, they're so far ahead. Braintree has caught up a fair bit over the years, but they're still nowhere near Stripe's level, and now that they're owned by PayPal I don't really expect them to ever get there. (As an aside, I also had a pretty frustrating experience with Braintree back in the day because they took too long to support card tokenization, and one client had no feasible way to only charge the customer once inventory was secured. Lame customer experience.)
WePay is doing some cool stuff, but, as one example, their ruby SDK gem is a 100-line thin wrapper around the core Net::HTTP library, which means I have to dig pretty heavily into both their documentation and Ruby's various Net::HTTP exceptions to safely handle errors, whereas Stripe has all of this built into their ruby gem out of the box.
My time is limited, and I'd much rather invest it towards designing great customer experiences than reading and understanding lacking documentation. Stripe is the only platform I've seen that gets that their documentation is their product. If the price is I'm on an over-hyped platform, I'm okay with that. :)