[binwiederhier]

I wholeheartedly disagree. I think the Stripe docs and developer experience is one of the greatest, if not the greatest, I've ever seen.

It has great user docs, API docs, developer centric UI elements like copy pastable IDs, webhook event browser, time travel features, test mode (!!), and you can even look at the exact API calls that the stripe UI itself is making. I've brought it up to many colleagues are awesome the docs and experience is...

IMHO, for most things, the data model is straight forward and well explained. Of course there are complicated topics and quirks, but that's just because payments is not easy in general..

I'm clearly a Stripe fanboy, but I am not affiliated in any way.

[chucky123]

Stripe undoubtly has great docs. The problem is:

- Them adding a ton of products that are automatically integrated/opted-in their default payments stack

- This has massively increases the api surface, and the complexity of integrating stripe has gone up.

- And to top it off, they charge for every single "feature" that they automatically added in their payments stack.

[jinushaun]

I agree. I think stripe is complicated because accepting payments is complicated. It’s easy to start a new services that only support the 80% of use cases. Especially if you don’t have to consider fraud or regulatory requirements. But that remaining 20% is what kills your simplicity.