How to Update BVN Details in Nigeria (2026)

Three BVN fields can be modified after enrolment: the name on the record, the date of birth, and the BVN-linked phone number. Each modification goes through the same physical channel — the bank counter — but each one carries its own documentary load and its own NIBSS review profile. A reader who walks in needing all three changed on a single visit will not leave with all three done; the chains assemble at different speeds and the bank's KYC desk processes each as a separate submission.

The framing that makes this batch coherent is the three-actor architecture you have already met if you have read earlier BVN articles. The bank is the counter; NIBSS holds the underlying record; CBN sets the framework that governs both.

What you do as a customer is gather the right paperwork for the field you are changing and stand in front of the bank's KYC desk with it. What the bank does is fill the BVN Linking and Correction Form on your behalf and submit the request to NIBSS. What NIBSS does is review, register, and propagate. You only ever stand at one counter.

The three sections below summarise each modification. The deeper walkthroughs sit in the dedicated articles linked at the end of each section. Treat this hub article as the routing surface; the field-level walkthroughs are where you head for the bundle-by-bundle detail.

The name on a BVN record changes for one of four reasons, and each reason has a different documentary chain. A typographic error from the original enrolment travels light: birth certificate, an affidavit explaining the misspelling, and any school or family record that backs the correct spelling. A marital surname change travels heavier: marriage certificate, court-sworn affidavit, and a change-of-name notice published in a national daily. A court-ordered name change for non-marital reasons sits in the heaviest documentary category: an order of a Nigerian High Court, an affidavit, and the same newspaper publication. A cross-system mismatch — where the BVN spelling and the NIN spelling disagree — is fixed on the side that holds the wrong value, and either route can be the right one depending on which record was captured incorrectly.

The bank's KYC desk reviews the bundle, fills the BVN Linking and Correction Form against the customer's account, and submits to NIBSS. There is no customer-side fee at the bank counter for the modification itself. The court affidavit, the newspaper publication, and any NPC document carry their own costs where they apply, paid at the issuing registry.

Processing windows on a clean name modification run within a few working days at NIBSS for a typographic case and longer for cases that involve a court order or newspaper publication review. The downstream propagation to other banks where you hold accounts adds another 24 to 72 hours after NIBSS confirms.

The full walkthrough, with one section per reason and the documentary chain tabulated for each, is at how to correct your BVN name. The parallel NIN-side route, useful where the same person needs both records aligned, is at how to correct the name on your NIN. For cross-system mismatch specifically, see BVN does not match NIN and the NIN-side mirror.

DOB correction is the heaviest-scrutiny modification in the BVN cluster, and it is not because the bank's KYC desk has decided to be difficult. The reason is structural. A date of birth is the field that ties a customer to age-gated services, retirement schemes, statutory office eligibility, and insurance valuations. A DOB shift on a BVN propagates into every Nigerian bank where you hold an account and gets cross-referenced with the NIN, the passport, the driver's licence and the tax record. The bank therefore wants the change anchored in a civil document NPC has issued, not in a customer assertion.

The legal anchor is the National Population Commission's attestation certificate (for customers born before 1992) or the NPC's digitalised birth certificate (for customers born after 1992). The bank cannot proceed without it. A court-sworn affidavit sits alongside the NPC document, explaining the discrepancy between the original NIMC capture and the corrected value.

The same documentary chain works on the NIN side, which is why the cross-cluster reference makes sense. The structural difference between the two clusters is the channel: the NIN's DOB correction is portal-self-service through NIMC's self-service modification portal, whereas the BVN's DOB correction is bank-submitted. Both routes converge on the same NPC document.

Processing at NIBSS for a clean BVN DOB modification typically runs two to six weeks. The bank submits same-day; NIBSS's review for higher-scrutiny modifications takes longer than for name or phone. Where a customer is also correcting the NIN DOB, the order to submit them in is treated at length in the deeper walkthrough.

The full walkthrough — including how to obtain the NPC attestation if you do not already hold one, what the bank's KYC desk inspects, and what happens at NIBSS on receipt — is at BVN date of birth correction. The parallel NIN-side route is at how to change the date of birth on your NIN.

