Bank USSD can fail because of weak signal, an unregistered SIM, a changed code, insufficient airtime, a timed-out session, a phone setting or temporary bank maintenance. This guide helps you separate these causes without repeatedly authorizing a transaction. It explains what Invalid MMI Code, Connection Problem, Session Expired and Service Unavailable messages usually mean, then gives safe checks for each
Start with your bank USSD code, then troubleshoot signal, SIM, menu and bank availability.
What to dial first
| Need | Code or route | Use it for |
|---|---|---|
| Access Bank | *901# | Test official bank menu |
| GTBank | *737# | Test official bank menu |
| First Bank | *894# | Test official bank menu |
| UBA | *919# | Test official bank menu |
| Zenith Bank | *966# | Test official bank menu |
| Fidelity Bank | *770# | Test official bank menu |
| Wema Bank / ALAT | *945# | Test official bank menu |
| Sterling Bank | *822# | Test official bank menu |
| Stanbic IBTC | *909# | Test official bank menu |
| Ecobank Nigeria | *326# | Test official bank menu |
| Polaris Bank | *833# | Test official bank menu |
| Keystone Bank | *7111# | Test official bank menu |
| ProvidusUnity Bank | Official website, app or support | Current USSD route is not publicly confirmed |
| Jaiz Bank | *773# | Test official bank menu |
| FCMB | *329# | Test official bank menu |
| Union Bank | *826# | Test official bank menu |
Step-by-step
- Confirm the code is correct.
- Dial it from the registered SIM.
- Press call and wait for the menu.
- If it fails, move to a stronger signal area.
- Restart the phone if MMI errors continue.
- Contact bank support if the official code still fails.
Expected result
A working session should open the bank menu. If money was involved, you should get a receipt or alert.
Alternatives
Use bank app, ATM, branch or customer care while USSD is down.
Common errors and fixes
- Invalid MMI: check code/network.
- Session timeout: retry once carefully.
- Debited after failure: stop and report.
Do not accept USSD reset help from strangers asking for PIN or OTP.
Fast troubleshooting answer
Bank USSD may fail because of poor network signal, wrong short code, session timeout, inactive bank USSD profile, SIM registration issues, insufficient airtime for session charges or temporary bank downtime. Start with signal, code and registration checks before contacting official support.
Why a USSD session can fail
USSD depends on your phone, SIM, mobile network, bank switch and sometimes session billing. If one part is weak, the menu may not load or may show an error. That does not always mean your bank account has a problem.
People often see messages like invalid MMI code, session expired, request failed or service unavailable. The wording can differ by phone and network. The safest response is to troubleshoot calmly instead of dialing random codes from strangers.
First checks before you try again
Confirm that you are using the bank official code. If your bank merged, changed branding or updated its menu, old codes from search results may be wrong. Check the bank website, app, branch or profile in our USSD Finder.
Make sure the SIM in the phone is the one linked to the account. Also check signal strength and whether you can make a normal call. If your SIM has no service suddenly, treat it as a possible network or SIM issue and contact your provider.
Safe fixes to try in order
These checks solve many ordinary USSD problems without risking your private information.
- Move to a place with better network signal.
- Confirm the bank code from an official source.
- Restart the phone if the dialer keeps showing MMI errors.
- Try again after a few minutes if the session times out.
- Check whether your registered SIM is active and inserted correctly.
- Contact your bank official support if the code still fails.
- Do not share PIN, OTP, BVN, NIN or card PIN with anyone who claims to reset USSD for you.
If a failed USSD transfer debits your account, stop troubleshooting the code and start documenting the transaction. Save the debit alert and report through your bank dispute channel.
Common errors and what they may mean
| Message or symptom | Possible cause | What to try | When to escalate |
|---|---|---|---|
| Invalid MMI code | Dialer, network or wrong code issue | Check code and restart phone | If official code still fails |
| Session expired | Delay or weak signal | Start again and move carefully | If repeated on many attempts |
| Service unavailable | Bank or network downtime | Wait and retry later | If urgent payment is affected |
| Debit without value | Failed transaction after authorization | Save evidence | Report to bank immediately |
Three real troubleshooting examples
The following examples explain three real troubleshooting examples and show how the guidance applies in different situations.
1. Weak signal in a shop
A customer tries to transfer in a shop with poor signal. The session expires twice. Moving outside before trying again may fix the issue, but the customer should not keep entering PIN repeatedly if a debit occurs.
2. Wrong code from old memory
A user remembers an old code but the bank menu has changed. Checking the official bank website or our updated bank profile helps avoid repeated failed attempts.
3. Unregistered SIM after phone change
A customer inserts a different SIM and expects bank USSD to work. Many banks require the phone number linked to the account, so the user may need official bank support.
Avoid fake reset helpers
Scammers use USSD failure as an opening. They may say your profile is blocked and ask for your PIN, OTP or card number. Do not cooperate. A real support route should not require your full confidential details.
If you suspect your SIM has been swapped or your phone stolen, move to emergency protection steps instead of normal troubleshooting. Use Emergency Help for stolen phone or SIM swap concerns.
USSD failure FAQs
The following examples explain uSSD failure FAQs and show how the guidance applies in different situations.
Does invalid MMI code mean my bank blocked me?
Not always. It can be a phone, network or code-format problem. Confirm the official code and network signal first.
Can I use another phone?
You can dial from another phone only if your registered SIM is in that phone and the bank allows the service.
Why did I get debited after a failed session?
Some failures happen after authorization. Save the reference and report through your bank official dispute channel.
Should I keep trying until it works?
No. Repeated attempts can create confusion. If money is involved or errors repeat, pause and document.
Troubleshoot calmly and protect your PIN
Most USSD issues are ordinary network, code or session problems. The important thing is not to turn a small error into a security risk by following fake reset instructions.
Use the USSD Finder to confirm bank profiles, and report outdated codes through Support so we can review them.
When troubleshooting becomes a complaint
If the code repeatedly fails or a session deducts money, stop testing and document the result. The CBN complaints process explains why the bank should receive the first formal report and why its reference matters.
Verification record
- Last fact-check
- July 31, 2026
- Method
- Official provider or regulator sources reviewed where available; live menus control account-specific actions.
- Reviewed by
- Nigeria USSD Codes Editorial Team
Primary official sources:
Article note
Last reviewed: July 31, 2026. This independent guide is informational and does not replace instructions from your bank, telecom provider, regulator, or service provider. Verify sensitive actions through an official channel before sending money or sharing information.
Nigeria USSD Codes Editorial Team
Nigeria USSD CodesThe Nigeria USSD Codes Editorial Team researches, reviews and maintains practical guides using official provider and regulator sources where available. Corrections are checked before publication, and sensitive actions are directed back to the responsible provider.