Understanding Card Chargebacks: What Nigerian Online Merchants Should Do

Imagine selling a laptop for ₦450,000 through your online store. The customer pays with a debit card, your payment gateway confirms the transaction, and you dispatch the product. Several days later, you receive a notification that the customer has disputed the payment. The funds may be held or reversed while the transaction is investigated, even though the merchant believes the order was fulfilled.

This is the financial risk associated with a card chargeback. For Nigerian online businesses, understanding chargebacks is essential to protecting revenue, managing customer complaints and maintaining good relationships with payment providers. Paystack, Flutterwave and Monnify provide dispute-handling processes, but merchants need to act quickly and produce evidence relevant to the actual complaint. A successful card payment does not eliminate the possibility of a later dispute, and evidence of receiving payment is not necessarily proof of delivering goods or services.

1. What is a card chargeback?

A chargeback is a reversal of a card transaction through the card-issuing bank and applicable payment-network process after a cardholder disputes the charge. It can result in the disputed funds being debited or withheld from the merchant. A dispute may be legitimate, such as when goods never arrive, or the merchant may have records supporting the transaction and choose to contest it.

The core parties generally include the cardholder, the cardholder's issuing bank, the merchant's acquirer/payment processor and the card scheme such as Visa or Mastercard. The exact decision path and evidence rules depend on the card scheme, reason code, transaction and merchant contract. Mastercard explains that an acquirer provides the merchant with a reason code and deadline for submitting relevant evidence.

2. A chargeback is different from a refund or a failed transfer

For Nigerian merchants, this distinction matters. A customer saying 'I transferred money to the wrong account' is not automatically raising a Visa or Mastercard chargeback. Likewise, a cardholder requesting a refund directly from the store is not necessarily in a formal card dispute. Flutterwave's dispute guidance specifically distinguishes voluntary refunds from chargebacks.

3. Why do customers raise card disputes?

Common reasons include an unrecognised merchant name on the bank statement, a purchase the cardholder says they did not authorise, duplicate charges, goods not delivered, services not provided as promised, disputed subscriptions, a failed or late refund, or product quality complaints. Some disputes stem from fraud; others arise from misunderstanding, weak customer support or poor order records.

For example, a hotel may have processed an approved reservation charge but failed to communicate its cancellation policy clearly. An e-commerce shop may have shipped a product but kept no reliable delivery record. A subscription application may continue billing after the customer believes they cancelled. The reason provided in the dispute notice should drive the evidence response; one generic receipt will not address every complaint.

4. How the chargeback process works

1. The cardholder contacts their issuing bank to question a transaction.
2. The issuing bank evaluates the claim and, where appropriate, initiates a dispute through the relevant card network and acquiring arrangements.
3. The payment provider notifies the merchant and provides a reason, case reference and response deadline.
4. The merchant checks the order and chooses to accept the dispute or contest it with evidence directly addressing the reason.
5. The acquirer or provider passes evidence through the applicable dispute process; the bank or scheme evaluates it under the relevant rules.
6. Depending on the outcome, disputed funds may be restored, remain withheld or be permanently reversed; further stages may sometimes be available.

The provider does not necessarily make the final card-scheme decision. Monnify's knowledge base explains that its role is to submit merchant evidence and that card-scheme rules govern final outcomes. A case marked 'submitted' is not the same as a case marked 'won'.

5. Nigerian merchants must take deadlines seriously

The correct response window is not universal. As of 1 November 2026, Paystack's Nigeria support documentation states that businesses have 16 hours to respond to chargebacks and that an unanswered dispute may be auto-accepted. Its weekend and holiday guidance explains how the business-day clock normally pauses over weekends, while warning that some partners process holiday cases. Merchants should follow the live case countdown rather than calculate their own extension.

Flutterwave's developer guide lists 10 working hours for local disputes and 30 working hours for international disputes. A separate Flutterwave help-centre article states 24 and 48 working hours respectively. Because official pages differ, the merchant must obey the specific live deadline shown in the dashboard or dispute notification and seek written clarification from Flutterwave rather than relying on whichever general article appears more generous.

Monnify's card-dispute guidance instructs merchants to respond before the deadline specified in its notice, recommending action within 24 hours. This is an operational target, not a guarantee that every case permits a full day. Assign an owner to monitor dispute alerts even when the business is closed.

6. What evidence should a Nigerian merchant submit?

Evidence must connect the specific payment, named customer and disputed allegation to a verifiable event. Paystack's chargeback guide recommends clear receipts and relevant transaction, identity and fulfilment details, while advising that informal chat messages alone may not suffice. Mastercard likewise advises merchants to respond to the dispute reason code rather than sending unrelated paperwork.

Evidence acceptance varies by card scheme, reason code and provider. A shipping label proves that a parcel was prepared, not necessarily delivered. A successful payment receipt proves a charge occurred, not necessarily that the service was delivered. A browser IP address alone cannot establish that a particular person authorised a card payment.

7. A practical example: A ₦150,000 disputed order

Suppose a merchant receives a chargeback notification for a ₦150,000 online order, with the reason 'goods not received'. The merchant finds a paid invoice, shipping reference, delivery confirmation signed on the relevant date and customer-support correspondence.

The merchant should confirm these records refer to the same transaction and buyer, check whether the item was indeed delivered to the agreed address, and submit a concise response through the provider dashboard before the deadline. If the order was genuinely never delivered, the merchant should accept the valid claim or follow the provider's permitted resolution method instead of manufacturing evidence.

