Help for owners
Flutterwave payments stay pending and my orders do not confirm
Short answer
Flutterwave says you should verify a payment with it before giving the customer value, and that some payments finish later, such as mobile money. Check status, reference, currency and amount through its verify endpoint, and run a periodic check on pending transactions instead of trusting a single redirect.
Does this sound like your situation?
- The customer paid, but my order still says awaiting payment.
- The transaction is pending in my Flutterwave Dashboard and nothing changes.
- Some customers get confirmed and others, paying the same way, do not.
- Customers write to say they were charged but got no access or goods.
- I have to confirm orders by hand after checking the Dashboard.
Why does this happen?
Some payments finish later
Flutterwave says webhooks are most useful for asynchronous events, such as mobile money payments, recurring charges and pending payments that later succeed. A payment that is pending when the customer returns can be successful minutes later.
The site trusts the return page
A customer can close the tab before returning to your site. Flutterwave says to verify with its API before giving value, so a flow that depends only on the redirect leaves paid orders stuck.
The check is incomplete
Flutterwave says to verify that the reference matches, the status is successful, the currency is correct and the amount is at least what you expect. A check that skips one of these either rejects good payments or accepts bad ones.
The webhook never arrived or failed
Flutterwave says that if your endpoint fails you may never learn about some payments, and recommends a background job that rechecks pending transactions until they reach a final status.
The wrong transaction ID is used
The verify call needs the transaction ID, which Flutterwave says is in the create response or the webhook payload. A mix-up with your own order reference returns a not-found result.
What can I do about it today?
- Do not hand over goods on a pending statusWait until the transaction shows successful in your Dashboard, or ask the customer for the transaction reference.
- List the stuck ordersWrite down order number, amount, time and Flutterwave reference for each, so they can be checked one by one.
- Compare with the DashboardCheck each reference in the Flutterwave Dashboard and mark the ones that show successful.
- Confirm manually and keep a noteFor the successful ones, fulfil the order by hand and record that you did, so nothing is fulfilled twice.
- Tell waiting customers honestlyA short message that the payment is being checked is better than silence.
- Ask for the confirmation logic to be reviewedDo not edit payment code yourself. Pass the list of stuck orders to whoever maintains the site.
When should I bring someone in?
- More than a few orders get stuck, or it repeats weekly.
- You cannot tell which orders were fulfilled twice.
- Your site only reads the redirect and has no background check of pending payments.
How do I handle it?
- Trace one stuck orderI follow a pending payment from checkout through the verify call and the webhook to your order record.
- Add a full verification stepBefore an order is marked paid, I check reference, status, currency and amount against your own record.
- Add a recheck job for pending paymentsA scheduled job re-verifies pending transactions until they are final, so late successes are not lost.
- Make confirmation safe to repeatEach transaction is recorded once, so a repeated webhook or recheck cannot fulfil an order twice.
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?
Is a pending payment lost?
Not necessarily. Flutterwave describes pending payments that later succeed, so check the final status before you refuse or fulfil.
What must I verify before giving value?
Flutterwave lists: the reference matches, the status is successful, the currency matches, and the amount is at least what you expect.
What if the customer overpaid?
Flutterwave says that if the customer paid more, you can deliver value and refund the difference.
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.