Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Payments or orders are not reaching my system (webhooks not working)

Short answer

A webhook is a message another service sends to your app, such as payment done. If your app does not answer quickly with a success code, the sender treats it as failed and retries. Check the sender's delivery log, do not re-take payments, and give your developer the failed event's ID.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Customers paid, but the order in my system still says pending.
  • Subscriptions renewed at the payment provider and not in my app.
  • The provider dashboard shows failed or pending deliveries.
  • It worked before I moved the site, renewed the certificate or changed hosting.
  • Some events arrive late or twice.

Why does this happen?

  1. Your app must answer fast with a success code

    Stripe states that an endpoint must quickly return a 2xx status code before any complex logic. A timeout, a redirect or an error status counts as a failure on the sender's side.

  2. The sender cannot reach your server

    Stripe lists the usual delivery failures: it cannot connect, the address redirects, the endpoint answers with a 4xx or 5xx status, there is a certificate (TLS) error, or the endpoint times out.

  3. The signature check rejects genuine messages

    Senders sign each message and your app verifies it. If the secret was changed or the framework alters the raw request body, every message is rejected, although the sender did nothing wrong.

  4. Failed deliveries are retried for a limited time

    Stripe retries a failed live event for up to three days with exponential back off. After that it is no longer retried automatically, so a long outage leaves gaps that must be filled by hand.

  5. Messages can arrive twice or out of order

    Stripe states that event order is not assured and says the same event may be received more than once. An app that assumes order or single delivery will show wrong states.

What can I do about it today?

  1. Open the sender's delivery logIn the payment or service dashboard, find the webhook or event deliveries page. Note whether events say delivered, pending or failed, and the status shown.
  2. Do not charge customers againIf money was taken but the order is pending, check the provider dashboard first. Taking a second payment makes refunds and disputes.
  3. Keep a list of affected ordersWrite order numbers, times and amounts. This is what lets the gaps be filled safely afterwards.
  4. Do not delete or recreate the webhookA new endpoint gets a new secret and can break what still works. Leave it until your developer has looked.
  5. Send your developer the failed event IDsCopy the event ID and the status shown by the provider for two or three failed events.

When should I bring someone in?

  • Paid orders are not being fulfilled.
  • The provider shows many failed deliveries or says it disabled the endpoint.
  • You recently changed hosting, domain or certificate.

How do I handle it?

  1. Trace one failed event end to endI follow one event from the provider's log through your server to your application, and find where it stops.
  2. Fix the causeReachability, certificate, signature secret, or slow handling: I fix what the evidence shows, and make the endpoint answer first and process after.
  3. Fill the gapsI use the provider's resend or event list to replay missed events safely, and make the handler ignore duplicates.
  4. Reconcile and monitorI compare the provider's records with your orders, then add an alert for failed deliveries.

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 the missed messages be sent again?

For a limited time. Stripe retries live events for up to three days automatically, and lets you resend an event manually from the dashboard for a longer window. Other providers differ, so I check their documentation.

Why did customers still get charged?

The payment happens at the provider. The webhook only tells your app about it, so a failed webhook leaves your system behind, not the payment.

Is this the same as my API returning errors?

No. Webhooks are messages sent to you. If your own backend is failing for your users, see the 500 errors page.

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.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.