I built a tool to address a worrying gap in payment integrations: a provider can successfully deliver a webhook to your server while your application still fails to update the order. The important distinction is that an HTTP acknowledgement confirms receipt at the endpoint—not that the payment was verified, recorded, or fulfilled. To make that gap visible and recoverable, treat webhook handling as a durable, idempotent workflow, and verify each payment against the provider’s own contract before granting value.
Why “delivered” does not necessarily mean “payment completed”
A webhook is a message sent from a payment provider to an endpoint on your system. When the endpoint returns the required success response, the provider can consider delivery successful. But your application may still have failed to persist the event, update an order, credit a wallet, or complete another business action.
As an Amazon Associate I earn from qualifying purchases.
Paystack makes that boundary explicit: “A Delivered status means your server returned a successful response to Paystack.” That status describes the server’s response, not the later outcome of your application’s work. Paystack’s dashboard guide explains how to inspect and retry webhook deliveries.
So there are two separate questions to answer: did your endpoint receive and acknowledge the event, and did your application safely apply the payment to the correct order? Logging only one of those stages can leave failures invisible.
#1 Best Overall
- WIFI ENABLED TO CONTROL FROM ANYWHERE – Transform your home into a smart home with the Feit Electric Smart Wi-Fi Plug. Remotely turn on or off lights, fans, coffee makers, or other home appliances from your smartphone or tablet. Works seamlessly with Alexa and Google Home, giving you effortless voice control without needing a separate hub. Manage your devices anytime, whether you’re at home, at work, or traveling.
- SIMPLE SETUP, NO HUB REQUIRED – Enjoy the convenience of smart home automation without extra equipment. The plug connects directly to your 2.4 GHz Wi-Fi network, making installation fast and easy. Plug it in, download the Feit Electric app, follow the simple steps, and your devices are instantly connected. Perfect for beginners or anyone looking to expand their smart home ecosystem with minimal hassle.
- SET YOUR ROUTINE & SAVE ENERGY – Save energy, stay organized, and automate daily routines with customizable schedules and timers. Set your lamps, heaters, or appliances to turn on and off automatically at specific times, ensuring your home is always comfortable and efficient. Ideal for morning routines, evening wind-downs, or holiday lighting, giving you peace of mind and energy savings without constant manual operation.
- ENHANCED SAFETY & CONVENIENCE – Protect your home and appliances with the Feit Electric Smart Plug’s durable design and safety features. Its compact size fits easily into standard indoor outlets without blocking other sockets. With real-time app control and notifications, you can monitor appliance activity and prevent energy waste. Ideal for families, pet owners, or anyone seeking a smarter, safer, and more convenient home setup.
- RELIABLE 2.4GHz WI-FI PERFORMANCE – Designed to work exclusively on 2.4 GHz networks, this smart plug provides stable connectivity for smooth operation of all your devices. Avoid interruptions caused by incompatible networks, ensuring your appliances respond instantly when controlled via the app or voice commands. Perfect for indoor home use, it supports up to 15 amps, handling heavy-duty appliances safely and reliably.
Build the receiver so acknowledgement and processing are separate
A reliable receiver should authenticate the request, durably record enough information to process it, and acknowledge it promptly. Longer work should happen after that request has been accepted, with a separate record of whether processing succeeded.
- Preserve the request as received. Some signature checks depend on the original request bytes. In particular, Paystack documents an HMAC check over the raw event body; JSON middleware that parses and reserializes the body can change those bytes and invalidate the comparison. Paystack’s webhook documentation provides its signature scheme.
- Authenticate with the provider’s documented method. Reject requests that fail verification before they can trigger a value-granting action. Do not assume two providers use the same header, hash, or signing procedure.
- Record an event or transaction key durably. Save enough information to continue processing after the HTTP request ends. A successful response should mean the event was accepted for processing—not that every later business operation has completed.
- Return the required success response promptly. Move slow database work, fulfillment, notifications, or other potentially delayed tasks out of the request path. Track processing failures separately so an acknowledged event does not disappear from operational view.
- Verify the payment before granting value. Check the provider’s transaction status and compare the amount, currency, and transaction reference with the order your system expected. A valid signature establishes that a request came through the provider’s documented mechanism; it does not by itself establish that the payment belongs to a particular order.
- Make the value-granting operation idempotent. Use a unique transaction or event identifier to prevent a repeated delivery from fulfilling the same order or crediting the same wallet twice. Protect the business side effect itself, not just the HTTP endpoint’s receipt log.
This pattern separates receipt, verification, and fulfillment into observable steps. It also gives an operator a clear place to investigate: whether the request failed authentication, was not durably accepted, could not be processed, or did not match an expected transaction.
Rank #2
- equipped with atom n2600 d2700 processor, compatible with many freebsd based router systems, linux distros, or win.os supported, easy configuration and management
- Please note, this is a barebone only. A system memory, a storage drive and an operating system are needed to complete this system
- 13-19 inches 1u, 50w power, with power cord, make sure to use a big brand memory and ssd/hdd with quality assurance
- Designed with console, 2 x usb, 4 x lan, vga, power switch, size at 290 x 180 x 44mm
- There are 2 inside reserved fans on chassis, which could be removed freely or be turned on in a high temperature environment to ensure the best function of the product
Flutterwave and Paystack do not share one webhook contract
Use the documentation for the provider, version, and environment configured in your integration. Even within Flutterwave’s published material, signature instructions differ between the current guide and its versioned v4 guide. The table summarizes what the linked documentation says; these values are provider settings, not guarantees that every event will be retried or recovered automatically.
Recommended Free Tools
| Provider and documentation | Authentication | Acknowledgement and delivery behavior | Recovery guidance |
|---|---|---|---|
| Flutterwave current guide | Compare the configured secret hash with the verif-hash request header. The guide says provider IP addresses are dynamic and recommends signature verification rather than strict IP allowlisting. Flutterwave Webhooks |
Return HTTP 200. The documented request timeout is 60 seconds. When retries are enabled, Flutterwave documents three retries, 30 minutes apart. Flutterwave Webhooks | Verify the transaction through the API; the guide recommends polling pending transactions as a backup and processing events idempotently. Flutterwave Webhooks |
| Flutterwave v4 guide | The versioned v4 guide specifies HMAC-SHA256 in the flutterwave-signature header. This is not the same instruction as the current guide’s verif-hash comparison. Follow the contract for the version actually in use. Flutterwave v4 Webhooks |
Not stated in the linked v4 guide cited here; use the acknowledgement and retry details documented for your active integration version. | Not stated in the linked v4 guide cited here. |
| Paystack | Compute HMAC-SHA512 over the raw event payload and compare it with x-paystack-signature. Paystack Webhooks |
Return HTTP 200 OK. The documented timeout is 30 seconds. In live mode, Paystack retries every three minutes for the first four attempts, then hourly for 72 hours. In test mode, retries are hourly for 10 hours. Paystack Webhooks | Inspect delivery history and manually retry from the dashboard; verify transactions through the API. Paystack says its current webhook events are sent for successful transactions only. Dashboard retries and payment verification. |
Paystack’s documented mobile-money flow gives one example of a provider-specific fallback: if a charge.success event has not arrived, its guide suggests verifying the transaction after 180 seconds. That interval applies to the documented flow; it is not a universal timeout for all Paystack payments. Paystack payment channels
Rank #3
- Shelly Plus 1 PM is a Wi-Fi smart relay switch with 1 channel, up to 16A with power metering that can be used also as a WiFi repeater and Bluetooth gateway. Shelly Plus 1PM can be used to monitor the consumption and take control of home appliances, electric circuits, and office equipment individually.
- Automate electrical appliance and control - With Shelly Plus 1PM you can automate any electrical appliance in your home and control it remotely. Shelly Plus 1PM can control appliances with a large load which makes it perfect for kitchen appliances and domestic systems monitoring and control. You can get precise measurements of the power consumption of each appliance and switch in on/off remotely, no matter where you are.
- Set and be prepared for everything - Reveal the full potential of Shelly Plus 1PM by combining it with other devices from your home network! Set Shelly Plus 1PM to activate custom scenes based on hour, light, or various occurrences. For example, you can set Shelly Door/Window sensor to report a porch door opening and activate Shelly Plus 1PM to turn on the hot tub heaters only in the hours after 8 pm.
- Shelly Customer Service - Shelly is one of the fastest-growing Smart Home brands in the world with devices, providing solutions for the automation of private homes, buildings and businesses. We provide our customers with professional support and a 3 years device warranty.
- Shelly Smart Control App will help you control your Shelly devices remotely and will send notifications for all automated events in your home. You can easily configure devices and manage their settings individually, or you can create personalized scenes by combining Shelly devices to trigger certain actions in your home automation.
Retries help, but they are not a reconciliation plan
Provider retries are finite and differ by provider and environment. They can recover a temporary endpoint outage, but they cannot guarantee that your business records match the final payment state. For example, your endpoint might acknowledge an event and then fail while processing it; a provider may have no reason to resend an event it considers delivered.
- Separate delivery status from processing status. Record whether the provider request was authenticated and accepted, then separately record verification and fulfillment outcomes.
- Use the provider’s recovery tools. Paystack documents delivery history and manual retry from its dashboard. Check the relevant provider dashboard when a payment remains unresolved.
- Reconcile unresolved transactions. Query the provider’s verification API, or poll pending transactions where the provider recommends it. Compare the returned transaction with the expected order before changing its state.
- Make replay safe. Whether an event arrives through an automatic retry, a manual retry, or a reconciliation job, the same transaction must not grant value twice.
Paystack says webhooks are preferred for payment status, while its current webhook events cover successful transactions. That makes a verification path especially important when an order is still pending or the expected success event has not appeared. Paystack payment verification
Rank #4
- Portable 100M/1G Network TAP Appliance for remote capture of data traffic
- Integrated with a Raspberry Pi 4 module (8GB RAM and 64GB Micro SD Card)
- Can be used as a standalone 100M/1G network TAP with the external monitor port
- Dual DC power inputs for enhancing overall system availability
What to establish before relying on Orange Money callbacks
The linked Orange Developer materials confirm an Orange Money payment API and an application process, but they do not establish the Web Payment callback’s signature method, acknowledgement requirements, retry schedule, or reconciliation flow. Those details may depend on the market and API version, so do not copy Flutterwave’s or Paystack’s contract into an Orange integration.
Before implementing callback handling, obtain the payment-specific documentation for the target market and version, then confirm how to authenticate callbacks, acknowledge them, identify duplicate events, and verify or recover a transaction. The available starting points are Orange Money application information and the Orange API portal.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
