Paddle Webhook Not Firing or Signature Failing

How to fix it

Try these in order — the most common fix is first.

1. 1. Use the raw body

   Copy steps
   1. Verify against the unmodified request bytes
   2. Disable body-parsing middleware on this route
   Did this fix it? Yes No

2. 2. Check the secret

   Copy steps
   1. Developer Tools > Notifications > your destination > Secret key
   2. Make sure the environment variable matches
   Did this fix it? Yes No

3. 3. Check header scheme

   Copy steps
   1. Billing sends Paddle-Signature with ts and h1
   2. Use the official SDK verification helper
   Did this fix it? Yes No

4. 4. Inspect delivery logs

   Copy steps
   1. Open the notification's logs in the dashboard
   2. Return 200 quickly; Paddle retries with backoff
   Did this fix it? Yes No

Symptoms

Your endpoint gets nothing, or the Paddle-Signature check fails.

Why it happens

• Verifying parsed JSON instead of the raw body
• Wrong endpoint secret key
• Paddle Classic p_signature code used with Paddle Billing
• Endpoint returns errors or times out
• Notification destination inactive

This guide also covers

• paddle webhook not firing
• paddle webhook signature
• paddle webhook not received

Other Paddle errors

• What Is the Paddle.net Charge on My Card Statement?
• Paddle Refund Request: How to Get Your Money Back
• How to Cancel a Subscription Purchased via Paddle
• Paddle Payout Delayed or Missing
• Paddle Account Verification and Domain Approval Rejected
• Paddle Checkout Not Loading
• Paddle Account Closed and Funds Held
• Paddle Support Not Responding