Help for owners
Braintree notifications are not reaching my site or keep failing
Short answer
Braintree posts each notification to your URL and resends it until your server answers with a 2xx within 30 seconds. Sandbox retries hourly for up to 3 hours, production for up to 24 hours. A rejected signature or a slow handler causes failures. The fix is in your site's handler, not in Braintree.
Does this sound like your situation?
- Customers pay but my site never marks the order as paid.
- Subscription renewals happen in Braintree but my system does not update.
- Everything worked in the sandbox and not in production.
- My developer mentions an invalid signature or a timeout.
- A burst of subscriptions renewed on the same day and some were missed.
Why does this happen?
Your handler answered too slowly
Braintree states that a webhook taking longer than 30 seconds to respond is considered a timeout and will be retried. A handler that does heavy work before answering can time out for every notification in a busy period.
Confirmed by developer.paypal.com
The signature check failed
Each notification arrives with two form-encoded values, a signature and a payload, which your code passes to Braintree's parse method. Parsing a notification with an invalid signature raises an exception, and a site that does not handle it returns an error.
Confirmed by developer.paypal.com
Notifications are retried for a limited time
Braintree resends until it gets a 2xx within 30 seconds. In the sandbox it retries hourly for up to 3 hours, and in production for up to 24 hours. A fault that lasts longer than that can lose notifications.
Confirmed by developer.paypal.com
They can arrive out of order
Braintree notes notifications may arrive out of order, so your code should compare the timestamps rather than trust the arrival sequence.
Confirmed by developer.paypal.com
The destination URL has to be valid HTTPS
Braintree requires a valid HTTPS path for the destination URL, and your Control Panel role needs webhook permissions. Many subscriptions renewing the same day can also cause a burst of notifications.
Confirmed by developer.paypal.com
What can I do about it today?
- Check that the URL opens on HTTPSOpen the address your developer set as the destination in a browser. A certificate warning is a problem; a not-found page may be normal for a browser GET.
- List the orders that did not updateCollect order numbers and times for a few missed ones. This lets whoever fixes it find the matching notifications.
- Do not mark orders as paid by hand in bulkCheck each against Braintree first. Doing it from memory risks shipping unpaid goods or refunding twice.
- Ask whether sandbox and live keys are mixedA common cause is the live site using sandbox keys or the other way round. Your developer can check this quickly.
- Ask for failures to be loggedRequest that the site records each notification it receives and the reason for any error, so the next failure is visible.
When should I bring someone in?
- Notifications have been failing for longer than 24 hours, so retries have stopped.
- You cannot tell which orders were paid and which were not.
- Nobody on your side can read the server's logs.
How do I handle it?
- Send a test notification and watch itI trigger a notification from the sandbox, follow it to your server and read what happens at each step.
- Make the handler fast and safeThe handler answers at once, stores the notification, and processes it afterwards, so the 30 second window is never at risk.
- Make repeats harmlessThe same notification can arrive more than once, so each action is written so a repeat does nothing extra.
- Catch up on what was missedI compare Braintree's own records with your orders for the failed period and fix the differences, listing each one for you.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will Braintree keep trying forever?
No. Braintree says production retries run for up to 24 hours and sandbox retries for up to 3 hours.
Is the problem on Braintree's side?
Usually not. The notifications are being sent, and the failure is in how your server receives them.
Can a missed notification be recovered?
Your own records can be compared with what Braintree shows for the period, so the missing updates can be rebuilt. I cannot promise this for notifications whose details are not recorded anywhere.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.