I've used both extensively and in our mobile apps, we've switched back and forth. Stripe is noticeably easier to implement on mobile (including Apple Pay). Maybe not an order of magnitude easier but close. Part of the reason is that Stripe's documentation is much better.

I'm not saying that's a deal-breaker–and I do think Braintree does have an advantage in some areas–but I'm just attempting to answer your question.

Braintree/PayPal really needs to hire a serious UX/frontend team to clean up their docs and dashboards (monospaced font srsly?).

Throwaway for obvious reasons. We do approx $5MM of annual business through Stripe.

#1 reason is lock-in and momentum. Stripe has, bar none, the WORST support of any company in existence. And they don't care to ever change that, having made noise about it for years, but expending precisely zero effort on that front. We would love to move.

But we stay, because we utilize Stripe's card tokenization in order to "store" repeat customers' payment information without having to deal with PCI-DSS compliance processes. If we moved, all existing customers "stored" payment information would, by necessity, go away.

Not sure about in USA. But in Canada to get a Braintree account is a giant process that takes several weeks and required submitting a ton of stuff, and you need too meet their minimum transaction volume in order to qualify.

That's why I use Stripe.

I've implemented both in a typical SaaS app.

Braintree first, because it was the only option, and then Stripe because we were eager to get away from Braintree.

In short, Braintree was very painful to implement and run, while Stripe has been both easier to implement and operate.

Even with the sunk-cost of a working Braintree implementation it was an easy choice to switch to Stripe.

I was a big fan of Braintree. It got acquired by Paypal. They cause their users pain quite often since they're a dominant company that doesn't have to care:

https://lifehacker.com/5821634/why-you-should-ditch-paypal-a...

That puts Braintree into liability category as Paypal's influence on them increases. Leaves Stripe as safer bet for now if they don't pull stuff like that on customers regularly. If Stripe IPO's, they might turn into villains as well. However, there will be another startup or mid-sized company differentiating on quality of service by then. I'll recommend that one.

Note: If Stripe management is reading, I suggest that they continue to pull less crap than Paypal with better service as a continuing differentiator from this point on. It should always work. Braintree also succeeded that way when competing with payment processors.

Stripe in the UK is 1.4% + 20p which is less than half price. So I was surprised and intrigued to read these comments. Is this an intro offer I wonder?

Because Stripe is not available in my country I am forced to use Braintree. I am waiting Stripe to come in while building my app at the moment.

When I started using Stripe the thing for me was ease of use, it was quick and painless to add to an app, the APIs made sense and were incredibly well documented. They also had a reputation for great customer service (though I've heard this has waned as they grew). I honestly didn't consider Braintree at the time but it was clear from the moment I started researching Stripe that they understood the pain points of payments and were making a product to alleviate them.

I thought the competitor was Adyen.

When I had to make the choice it was simple - with Braintree you needed your own card acquiring agreement (with the bank), with Stripe you didn't. I don't know if this still applies though.

What problems does Braintree solve that Stripe doesn't?

One reason could be that Braintree is less known than Stripe?

In my case: I've never heard of Braintree before this discussion and I was going to implement Stripe for my SaaS without even looking at the existing competitors.