If the merchant contests and loses, the ₦150,000 may be withheld or deducted according to the provider's process and contract. There may also be a dispute fee, especially for international transactions: Flutterwave currently publishes a $38 or equivalent fee for international chargebacks . The example is illustrative; it does not imply every domestic transaction incurs the same charge.

8. How Paystack, Flutterwave and Monnify handle disputes

Paystack

Paystack notifies merchants through dashboard, email and available dispute webhooks, with periodic reminders. A merchant can accept a valid claim or submit evidence to decline it. The provider recommends maintaining an actively monitored disputes email address and supports dispute-management APIs for suitable integrations. Missing the published Nigeria response window risks automatic acceptance.

Flutterwave

Flutterwave has a Chargebacks section where merchants can review cases, upload supporting files and see a case trail. The provider describes accepting a valid chargeback or contesting it with proof of value. Because its published timeline pages do not completely agree, merchants should prioritise the case-specific deadline and seek guidance promptly. Flutterwave's current documentation also describes a possible hold on disputed amounts.

Monnify

Monnify's 2026 card-dispute guidance describes notification by email and merchant options to accept or contest. It states that no separate penalty fee is charged merely because a card dispute was filed, but an upheld chargeback can debit the merchant wallet and even create a negative balance if the funds were already withdrawn. Its required evidence and exact response deadline are provided in the notice.

9. Accounting for chargebacks and reconciliation

Chargebacks affect accounting records even when the underlying order remains recorded as fulfilled. An application should store the dispute separately from the original successful payment, rather than deleting the original transaction or blindly changing all historical entries to 'failed'. Track the case identifier, original payment, reason, amount, status, fee if any, held balance, responses, outcome and financial adjustment.

A merchant finance ledger should reconcile any provider deduction or refund against the original settlement and the applicable account. For a multi-branch business, retain the originating branch and invoice so that the disputed amount does not become an unexplained shortfall in another unit. For a platform wallet, do not simply claw back customer funds without documented authority and the proper dispute workflow.

10. How merchants can reduce avoidable chargebacks

1. Use a recognisable merchant billing descriptor and include the business name on receipts and order confirmations.
2. Show delivery estimates, cancellation rules, refunds and product specifications before payment.
3. Verify payments server-side and monitor obvious signs of suspicious orders using lawful, proportionate controls.
4. For physical goods, preserve reliable dispatch and proof-of-delivery records; for digital goods, preserve relevant access and usage evidence.
5. Provide accessible customer service and respond to delivery or billing complaints promptly.
6. Send clear subscription reminders and make cancellation practical when required by the offer and applicable law.
7. Monitor Paystack, Flutterwave or Monnify dispute notifications through a shared on-call process with backup personnel.
8. Review recurring dispute reasons monthly and correct the relevant operational cause.

Visa's guidance on first-party misuse emphasises clear billing descriptors, order confirmations, delivery communication and accessible refunds. These practices can reduce avoidable confusion without dismissing legitimate customer rights.

11. Chargeback prevention versus chargeback management

Prevention focuses on avoiding the conditions that generate disputes. Management begins when a dispute has already been raised. Both are necessary. A merchant with excellent customer support may still face stolen-card purchases or fraudulent claims; a merchant that always contests disputes without improving service may repeat the same losses.

A good review measures dispute volume, valid complaints, the reason-code mix, response time, cases won or lost and total financial exposure. Do not invent a universal 'safe chargeback ratio' for all card schemes or merchants. Thresholds and consequences differ by provider and programme. Evaluate repeated problems rather than chasing a single anecdotal outcome.

12. Build a simple chargeback-response playbook

• Within minutes of notification: assign case ownership, record the deadline and identify the original order and customer.
• During investigation: confirm transaction status and whether an earlier refund, reversal or support complaint exists.
• Before responding: assemble concise evidence that directly addresses the stated reason code; remove unrelated personal information.
• On submission: retain the provider acknowledgement, files and timestamps, and monitor requests for follow-up.
• After decision: reconcile debits or credits, resolve any customer issue and record preventive lessons.

For broader guidance on selecting Nigerian providers and integrating secure payment flows, see FlyingEze's article on payment gateway integration and website credibility . A separate comparison of Paystack, Flutterwave and Monnify is already scheduled for 11 November 2026; its public URL should be added only after it is live.

Frequently asked questions

Can a customer reverse a successful card payment after delivery?

A cardholder can raise a dispute after a card transaction is completed. Whether the reversal stands depends on the claim, the relevant scheme rules and the merchant's evidence. Delivery alone does not defeat every possible dispute reason.

How quickly must Paystack merchants respond in Nigeria?

Paystack currently states 16 hours for Nigeria-based businesses, with special weekend and holiday counting guidance. Always check the exact deadline displayed for the case.

Are Flutterwave chargeback deadlines the same as Paystack's?

No. Flutterwave's currently available developer and help-centre pages state different working-hour response periods. Merchants should use the actual case deadline and request clarification immediately if documents conflict.

Is a refund the same thing as a chargeback?

No. A refund is generally initiated by the merchant, while a card chargeback proceeds through the bank and card-dispute system.

Can a merchant win a chargeback with a transaction receipt alone?

Not reliably. A receipt confirms a payment but may not prove delivery, customer authorisation or compliance with cancellation terms. Evidence should address the precise dispute reason.

Conclusion

Card chargebacks are part of accepting online card payments, and Nigerian merchants cannot eliminate every dispute. They can, however, reduce unnecessary losses through accurate order records, clear customer communication, reliable fulfilment evidence and prompt responses.

Know the rules that apply to your payment gateway, act on the case-specific deadline and distinguish real customer complaints from unsupported claims. A structured dispute process protects customers' rights while giving merchants a fair opportunity to defend legitimate transactions.