Braintree Webhooks Not Firing
Workaround available Web, iOS, Android, Server SDKs Updated November 13, 2026Based on 3 user reportsHow we research
Quick answer
Past-due webhooks fire only on the first failed charge in a billing cycle, and endpoints must return 200 in the matching environment. Verify the URL and sample notifications.
Most likely fix: Verify the endpoint
How to fix it
Try these in order — the most common fix is first.
1. Verify the endpoint
- Control Panel > Settings > Webhooks > Check the destination
- Make sure it is public and returns 200
Did this fix it?2. Send a sample
- Use the sample notification tool and inspect your handler
Did this fix it?3. Use the right event
- Use subscription_charged_unsuccessfully for failed renewals
- Do not expect a second went_past_due in a cycle
Did this fix it?
Symptoms
Your server never receives subscription or dispute webhooks.
Why it happens
- Wrong destination URL or environment
- Handler not returning 200
- Past-due event fires once per cycle
This guide also covers
- braintree webhook not working
- braintree subscription past due webhook
Still not working?
If Braintree keeps failing, you're not alone. See every Braintree problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Braintree errors
- Braintree Processor Declined Error
- Braintree Gateway Rejected Error
- Braintree Fraud Rule Rejecting Good Payments
- Braintree 3D Secure Authentication Failed
- Braintree Payout Delayed or Missing
- Braintree Holding My Funds (Risk Hold or Reserve)
- Braintree Account Suspended or Closed
- Braintree Go Live: Sandbox Works but Production Fails