You tap send. The balance updates in two seconds. What you don’t see is that four separate systems just confirmed your instruction, identified the receiving bank, exchanged messages, and recorded who owes whom — all before your screen finished refreshing.
The exact route shifts depending on the channel and provider, but understanding the basic stages explains something practical: why a transfer can succeed, stall, reverse, or end up disputed.
Step One: You Create the Payment Instruction
You enter the account number, confirm the beneficiary, and authorise with a PIN, password, token, or biometric check. The app usually shows the beneficiary’s name before final confirmation.
Check that name. A correct account number attached to the wrong expected name is reason enough to stop before confirming.
Step Two: Your Bank Checks the Request
Your bank or payment provider checks whether the account is active, whether funds are sufficient, and whether the transaction passes its security and risk controls. A provider may pause anything that looks unusual — that’s a feature, not a glitch, even when it’s inconvenient.
Step Three: The Message Gets Routed
For most account-based transfers in Nigeria, infrastructure run by the Nigeria Inter-Bank Settlement System (NIBSS) lets financial institutions exchange real-time transfer messages. That message tells the receiving bank a valid instruction has arrived.
You might be using mobile banking, internet banking, USSD, an agent, or an ATM — the interface changes, but the same infrastructure sits behind all of them.
Step Four: The Beneficiary Actually Receives It
The receiving institution validates the message and credits the beneficiary. This is the moment that feels instant to you.
But the money reaching the customer and the final settlement between institutions are two related, separate things. Banks settle their net obligations with each other on scheduled or real-time arrangements, depending on the payment system — which is part of why a transfer can look “done” to you but still be finishing up behind the scenes.
Five Real Reasons a Transfer Sits Pending
- Your bank accepted the request but hasn’t gotten a final response yet
- The receiving bank is temporarily slow or unavailable
- A network or channel timed out after the instruction was already sent
- A risk-control check paused the transaction for review
- Your app simply hasn’t refreshed, even though the status already changed on the backend
Do not send the same amount again unless you’ve actually confirmed the first attempt failed. Duplicate attempts create two successful transfers, not one corrected one.
What to Save the Moment Something Goes Wrong
- Transaction reference or session identifier
- Date and exact time
- Amount
- Sending account or wallet
- Beneficiary name and institution
- Status shown in the app
- Debit alert or receipt
Contact the sending institution through an official channel first — not social media, not a forwarded phone number. Keep account details and reference numbers off public posts entirely.
The One Instruction That Should End Any Call Immediately
Confirm the beneficiary name. Check the amount twice. Use a trusted device. Keep transaction alerts on. And never, ever authorise a payment because someone claiming to be a bank employee tells you to “reverse” a transfer by sending another one — that instruction alone is the scam, every time.
An instant payment feels like one simple action. It’s actually a coordinated handoff between your channel, two financial institutions, and shared payment infrastructure. The reference number and status you barely glance at are exactly what lets anyone trace what really happened, if it ever needs tracing.
