Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My site is not getting Flutterwave payment notifications

Short answer

Flutterwave sends a POST to your endpoint and treats anything other than a 200 response as a failure, including redirects. Requests time out after 60 seconds, and retries must be enabled in the Dashboard. If the secret hash header does not match, your own code may be discarding genuine events.

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

Does this sound like your situation?

  • The Flutterwave Dashboard shows successful payments, but my site has no record.
  • Orders only update when I confirm them by hand.
  • It worked at launch and stopped after a server or domain change.
  • Some events arrive and others do not.
  • The same payment sometimes updates the order twice.

Why does this happen?

  1. Only a 200 counts as received

    Flutterwave says your endpoint must return a 200 status to acknowledge a webhook, and any other code, including a redirect, counts as a failure. A webhook URL that redirects to another address, for example from http to https, fails.

  2. The secret hash does not match

    Flutterwave puts your secret hash in a header called verif-hash and says to discard requests where it is missing or different. If the value in the Dashboard and on your server differ, your own code rejects real events.

  3. Your site is too slow to answer

    Flutterwave says requests time out after 60 seconds. Doing the order work before answering can exceed that. Long jobs should be handed to a queue.

  4. Retries are limited or off

    Flutterwave says retries are enabled in the Dashboard and describes three retries, thirty minutes apart. After that an event is not resent automatically.

  5. The same event can arrive more than once

    Flutterwave says the same event may be delivered more than once and processing should be idempotent. Without that, a retry creates a second order or a second email.

What can I do about it today?

  1. Look at the webhook settingsIn the Flutterwave Dashboard, check that the URL is the address your site really uses, with the right protocol and no redirect.
  2. Check retries are onIf they are off, ask whoever manages the account to enable them.
  3. Compare the secret hashDo not paste it into emails or chats. Ask your developer to confirm that both sides hold the same value.
  4. List payments your site missedCompare successful Dashboard transactions with your orders for the last days.
  5. Confirm missed payments by handFulfil each missed order once, and note that you did.
  6. Do not publish the secret hashTreat it like a password.

When should I bring someone in?

  • The webhook URL looks right but nothing arrives.
  • The endpoint is behind a firewall, proxy or a security plugin you did not set up.
  • Missed payments recur and you cannot list which ones.

How do I handle it?

  1. Check the endpoint from outsideI test whether the public URL answers with 200 and no redirect, and look at server logs for requests from Flutterwave.
  2. Check the verification stepI confirm the header check works with the real secret and that the code does not reject genuine events.
  3. Answer quickly and process laterThe endpoint acknowledges receipt and passes the work to a queue, so the 60 second limit is not at risk.
  4. Make processing safe to repeatEach event is stored by a unique key, and duplicates are skipped.
  5. Add a safety netA scheduled check re-verifies pending transactions so a missed webhook cannot lose an order.

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?

What response does Flutterwave expect?

A 200 HTTP status. Flutterwave says any other code, including 3xx, counts as a failure, and the response body is ignored.

How many times does it retry?

Flutterwave describes three retries, thirty minutes apart, when retries are enabled in the Dashboard.

Should I allow only Flutterwave IP addresses?

Flutterwave says its IP addresses can change and does not recommend IP whitelisting. It recommends the secret hash instead.

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.

Next step

Want this off your desk?

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