You can enable all webhooks for future-features compatibility.
Those that are handled today are all these:
- charge
- checkout.session
- dispute
- invoice
- payment intent
- source
- subscription
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Can you be more specific as to what those errors were and what webhooks were causing them? Webhooks we don't utilize are just simply rejected, but still response with a 200 response code so they shouldn't error.I recently used Stripe for another platform (not CB) and setup more Events than needed. Unfortunately, that created errors and those extra events kept trying to connect to a server that was not responding to those events. I would be inclined to just use the ones enabled, unless CB had a sort of "catch all" so as to not generate repeating errors.
Please Log in or Create an account to join the conversation.
You need to return anything between a HTTP 200 to 299 for the webhook to be considered successfully delivered.
Please Log in or Create an account to join the conversation.