TIRMS in Nigeria: check the number before you trust an SMS OTP
Robase · 2026-10-07
An SMS OTP proves one thing: whoever holds the SIM for that number right now received the message. It does not prove that person is still your customer. In Nigeria a number can be SIM-swapped, churned after a long stretch of inactivity, and reassigned to a new subscriber, and the code will still arrive and verify cleanly.
For a routine login that may be acceptable. For a payout, a new-device login, or a phone number change, it can hand over the account. The Nigerian Communications Commission (NCC) is building a system aimed at this gap: the Telecom Identity Risk Management System (TIRMS).
What TIRMS is
NCC's portal at tirms.ncc.gov.ng describes TIRMS as a centralised framework, managed by NCC, "for managing, verifying, and sharing phone number data, with a focus on reassigned numbers." (NCC documents also use the longer name Telecommunications Identity Risk Management System. It is the same system.)
NCC's report of the TIRMS stakeholders' forum (dated May 12, 2026) goes further. It describes TIRMS as a regulatory-backed data-sharing platform for real-time verification of mobile number status, covering the full life of a number: active use, dormancy, recycling, and reassignment. The risks it names are recycled, churned, swapped, barred, and blacklisted numbers (MSISDNs).
The same report lists rule changes NCC proposed alongside it: operators would notify subscribers at least 14 days before a line is churned, and submit churned numbers to TIRMS within seven days of the churn. Those were consultation-stage proposals, so check NCC for the final business rules.
When it goes live
NCC's board said in a communiqué after its 110th meeting, held on 9 September 2026, that TIRMS and its business rules are scheduled to go live in October 2026. That was reported by Nigeria Communications Week and Technext on 14 September 2026.
A schedule is not a launch. Check the TIRMS portal for current status before you plan a release around it.
Who can get access
Not everyone. The public sources describe a gated system:
- NCC's portal says TIRMS is designed for "telecom operators, service providers, and other approved entities," and offers separate onboarding for telecom operators and for organisations or companies.
- NCC's forum report describes verification "by regulators and licensed entities."
- Technext describes the main aim as giving banks up-to-date number status, with banks and service providers checking a number in real time before granting access.
- On cost, the portal FAQ says fees depend on the selected plan and usage, and to contact NCC for pricing.
The public pages do not spell out the eligibility criteria, the approval steps, or whether a given fintech licence qualifies. Ask NCC through the portal, and do not assume approval.
What the check tells you
From NCC's public portal page, TIRMS offers:
- Real-time phone number verification through API integration.
- Number status updates: alerts when a number you have subscribed to changes status, for example becoming inactive, reassigned, or deactivated.
- Status management for operators: operators upload and maintain reassigned numbers.
The portal's illustration shows example statuses such as Normal, Swapped, Churned, and Blacklisted. Technext describes knowing whether a number is active, swapped or disconnected, reassigned, or flagged for suspicious activity.
NCC links API documentation from the portal (doc.tirms.ncc.gov.ng). This post does not reproduce endpoint names, request fields, or response codes. Take those from NCC once you are onboarded.
Where a number check fits in an OTP flow
First, the plain disclaimer: Robase does not run TIRMS, SIM-swap, or number-reassignment checks. Robase sends SMS OTP, WhatsApp OTP, and transactional SMS. Any TIRMS lookup in the flow below is a separate call your backend makes to NCC under your own access.
The pattern is simple: check the number before you send the code, and only for actions where a hijacked number would hurt.
- The user starts a high-risk action.
- Your backend checks the number's status with TIRMS.
- If the status is clean, send the OTP and verify it as usual.
- If the number is flagged, or the check fails or times out, do not rely on the SMS OTP alone. Route the user to a step-up path (below).
- Store the check result next to the OTP record so support and fraud teams can see why a request was held.
Where to apply it:
| Action | Check before the OTP? | If the number is flagged | | ------------------------- | -------------------------------- | ------------------------------------- | | Login on a known device | Optional | Step up | | Login on a new device | Yes | Step up, notify existing sessions | | Payout or new beneficiary | Yes | Hold, step up | | Phone number change | Yes, on the old and new number | Cooling-off period, confirm elsewhere | | PIN or password reset | Yes | Step up | | Signup | Useful to catch recycled numbers | Ask for another number or more proof |
Decide your failure policy up front: for example, fail closed (hold) for payouts and number changes, and fail open (continue with the OTP) for low-risk logins. If your access includes status-update alerts, subscribe high-value accounts so a status change can trigger a hold before the next payout request.
Fallbacks for high-risk actions
When the check flags a problem, or you do not have TIRMS access yet:
- Step up with a second factor that is not tied to the SIM. An authenticator app, a passkey, or a transaction PIN still works after a SIM swap.
- Cooling-off period after a number change. Hold payouts and beneficiary changes for a window your risk team sets, and notify the user on every other channel you have.
- WhatsApp OTP as an additional channel. Robase can deliver OTP over WhatsApp, or one code over SMS and WhatsApp together in
bothmode. WhatsApp on Robase is OTP only, and a failed WhatsApp leg is refunded and reported failed, never silently re-sent as SMS. A WhatsApp account is also tied to a phone number, so treat it as a second delivery path, not an independent identity check. See the WhatsApp OTP API Nigeria guide. - Email confirmation. Send a confirm-or-cancel link to the verified email on file, through your own email provider.
- In-app approval. Ask the user to approve the action from a device that is already signed in and trusted.
Delivery problems are a different problem
TIRMS answers "is this still the right person's number?" It does not explain an OTP that shows sent but never arrives. In Nigeria that is often a Sender ID or DND routing issue. See Nigeria SMS Sender ID for OTP for that side.
Get the OTP side right
Number checks decide whether to send a code. Robase handles sending and verifying it: POST /v1/otp/send and POST /v1/otp/verify, on prepaid credits (1 credit = ₦6). A Nigerian SMS OTP starts at 1 credit (₦6), and a Nigerian WhatsApp OTP is 4 credits (₦24); live rates per network are on Pricing. Creating an account is free, and your first successful top-up adds bonus credits, once per account.
Start with the SMS OTP API Nigeria guide, then wire your TIRMS check in front of the high-risk actions.