Resolving Failed Wrong and Disputed Payments

Organise evidence, contact the right support team and follow a complaint without assuming a guaranteed reversal.

Part 8 of 10 | Mobile Money and Digital Payments Safety

Learning goals

You will classify a payment problem, create a concise complaint record and plan follow-up. You will distinguish an acknowledgement from a refund and explain why reporting promptly is better than relying on a remembered deadline or another provider's policy.

Before you begin

Allow about an hour and use only the fictional cases in this lesson. Do not file a real complaint for practice. If you are currently dealing with a genuine loss, use verified provider support promptly instead of waiting to finish the course. Keep private account records out of shared worksheets.

Name the problem accurately

A pending payment has not reached a clear final outcome in the information available to you. A failed payment is reported as unsuccessful, but you should still check whether a debit or later correction appears. A completed payment to the wrong recipient differs from a correct payment for goods that were not delivered. An unknown debit differs from a payment you knowingly approved after being deceived.

Write what you observed without assuming its cause. For example: My activity shows a debit; the recipient says no credit has arrived. That is more useful than declaring that the recipient or provider stole the money. Include whether a second attempt was made. A support team needs the sequence to distinguish a delayed credit, duplicate transfer or another issue.

Preserve the original transaction

Do not immediately resend after a timeout. Check your own transaction record and ask the recipient to check theirs through their own account. If the results remain unclear, contact the provider. Record the reference, amount, time and displayed status. Keep original evidence securely, and share only what the verified support process needs.

Avoid editing the only copy of a receipt to add explanations. Keep a separate note of your interpretation. If you redact a copy for sharing, preserve the original privately where appropriate. Do not publish full phone numbers, identity documents or statements in a public complaint. Public exposure does not make the underlying transaction easier to resolve.

Report promptly without assuming reversal

Use the official support route and ask whether the transaction can be investigated, stopped or corrected. Act as soon as you notice the issue. Do not transfer more money to someone claiming that a reversal requires a deposit. For a wrong recipient, avoid demanding that they send a new transfer to an unrelated number; use the provider's supported process.

Provider conditions differ. Wave's Gambia terms restrict cancellation of settled transfers. Afrimoney describes an attempted reversal process with conditions. Neither should be taught as an unconditional recovery promise. This course also found differing complaint timelines between Wave's general complaints page and its Gambia terms, so it does not give a universal deadline or guaranteed resolution time. Ask which current procedure applies to your case.

Build a useful complaint

Start with the issue and requested help, then provide the facts through the verified private channel. A practice message might say: Please investigate a fictional transfer marked pending. I approved one payment, the recipient reports no credit, and I have not repeated it. I can provide the transaction reference securely. Please confirm the case reference and next step.

For a real case, the provider may need identifying and transaction details. Supply them only through its verified process. Do not include your PIN, password or one-time code in a complaint narrative. Ask for a case reference, the expected response process and a way to follow up. Save the date and outcome of each contact.

Follow through to a recorded outcome

An automated acknowledgement means the request was received, not that the payment was reversed. If support says a correction occurred, check the account record and amount. Match the correction to the original issue rather than treating any new credit as resolution. Note any remaining difference and ask for clarification.

If the issue remains unresolved, request the provider's formal escalation route and written outcome. For questions about the relevant Gambian regulatory route, verify current guidance with the Central Bank of The Gambia or the appropriate authority for the issue. This course does not invent a regulator complaint deadline or promise that one body handles every dispute. Suspected theft or threats may also require the appropriate local law-enforcement route; keep your factual record consistent.

Guided exercise

1. Classify these fictional cases: a timeout with an unexplained debit; a completed transfer to the wrong number; and a correct seller payment with no delivery. Write what is known and unknown for each.

2. Choose one case and build a timeline with the attempt, observed status and support contact. Do not invent an outcome.

3. Draft a complaint of five to seven sentences stating the issue, relevant facts and requested help. Replace private identifiers with labels.

4. Add a follow-up log with date, case reference label, response and next action. Distinguish acknowledgement from resolution.

5. Practise checking a fictional correction of GMD 250 against an original disputed GMD 300 debit. Record the GMD 50 difference and ask what explains it.

Knowledge check

1. Does an acknowledgement prove that money was returned?

2. Should you promise a wrong transfer will be reversed?

3. Why distinguish an approved scam payment from an unknown debit?

Answer guide

1. No. Verify the actual account correction and its amount.

2. No. Recovery depends on the facts, provider process and applicable terms.

3. They describe different facts that support needs to investigate accurately.

Completion standard

Correctly classify all cases, produce a credential-free complaint and follow-up log, and identify the incomplete correction. Explain why you will report promptly without assuming a refund or fixed resolution time.

Sources and verification notes

Wave terms for The Gambia. Checked 15 September 2026. Gambia-specific terms include cancellation restrictions. Outcomes depend on the circumstances and applicable terms.

Wave complaints policy. Checked 15 September 2026. General policy. Its timelines differ from the Gambia terms; confirm the applicable process with support.

Africell Afrimoney official FAQs. Checked 15 September 2026. Provider-specific guidance. Conflicting limits appear on this page; confirm current terms directly before transacting.

Central Bank of The Gambia mobile money information. Checked 15 September 2026. Regulatory signpost only; this incomplete page is not treated as a comprehensive current licensing register.