Digital payments have changed how people move money.
You can send money from a phone in seconds.
You can pay a business without carrying cash.
You can buy airtime, pay bills, receive money, transfer funds, and run a business from a mobile device.
But the convenience creates a new problem:
What do you do when the payment does not go as expected?
Maybe your account was debited but the recipient did not receive the money.
Maybe you sent money to the wrong account.
Maybe you paid for something and the merchant says the payment was not received.
Maybe a transaction is showing as pending.
Or perhaps you discover that someone made a transaction you did not authorize.
These situations are different.
Treating every payment problem as simply “a failed transfer” can delay the right response.
The first skill is therefore not knowing a particular banking app.
It is knowing how to diagnose the payment problem and respond correctly.
Nigeria's payment infrastructure continues to evolve. In June 2026, the Central Bank of Nigeria launched Payments System Vision 2028, emphasizing security, inclusion, interoperability, innovation, trust and collaboration.
The more digital payments become part of everyday life, the more important payment literacy becomes.
KEY TAKEAWAYS
By the end of this article, you should know how to:
- Distinguish a failed payment from a pending payment
- Recognize an unauthorized transaction
- Handle money sent to the wrong account
- Respond when an account is debited but the recipient is not credited
- Preserve evidence
- Contact the right institution
- Understand transaction references
- Avoid making the situation worse
- Recognize payment scams
- Escalate unresolved complaints
- Build safer digital-payment habits
- Create a personal payment-response checklist
THE FIRST RULE
When a digital payment goes wrong:
STOP. VERIFY. DOCUMENT. REPORT.
Do not immediately send another payment because someone says the first one failed.
Do not immediately delete the transaction notification.
Do not argue with the recipient before checking your account.
Do not give your PIN or verification code to someone claiming to be customer support.
First establish what actually happened.
DIGITAL PAYMENT PROBLEMS ARE NOT ALL THE SAME
Consider these five situations.
Situation 1 — Failed transaction
You initiate a transfer.
The system says it failed.
You may not have been charged, or the transaction may later be reversed.
Situation 2 — Debited but recipient not credited
Your account shows a debit.
The recipient says nothing arrived.
This requires investigation.
Situation 3 — Pending transaction
The payment has neither clearly succeeded nor clearly failed.
The transaction is still being processed or reconciled.
Situation 4 — Wrong recipient
You intentionally made a payment, but entered the wrong account information.
This is different from fraud.
Situation 5 — Unauthorized transaction
You did not authorize the payment.
This should be treated as a security incident.
These cases may require different actions.
BUILD THE RIGHT MENTAL MODEL
Think of a digital payment as a chain:
YOU
↓
YOUR BANK / PAYMENT PROVIDER
↓
PAYMENT NETWORK
↓
RECIPIENT'S BANK / PROVIDER
↓
RECIPIENT
There may be additional participants depending on the transaction.
A problem at any point can affect what you see.
For example:
YOUR ACCOUNT
↓
DEBITED
↓
PAYMENT PROCESSING
↓
NETWORK / DESTINATION
↓
RECIPIENT
The sender seeing a debit does not automatically mean the recipient has received usable funds.
Likewise, a recipient saying “I haven't received it” does not automatically prove the sender's bank lost the money.
You need transaction evidence.
STEP 1 — CHECK YOUR ACTUAL ACCOUNT
Do not rely only on:
- SMS
- A screenshot
- A notification
- The recipient's statement
- A merchant's verbal claim
Open your official banking or payment application or use the provider's official channel.
Look at the actual transaction history.
Confirm:
- Amount
- Date
- Time
- Transaction status
- Recipient
- Account or wallet information
- Transaction reference
- Debit or credit status
This is your starting evidence.
STEP 2 — FIND THE TRANSACTION REFERENCE
A transaction reference is one of the most useful pieces of information in a payment investigation.
It allows the provider to locate the transaction in its systems.
When reporting a problem, have available:
TRANSACTION DATE
+
TRANSACTION TIME
+
AMOUNT
+
SENDER
+
RECIPIENT
+
TRANSACTION REFERENCE
+
DESCRIPTION OF PROBLEM
Do not assume customer service can investigate a vague statement such as:
“I sent money yesterday and it didn't arrive.”
Give them enough information to locate the exact transaction.
STEP 3 — SAVE THE EVIDENCE
Keep relevant:
- Transaction receipts
- Account statements
- Screenshots
- Reference numbers
- Emails
- SMS notifications
- Merchant receipts
- Chat messages
- Payment confirmations
Do not alter screenshots in a way that removes important information.
For important disputes, preserve the original evidence.
A simple folder can help:
PAYMENT-DISPUTES
└── 2026-09-20_Transaction-Reference
├── Receipt
├── Statement
├── Screenshots
└── Correspondence
This connects directly to the digital file-management system from the previous W3 NOTES article.
FAILED TRANSFER VS DEBITED TRANSFER
These two situations are often confused.
Failed transfer
The system indicates that the transaction did not succeed.
You should check whether:
- The account was actually debited
- The money was reversed
- The transaction remains pending
Debited but not received
Your account shows that money left your account, but the recipient has not received it.
This should be reported to the institution that handled the payment.
Do not automatically send the money again.
WHY YOU SHOULD NOT SEND IT AGAIN IMMEDIATELY
Imagine:
FIRST TRANSFER
↓
STATUS UNCLEAR
↓
YOU SEND AGAIN
↓
FIRST TRANSFER LATER COMPLETES
↓
SECOND TRANSFER ALSO COMPLETES
You may now have paid twice.
Instead:
FIRST TRANSFER
↓
VERIFY STATUS
↓
CONTACT PROVIDER IF NECESSARY
↓
WAIT FOR RESOLUTION
If the payment is genuinely urgent, you can make a decision after understanding the status and the risk of duplication.
WHAT IF THE PAYMENT IS REVERSED?
A reversal generally means the transaction is returned or cancelled rather than completed as originally intended.
Check your account rather than relying on assumptions.
A useful timeline is:
INITIATED
↓
PROCESSING
↓
SUCCESS
or:
INITIATED
↓
PROCESSING
↓
FAILED
↓
REVERSED
The exact status terminology depends on the provider.
WHAT IF THE RECIPIENT SAYS “I DIDN'T RECEIVE IT”?
Ask the recipient to check:
- Correct account
- Correct wallet
- Transaction history
- Pending transactions
- Account balance
- Their provider's notification history
Then compare the details with your own transaction record.
Do not rely on screenshots alone.
A screenshot can show that someone has a receipt.
It does not necessarily prove that the money reached the intended account and remains there.
WRONG ACCOUNT: A DIFFERENT PROBLEM
Suppose you intentionally made a transfer but entered the wrong account number.
That is different from an unauthorized transaction.
You authorized the transfer.
The mistake was in the destination information.
Your first response should be to contact your bank or payment provider through its official support channel as quickly as possible.
Provide:
- Transaction reference
- Amount
- Date
- Time
- Intended recipient
- Incorrect recipient
- Reason for the recovery request
Do not assume that a completed transfer can simply be cancelled.
The ability to recover funds depends on the transaction, the institutions involved, applicable rules, and whether the funds remain recoverable.
DO NOT TRY TO “RECOVER” MONEY THROUGH ANOTHER TRANSFER
A common scam pattern involves someone claiming:
“Your payment failed. Send another payment to this account to reverse it.”
Be careful.
A legitimate institution should not require you to transfer your money to a random account in order to “unlock” or “reverse” another transaction.
Use the provider's official support process.
UNAUTHORIZED TRANSACTION: ACT FAST
An unauthorized transaction is different.
You did not authorize it.
Treat it as a security incident.
Your priorities become:
STOP FURTHER LOSS
↓
SECURE ACCOUNT
↓
REPORT TRANSACTION
↓
PRESERVE EVIDENCE
↓
FOLLOW INVESTIGATION
Contact the bank or payment provider through an official channel.
If you still have access to the account, review recent transactions and security settings.
IF YOU THINK YOUR ACCOUNT IS COMPROMISED
Do not focus only on the single transaction.
Ask:
“How did the attacker obtain access?”
Possible causes can include:
- Stolen credentials
- Phishing
- Malware
- Compromised email
- SIM-related attacks
- Stolen device
- Social engineering
- Unauthorized device access
- Exposed recovery information
The transaction may be the symptom.
The compromised authentication system may be the cause.
CHANGE CREDENTIALS WHEN APPROPRIATE
If your account may have been compromised, use the provider's official security process.
For password-based accounts, change compromised passwords and avoid reusing them elsewhere.
If you suspect someone has access to your account, review:
- Active devices
- Recent sign-ins
- Recovery information
- Authentication methods
- Connected applications
- Transaction history
Google's current account-security guidance similarly recommends changing compromised passwords and reviewing unfamiliar signed-in devices when unauthorized access is suspected.
NEVER SHARE YOUR PIN
Your:
- ATM PIN
- Mobile banking PIN
- App PIN
- Password
- Passkey
- Verification code
should not be handed to someone claiming to be support.
A person calling you does not become trustworthy merely because they know:
- Your name
- Your phone number
- Your bank
- Your recent transaction
- Part of your account information
Scammers can obtain surprisingly convincing information.
NEVER READ OUT A VERIFICATION CODE
A verification code exists to prove something to the service.
If someone asks:
“What code did you just receive?”
stop.
They may be attempting to authenticate themselves using the code sent to you.
Google explicitly warns users never to share verification codes with callers claiming to be Google or account-security personnel.
The same principle should apply broadly to digital financial services.
BE CAREFUL WITH “BANK SUPPORT” ON SOCIAL MEDIA
Someone may post:
“Contact us here for help.”
The account may look official.
Instead of trusting the profile, obtain the institution's official contact information through its website, official app, card, statement, or another trusted source.
Do not send account credentials or sensitive information through an unverified social-media account.
THE URGENCY TRAP
Scammers want you to react before thinking.
Common messages include:
“Your account will be closed today.”
“Your transaction has been flagged.”
“Your money is about to be stolen.”
“Send this code immediately.”
“Transfer the money to this safe account.”
Urgency is not proof of authenticity.
Google's current guidance for account-security scams recommends slowing down, independently checking claims, and not sending money or personal information on the spot.
Use:
STOP
↓
THINK
↓
VERIFY
↓
ACT
AI HAS CHANGED THE SCAM PROBLEM
Modern scams can be more convincing because attackers can use technology to improve:
- Written messages
- Fake websites
- Voice impersonation
- Images
- Social profiles
- Personalized messages
Deloitte's 2026 Nigeria Cybersecurity Outlook identifies AI-powered scams, identity fraud and ransomware among the pressures affecting Nigeria's digital environment.
The practical lesson is:
Do not judge authenticity only by how professional a message looks.
A polished message can still be fraudulent.
WHAT ABOUT OTP AND SMS CODES?
One-time passwords can provide useful additional protection, but they are not magical.
An attacker may attempt to trick you into revealing the code.
They may also use social engineering or other techniques to interfere with account access.
Therefore:
OTP
+
SECURE PASSWORD
+
DEVICE SECURITY
+
ACCOUNT MONITORING
+
USER AWARENESS
is stronger than treating the OTP as an independent guarantee of safety.
Where phishing-resistant methods such as passkeys are available and appropriate, they can reduce exposure to credential-phishing attacks. Google describes passkeys as more resistant to phishing than passwords.
DIGITAL PAYMENT SAFETY STARTS BEFORE THE PAYMENT
Security is not only about what happens after money disappears.
Before sending money:
CHECK THE RECIPIENT
Verify:
- Name
- Account number
- Bank/provider
- Amount
CHECK THE PURPOSE
Ask:
“Why am I sending this money?”
CHECK THE CHANNEL
Are you using the legitimate banking application or website?
CHECK THE REQUEST
Did someone unexpectedly ask you to transfer money?
CHECK THE PRESSURE
Are they trying to make you act immediately?
A SIMPLE PAYMENT PAUSE
Before a large or unusual transfer:
WHO?
↓
WHO AM I PAYING?
WHAT?
↓
WHAT AMOUNT?
WHY?
↓
WHY AM I PAYING?
WHERE?
↓
WHICH ACCOUNT?
HOW?
↓
WHICH PAYMENT CHANNEL?
WHEN?
↓
DOES THIS NEED TO HAPPEN NOW?
This takes seconds.
For high-value transactions, those seconds can matter.
MERCHANT PAYMENT SAFETY
If you operate a business, payment verification is equally important.
A customer may show:
“PAYMENT SUCCESSFUL”
But the merchant should verify the payment through the merchant's actual account or approved payment system.
Do not release valuable goods solely because someone shows a screenshot.
For a business:
CUSTOMER CLAIMS PAYMENT
↓
VERIFY ACTUAL CREDIT
↓
CONFIRM AMOUNT
↓
RELEASE PRODUCT / SERVICE
The exact verification process should depend on the payment channel.
WHAT IF A CUSTOMER SENDS TOO MUCH?
Suppose a customer says:
“I accidentally sent ₦500,000 instead of ₦50,000. Please send ₦450,000 back.”
Do not automatically return money based only on the screenshot.
Verify the original transaction independently.
There may be fraud or a manipulated payment record.
A safer business process is:
CUSTOMER CLAIM
↓
VERIFY YOUR ACCOUNT
↓
CONFIRM ACTUAL CREDIT
↓
DOCUMENT TRANSACTION
↓
HANDLE REFUND THROUGH A TRACEABLE PROCESS
KEEP YOUR TRANSACTION HISTORY
Do not delete financial records simply because the transaction is complete.
For business activity especially, transaction records can help with:
- Accounting
- Reconciliation
- Customer disputes
- Tax records
- Fraud investigations
- Refunds
- Cash-flow tracking
Your payment history is part of your digital financial record.
PAYMENT RECONCILIATION
If you receive many payments, create a simple reconciliation process.
For example:
EXPECTED PAYMENT
↓
ACTUAL PAYMENT
↓
MATCH
↓
RECORD
↓
COMPLETE
For businesses:
ORDER
↓
INVOICE
↓
PAYMENT
↓
TRANSACTION REFERENCE
↓
BANK / PROVIDER RECORD
↓
RECONCILED
This reduces disputes.
DIGITAL PAYMENT FRAUD IS A SYSTEM PROBLEM
It is tempting to think:
“People lose money because they are careless.”
The reality is more complicated.
Payment security involves:
- Users
- Banks
- Fintechs
- Payment processors
- Networks
- Merchants
- Identity systems
- Regulators
- Fraud-monitoring systems
- Device security
Nigeria's CBN has been strengthening payment-system controls and consumer protection. In March 2026, the Bank issued guidance on instant-payment services that included controls such as stronger authentication, lower customer-settable transaction limits, real-time fraud monitoring and restrictions around device linking; the provisions were scheduled to take effect July 1, 2026.
The broader direction is toward making digital payments more secure at the infrastructure level.
THE NUMBERS STILL MATTER
According to NIBSS, reported digital-payment fraud losses in Nigeria fell from ₦52.26 billion in 2024 to ₦25.85 billion in 2025, a 51% decline. NIBSS also said the number of fraud cases had declined over the longer period it examined.
That is useful evidence that fraud controls can have measurable effects.
But it should not be interpreted as:
“Digital payments are now safe.”
Losses still occur.
A decline in reported losses does not eliminate the need for individual security.
KNOW YOUR PROVIDER'S COMPLAINT PROCESS
When a payment problem occurs, use the provider's official complaint channel.
Keep:
- Case number
- Date of complaint
- Customer-service channel
- Name or identifier of the support interaction where available
- Documents submitted
- Provider's response
Do not rely on:
“Someone on the phone said they would fix it.”
Get a traceable complaint or case reference whenever possible.
NIGERIA: KEEP YOUR COMPLAINT DOCUMENTED
The CBN's consumer-protection materials advise consumers to provide the relevant details of a complaint, including what happened, when and where it happened, the financial service involved, the amount involved, and what resolution they are requesting. The CBN has also published guidance on escalating unresolved complaints.
A useful complaint structure is:
WHAT HAPPENED?
WHEN?
HOW MUCH?
WHICH TRANSACTION?
WHAT HAVE I ALREADY DONE?
WHAT DO I WANT RESOLVED?
This is much more effective than writing:
“Please help me. My money is missing.”
KEEP YOUR COMPLAINT FACTUAL
A good complaint does not need anger to be effective.
Write:
On 20 September 2026 at approximately 14:30,
I initiated a transfer of ₦X from Account A
to Account B.
The transaction reference is XXXXX.
My account was debited, but the intended recipient
has not received the funds.
I am requesting investigation and resolution of
the transaction.
Facts are easier to investigate than emotional descriptions.
WHAT IF THE PROVIDER DOES NOT RESOLVE IT?
Follow the institution's escalation procedure.
If you are in Nigeria, the CBN provides consumer-protection and complaint channels for financial-service complaints. The Bank's published consumer guidance also describes escalation when a complaint remains unresolved after the institution's handling process.
Keep the original complaint reference.
Do not restart the entire story every time you contact a new support channel.
Give them the existing case information.
BUILD A PAYMENT EMERGENCY CARD
Create a private note containing the information you need during a payment incident.
Do not store passwords, PINs or one-time codes in it.
Instead store:
BANK / PAYMENT PROVIDER
Official website/app
Official customer-service channel
Fraud-reporting channel
Account identifier
What information to provide
Where transaction references appear
This can reduce panic during an emergency.
YOUR PAYMENT INCIDENT CHECKLIST
If something goes wrong:
1. STOP
Do not make another payment until you understand the first one.
2. VERIFY
Check the actual account or wallet.
3. IDENTIFY
Determine whether it is:
- Failed
- Pending
- Reversed
- Debited but not received
- Wrong recipient
- Unauthorized
4. DOCUMENT
Save:
- Receipt
- Reference
- Date
- Time
- Amount
- Relevant messages
5. SECURE
If unauthorized activity is suspected, secure the account immediately.
6. REPORT
Use the provider's official channel.
7. RECORD
Keep the complaint reference.
8. ESCALATE
Use the appropriate escalation route if the problem remains unresolved.
WHAT NOT TO DO
Do not:
- Share your PIN
- Share your password
- Share an OTP
- Approve an unexpected login prompt
- Install unknown remote-access software
- Transfer money to a “safe account”
- Trust a random support number
- Delete evidence
- Send another payment simply because someone says the first failed
- Assume a screenshot proves payment
- Wait unnecessarily when unauthorized activity is suspected
A BETTER WAY TO THINK ABOUT DIGITAL PAYMENTS
Digital payment literacy is not simply knowing how to press:
SEND
It is understanding the complete transaction lifecycle:
REQUEST
↓
AUTHENTICATE
↓
AUTHORIZE
↓
PROCESS
↓
SETTLE
↓
CONFIRM
↓
RECONCILE
↓
DISPUTE / RECOVER IF NECESSARY
That is a much more useful mental model.
FOR SMALL BUSINESSES
If you receive payments from customers, create a payment-control system.
At minimum:
BEFORE PAYMENT
Confirm:
- Price
- Customer
- Account details
- Payment channel
DURING PAYMENT
Record:
- Transaction reference
- Amount
- Time
AFTER PAYMENT
Verify:
- Actual credit
- Correct amount
- Correct customer
END OF DAY
Reconcile:
SALES
vs.
PAYMENTS RECEIVED
vs.
BANK / WALLET RECORD
This turns payment handling from guesswork into an operational process.
FOR INDIVIDUALS
Your personal system can be simpler:
PAY
↓
VERIFY
↓
SAVE RECORD
↓
MONITOR
For unusual or large transactions:
PAUSE
↓
VERIFY RECIPIENT
↓
VERIFY AMOUNT
↓
VERIFY PURPOSE
↓
SEND
THE BIGGER LESSON
Digital money is still money.
The fact that it moves through:
- A smartphone
- A banking app
- A fintech platform
- A QR code
- A USSD session
- A card
- An online checkout
does not make the underlying value less important.
The interface may look like a simple button.
Behind that button is a complex financial and technological system.
Understanding that system helps you use it more safely.
THE DIGITAL PAYMENT SAFETY MODEL
Remember:
SECURE DEVICE
↓
SECURE ACCOUNT
↓
VERIFY RECIPIENT
↓
VERIFY TRANSACTION
↓
AUTHORIZE CAREFULLY
↓
KEEP EVIDENCE
↓
MONITOR ACCOUNT
↓
REPORT PROBLEMS QUICKLY
This is a practical digital-finance skill.
You do not need to understand every payment protocol to use digital money responsibly.
But you should understand what happens when something goes wrong.
YOUR NEXT STEP
Open your primary banking or payment application.
Find your most recent transactions.
For one transaction, identify:
- The transaction reference
- The exact amount
- The date and time
- The recipient
- The transaction status
- Where you would report it if something went wrong
Then ask yourself:
If an unauthorized transaction appeared in my account right now, would I know exactly what to do?
If the answer is no, create your payment-emergency checklist today.
Digital payment security is not only about preventing fraud.
It is also about being prepared to detect, document, report, and recover from problems when they happen.
Image: EaseBuzz
.png)
No comments:
Post a Comment