Every BVN customer has exactly one phone-number change available across their entire banking life. The cap is the headline change in the CBN's 1 May 2026 amendments to the BVN framework.

Before May 2026 customers could update the BVN-linked phone number multiple times at branch. The amendment cancelled that flexibility. The motivation is explicitly anti-fraud: a SIM-swap attack works by hijacking a customer's number, intercepting the bank's OTP messages, and authorising transfers from the customer's accounts. A frictionless phone-number change at the BVN end made that hijack more attractive. The lifetime cap removes the frictionless option.

The procedural side is the lightest of the three modifications. The customer walks into the bank with a valid photo ID, the new phone number under their control, and any supporting evidence the bank's desk asks for (sometimes a police report where the original SIM was lost or stolen). The bank submits to NIBSS; NIBSS sends an OTP to the new number to confirm control; the linkage updates. The bank-side fee is zero.

The hard part is not the procedure. The hard part is the decision. The lifetime change is one-shot — once spent it cannot be reversed without an exceptional regulatory approval that is not yet in routine circulation. The deeper walkthrough exists specifically to give the reader the decision-support framework: when the lifetime change is appropriate, when it is not, and what recourse remains for a customer who has already used theirs.

Read BVN phone number update before submitting. The NIN-side parallel, useful for context only — the NIN allows three phone-number changes via the NIMC self-service portal rather than one via the bank — is at how to update phone number on NIN. Different agencies, different rules.

Different bundles, but several elements are constant across the three modification routes.

A BVN change rarely happens in isolation. The customer is typically also reconciling NIN, passport, driver's licence, or tax records to the new value. The sequence matters.

For a name change with a marriage certificate as the trigger, the canonical order is: NIN first, BVN second, passport third, then everything else. NIMC's record is the civil-identity anchor for the federal government; once the NIN reflects the new name, the BVN reconciliation is straightforward because the bank can pull a clean NIMC cross-reference. The marriage-name documentary chain is identical on both sides:

For a DOB correction, the order is the same — NPC document first, NIN modification through the NIMC self-service portal, then the BVN modification at the bank, with each subsequent step using the corrected document the previous step generated. Sequencing this way keeps the bank's cross-reference clean. Submitting the BVN modification before the NIN catches up risks a NIBSS-side mismatch and a stalled review.

For a phone-number change, the BVN side is the constrained side because of the lifetime cap. The NIN allows three changes through the NIMC portal; the BVN allows one across the customer's banking life. A reader replacing a number in both places should treat the BVN change as the binding decision: use the BVN change only when the new number is the long-term one, then update the NIN to match.

The cross-system mismatch problem — where the BVN and the NIN record the same field differently — is the subject of its own article. See BVN does not match NIN for the diagnostic and the fix on the side that holds the wrong value.

A short list of values the BVN modification route does not cover, because customers ask:

• The BVN itself. The eleven-digit number is permanent. A modification updates a field attached to it, not the number. If you believe you have two BVNs in error (duplicate enrolment), the route is a merge request at the bank, not a modification — see how to register for a BVN for the framing on duplicates.
• A biometric re-capture without a triggering reason. The bank does not re-take fingerprints or facial image on routine modification requests. A re-capture happens when an existing biometric template fails to verify and a fresh capture is needed; the bank's KYC desk initiates that, not the customer.
• Your gender field through a BVN form. Banks treat a gender change as a name-class modification with the same legal stack (court order, affidavit, newspaper publication). It is rare enough that the path is bank-specific rather than published; the customer's branch-relationship manager is the right initial contact.
• The bank where the BVN was originally enrolled. That field is historical and not customer-mutable. It does not affect any current operation; a customer can hold accounts at any number of banks regardless of where the original BVN biometric capture happened.

A customer arriving with a request that does not fit one of the three published modifications should expect the bank's KYC desk to need an internal escalation rather than a routine form. The route exists; it is not the same route as the three field corrections above.