JAMB Profile Code — The Candidate-Side Identifier Anchor

The JAMB profile code is the first identifier JAMB issues a candidate against a NIN. Ten alphanumeric characters, delivered by SMS to a single phone number, tied to that number for the whole cycle. It is the entry token the candidate uses to buy an e-PIN, and the surface JAMB uses to authenticate the candidate's identity at the registration boundary between the NIMC database and the JAMB eFacility system.

This article is a reference. The companion how-to that walks the registration sequence end to end is the JAMB registration walkthrough; the companion troubleshooter for the SMS-and-email channel diagnostic when the profile code does not arrive is the profile code not received article. This reference exists because the profile code is one of four candidate-side identifiers that recur across the cluster, and naming the four cleanly in one place lets every other JAMB article point here when the distinction matters.

The four identifiers — profile code, JAMB Registration Number, CAPS Profile, NIN — are the vocabulary every downstream JAMB article assumes the reader holds. The rest of this reference walks each identifier's issuer, format, when it is issued, where it surfaces, and how long it persists.

The article speaks to two readers. The UTME or Direct Entry candidate at the start of the registration cycle, trying to understand what the profile code actually does and how it relates to the e-PIN and the JAMB Registration Number. The parent or guardian of an under-18 candidate, handling the registration logistics on the candidate's behalf and trying to make sense of which identifier matters at which step.

The cluster's three-actor framework sits behind the identifier vocabulary. JAMB is the issuer of every JAMB-side identifier; the candidate holds the identifiers and uses them at each registration surface; the tertiary institution reads only the JAMB Registration Number and the CAPS Profile downstream, never the profile code or the NIN directly.

The statutory frame is the same JAMB Act and UTME Brochure that govern every other operation in the cluster.

The four identifiers map cleanly onto four different roles. The table below is the operational reference: each row names an identifier, its issuer, when it is issued, its format, where it surfaces, and how long it persists.

The four identifiers are not interchangeable. A NIN cannot be used as a JAMB Registration Number at the examination hall; a profile code cannot be used at the CAPS login; a JAMB Registration Number cannot be used as the SMS entry token for a fresh registration cycle. Each identifier sits at a specific surface for a specific purpose; mixing them up is the most common source of candidate-side confusion at JAMB.

The profile-code SMS handshake is the documentary-side bridge between NIMC and JAMB. The candidate sends a NIN to a JAMB shortcode; the shortcode reads the NIN against the NIMC database; if the NIN is active and the bio-data is clean, JAMB issues a profile code and binds it to the sending phone number. The handshake takes a few minutes on a clean SIM and a working network.

The exact SMS format is binding. The shortcode parses the message as NIN followed by a single space and then the 11-digit NIN, with no other characters. Variations the parser rejects:

• Lowercase nin instead of NIN (some sources cite case-insensitivity, but the safe discipline is uppercase).
• Dashes inside the NIN digits (NIN 123-456-789-01).
• Extra spaces between the digits.
• A different word in place of NIN.

A rejection returns a parser error from the shortcode — Wrong Parameter or Error 550/66019 in the most common cases. The fix is to re-send the SMS in the canonical format.

The shortcode binds the issued profile code to the phone number that sent the original SMS. JAMB designed the binding as a fraud-control surface: a profile code that drifted between phone numbers would let a malicious actor capture another candidate's NIN-anchored cycle. The binding is durable through the registration window and beyond — the candidate keeps the registered phone number active through to the end of the CAPS admission cycle.

The SMS to the shortcode is charged at ₦50, deducted from the SIM's airtime balance. JAMB's published recommendation is at least ₦100 airtime on the SIM at the time of sending — the headroom absorbs a single retry where a network failure on the first send would otherwise eat the airtime without delivering the code.

Where the profile-code SMS has been issued but the candidate has lost track of it, the recovery is the RESEND command. Send the single word RESEND (no other parameter, no NIN) from the same phone number that sent the original NIN SMS to 55019 or 66019. The shortcode returns the previously issued profile code at the same ₦50 SMS rate. RESEND does not generate a new code — it re-issues the existing one. A RESEND from a different phone number returns no code; the binding is to the original sender.

Where RESEND returns nothing — the SMS goes out but no reply arrives — the diagnostic shifts from JAMB-side reissue to candidate-side SMS-channel troubleshooting. The profile code not received troubleshooter walks the network-side, SIM-side and shortcode-side diagnostic in detail.

The profile code's operational role is to open the door to the e-PIN purchase. Three downstream surfaces read the profile code:

• The bank counter. Major Nigerian commercial banks vend JAMB e-PINs during the registration window. The candidate presents the profile code (or sends an SMS containing it from the registered phone number) at the JAMB e-PIN counter; the bank reads the code against JAMB's verification surface and vends an e-PIN. The candidate then pays the e-PIN fee (₦7,200 UTME-only, ₦8,700 UTME-with-Mock, ₦5,700 DE in the 2026 cycle).
• The JAMB eFacility portal. The candidate signs in at https://efacility.jamb.gov.ng/, navigates to the e-PIN purchase surface, enters the profile code, and pays through the integrated card-payment channel.
• The accredited CBT centre. The centre operator reads the profile code at the desk, vends the e-PIN, and immediately proceeds to biometric capture against the same code. This is the most common route for candidates who want a one-stop registration.

After the e-PIN purchase and the biometric capture, the JAMB Registration Number takes over as the persistent identifier. The profile code's primary operational use ends at the CBT-centre desk; the code is occasionally re-read at JAMB state-office support, but the registration number is the identifier that surfaces at every subsequent stage of the cycle.

Four candidate-side confusions surface most often at the profile-code stage.

• Confusing the profile code with the NIN — the profile code is JAMB-issued and ten characters; the NIN is NIMC-issued and 11 digits. The profile code cannot be used as an identity document at a bank or at NIS; the NIN cannot be used as an e-PIN entry token at the CBT centre.
• Confusing the profile code with the e-PIN — the profile code is the free SMS entry token; the e-PIN is the paid registration token (₦7,200 to ₦8,700 in 2026). The profile code is the prerequisite for the e-PIN, not a substitute for it.
• Confusing the profile code with the JAMB Registration Number — the profile code is the start-of-cycle identifier; the JAMB Registration Number is the post-biometric persistent identifier. The Registration Number is what the candidate carries to the examination hall, not the profile code.
• Using a relative's phone number for convenience — the profile code binds to the sending phone number for the whole cycle. A profile code generated on a relative's phone leaves the candidate dependent on the relative's number for JAMB notifications, RESEND retrievals, and result-release alerts. The conservative discipline is one phone number per candidate, owned by the candidate, kept active through to November.

The profile code is the entry surface for the cluster. The articles that bear on it most directly:

• How to register for JAMB — the registration hub that walks the profile-code-to-e-PIN-to-CBT-centre sequence.
• JAMB profile code not received — the SMS-and-email channel troubleshooter.
• JAMB eFacility portal reference — the candidate-side portal where the profile code is read at e-PIN purchase.
• JAMB CAPS login walkthrough — the post-result admission portal, where the CAPS Profile takes over from the JAMB Registration Number.
• NIN enrolment walkthrough — the upstream NIMC enrolment that issues the NIN the profile code is read against.

SMS short-code charges (₦50) and airtime guidance (at least ₦100 headroom) reflect telco rates and JAMB published guidance current at the 2026 UTME cycle. Confirm the charge on the SIM's call-data record after sending; rates vary slightly between MTN, Airtel, Glo and 9mobile/T2. The shortcode binding to the sending phone number is fixed at JAMB's framework level and does not change between cycles.