Braintree Webhooks Not Firing

Share
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. 1. Verify the endpoint

    1. Control Panel > Settings > Webhooks > Check the destination
    2. Make sure it is public and returns 200
    Did this fix it?
  2. 2. Send a sample

    1. Use the sample notification tool and inspect your handler
    Did this fix it?
  3. 3. Use the right event

    1. Use subscription_charged_unsuccessfully for failed renewals
    2. 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 us
Fixed it? Share this guide

Other Braintree errors

All 11 Braintree errors and fixes →