5 ms·

I've used Dwolla for my own payments before they decided to focus on merchant accounts. Pretty good experience with them, and I wonder how they compare to Strip

I've used Dwolla for my own payments before they decided to focus on merchant accounts. Pretty good experience with them, and I wonder how they compare to Stripe today. I'm always suspicious of such over-hyped services as Stripe, and wished that there was more of a focus on describing the features and technology rather than trying to make everything into a human interest story. Yeah, the Collisons are interesting and successful guys, no doubt. Is Stripe actually a better service on merit? I really don't know, nor does this article enlighten me on that front. It really gives no basis for answering the question in its headline, other than pointing to the precocious financial success of the founders.

nthj 11y ago
> 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. :)
- zekevermillion 11y ago
  Thanks, they should interview you or someone with your experience actually using the product when writing these articles!
_pius 11y ago
I'm always suspicious of such over-hyped services as Stripe hyped ≠ over-hyped
LukeHoersten 11y ago
Stripe's tech and customer service was unparalleled for the small business I had. Other guys like Braintree were just so far behind. If I hadn't used Stripe, I would have assumed the hype was over-hype as well. I don't think it is though.

nthj 11y ago

> 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. :)

zekevermillion 11y ago
Thanks, they should interview you or someone with your experience actually using the product when writing these articles!

_pius 11y ago

I'm always suspicious of such over-hyped services as Stripe hyped ≠ over-hyped

LukeHoersten 11y ago

Stripe's tech and customer service was unparalleled for the small business I had. Other guys like Braintree were just so far behind. If I hadn't used Stripe, I would have assumed the hype was over-hype as well. I don't think it is though.