> You don't have to figure out which webhooks you need or write listeners for each one. The library handles all of that. This follows the approach of libraries like dj-stripe in the Django world (https://dj-stripe.dev/).
I don’t figure out these types of things anymore. I just make sure they work in dev, staging and production.
this doesn't work. Most of people follow the workflow you described and call it a day. The problem comes later when, for example, you realise stripe gives a grace period when payment for a subscription fails but the subscription still shows as active in your backend (by this time bad actors have been abusing your software for months).
With stripe-no-webhooks the default behaviour is that subscriptions get cancelled when payment fails and you can deal with your internal logic by putting it inside onSubscriptionCancelled hook.
There are many of small quirks that can be extremely costly (for example if you offer an AI product) and we take care of this for you
I don’t figure out these types of things anymore. I just make sure they work in dev, staging and production.