Help for owners
Customers paid through Paddle but their accounts do not update
Short answer
Paddle tells your system about payments and subscription changes with webhooks. Paddle treats a delivery as successful only if your server answers with HTTP 200 within five seconds, and otherwise retries. A slow server, a wrong secret key or a signature check that fails leaves customers paid but not updated.
Does this sound like your situation?
- A customer paid and still sees the free plan.
- Cancelled or paused subscriptions still have access.
- Renewals work for some customers and not others.
- The Paddle dashboard shows payments, but my app does not.
- Some customers were updated twice or got two welcome emails.
Why does this happen?
The answer is too slow or is not a 200
Paddle's documentation says to return HTTP 200 within five seconds, before any internal processing. Any other status, or no answer in five seconds, counts as failed. The advice is to queue the event and handle it afterwards.
Confirmed by developer.paddle.com
Retries stop, and the event is marked failed
In the live environment Paddle retries for about two days, up to 60 attempts. The sandbox tries three times within about two minutes. When all attempts are used the notification is marked failed, and it can be redelivered with Paddle's replay feature.
Confirmed by developer.paddle.com
The signature check rejects real events
Paddle signs each notification, and the signature covers the raw request body. Its documentation says not to transform the body, including adding whitespace, before verifying. Each notification destination has its own secret key, so a key from a different destination, or one left from a deleted destination, fails.
Confirmed by developer.paddle.com
The same event arrives more than once
Because of retries, Paddle says the same event can be delivered more than once and recommends using the event ID to skip ones already handled. Without that, customers can get duplicate emails or double changes.
Confirmed by developer.paddle.com
The app listens to the wrong events
Paddle describes subscription.created as the point to save customer and subscription IDs and grant access, and subscription.updated as a catch-all for renewals, upgrades, downgrades, pauses, resumes and cancellations. An app that handles only some of them drifts out of step.
Confirmed by developer.paddle.com
What can I do about it today?
- Make a list of affected customersNote each customer's email, what they paid and what their account shows. Do not promise anyone a date for the fix.
- Reassure and grant access by hand if you canIf your admin screen lets you set a plan manually for a customer who paid, do so. Keep a note of each change, so it can be undone.
- Look at Paddle's notification listIn the Paddle dashboard, find the recent notifications and see which show failed or retrying. Take a screenshot of the status and the response.
- Do not delete or recreate the destinationPaddle generates a new secret for a recreated destination, and the old key will stop matching. Leave that to the developer.
- Do not refund or cancel to force a fixCancelling and re-buying can create duplicates. Wait until the cause is known.
When should I bring someone in?
- Many customers are affected, or renewals are failing.
- Paddle shows failed deliveries and nobody can read the server's answer.
- Customers might have been charged twice or lost access they paid for.
How do I handle it?
- Read the delivery log against the server logFor one failing event I compare what Paddle recorded, status and timing, with what my server received and answered.
- Answer fast, process laterThe endpoint verifies the signature on the raw body, stores the event, returns 200 and does the real work in a background job.
- Make handling safe to repeatEach event ID is recorded, so a retry or a replay cannot grant or cancel twice. Subscription state is updated from the latest event, not from the order of arrival.
- Replay what was missedFailed notifications are redelivered using Paddle's replay feature, and the result is checked customer by customer against the Paddle dashboard before I call it done.
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?
Are the payments lost?
No. The payment is recorded in Paddle. What is out of date is your own system's copy of the customer's status.
Can missed events be sent again?
Paddle's documentation says notifications that failed can be redelivered with its replay notification feature.
Why did it only fail sometimes?
A slow database or a busy server can miss the five-second window on some events only. Paddle then retries, so the problem may look intermittent.
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.