Risk Management Strategies

Caller Names on Every 4G Call From 1 November: Will CNAP Cut Impersonation Fraud, and What Social-Engineering Cover Your Business Still Needs

DoT has told Airtel, Jio, Vi and BSNL to show the caller's registered name by default on 4G calls from 1 November 2026. Here is what that fixes for corporate payment fraud, what it does not, and how to align call-back rules and crime cover.

Tarun Kumar Singh
Tarun Kumar SinghStrategic Risk & Compliance SpecialistAIII · CRICP · CIAFP
9 min read

Listen to this article

Audio version • 9 min read

CNAPimpersonation fraudsocial engineeringcrime insurancefinance controls

Last reviewed: November 2026

What DoT Has Ordered for 1 November

The Department of Telecommunications has directed Airtel, Jio, Vodafone Idea and BSNL to roll out calling name presentation (CNAP) with effect from 1 November 2026. The direction follows an amendment to the definition of calling line identification (CLI) in the unified licence, so the caller's name becomes part of what the network presents alongside the number, as reported by Inc42 on 15 October 2026.

Three design choices matter for a finance or risk team:

  • Default on, no opt-in. CNAP will be enabled by default on 4G and higher networks. Recipients do not need to sign up, which means most people on 4G or 5G connections will start seeing a name on incoming calls without doing anything.
  • Registered name, not a crowd-sourced label. The name shown is the one tied to the connection's registration with the operator. For business and bulk connections, the subscriber can display a preferred name only if it is backed by a registered trademark or a GST-registered trade name, and the operator verifies the documents.
  • Limited retention. The recipient's operator must not store the name after the call ends, and operators must set up complaint-handling systems for disputes over displayed names.

The policy path was long. TRAI's recommendations date to February 2024, and in October 2025 TRAI backed default activation, moving away from its earlier opt-in proposal. The final direction reflects that shift.

This post treats 1 November as the scheduled start date. How the rollout performs in practice, and how quickly operators clear business name verification requests, is something each company should check with its own operator rather than assume.

Which Impersonation Calls CNAP Is Likely to Blunt

Most voice-led payment fraud against Indian companies follows a familiar pattern. Someone calls an accounts payable executive claiming to be the company's bank relationship manager, a known vendor's finance head, or a senior executive travelling abroad. The caller creates urgency, asks for a change in beneficiary details or an out-of-cycle transfer, and relies on the fact that the number on screen is unfamiliar but plausible.

CNAP changes the information on the recipient's screen. When a caller using a personal SIM registered in their own name claims to be calling "from your bank's corporate banking desk" or "from your logistics vendor", the recipient will now see the registered subscriber's personal name instead of a bare number. That mismatch is a useful red flag, especially for junior staff who would otherwise hesitate to challenge a confident caller.

The benefit is strongest where three conditions hold:

  1. The fraudster calls over a 4G or 5G mobile connection, which is where CNAP is on by default.
  2. The SIM is registered to an individual whose name does not match the claimed organisation.
  3. The genuine organisation has registered its own trade name, so staff learn what a real call from that bank or vendor looks like.

The third condition is the one companies control. If your vendors and banking partners never register a business display name, staff have no reference point, and a personal name on screen tells them little.

What CNAP Does Not Fix

A displayed name is a signal about the connection, not about the person speaking or the instruction they give. Finance teams should be clear on the gaps before anyone starts treating the screen as verification.

Channels outside the scope

  • WhatsApp and VoIP calls. CNAP is a feature of the operator's calling line identification. Calls placed over WhatsApp or other internet calling apps do not carry the network-presented name, and these are a common route for executive impersonation.
  • 2G, 3G and landlines. The direction makes CNAP default on 4G and higher networks. 2G, 3G and landline connections are to be examined separately, so calls from those networks may show no name at all.
  • CLIR callers. Callers who have calling line identification restriction are exempt. A withheld identity is not new, but staff should not read "no name shown" as harmless.

Attacks that defeat the name

  • Compromised or misused genuine numbers. If a fraudster gains access to a real vendor employee's phone, or an insider at a vendor is involved, the call will show the correct company name. CNAP then makes the fraud more convincing, not less.
  • Deepfake voices on real lines. Voice cloning attacks, covered in our post on deepfake payment fraud and crime and cyber cover, often move to a messaging app or video call after first contact. The name on an initial call proves nothing about later instructions.
  • Email-led fraud. Business email compromise and fake invoices do not touch the phone network at all. Many payment diversion losses start with a spoofed or hijacked mailbox and use a phone call only to add pressure.

Why Finance Teams Should Register the Company's Trade Name Now

Registering a business display name is a defensive step that costs little. Under the DoT direction, business and bulk-connection users may present a preferred name if they hold a registered trademark or a GST-registered trade name, and the operator verifies the supporting documents.

There are three practical reasons to start before or immediately after 1 November:

  1. Customers and vendors learn your real name. If your treasury, collections and vendor-management teams call from connections that display your registered trade name, counterparties can be told to treat calls showing anything else with suspicion. That protects your vendors from fraudsters impersonating you.
  2. The default may not show what you expect. Corporate connections are often registered in the legal entity name, a parent company name, or an older name after a restructuring. If the default display does not match the name your vendors know, the mismatch creates confusion that a fraudster can exploit.
  3. Document verification takes time. Operators must check trademark or GST documents. Collecting the right certificates for each entity and each block of numbers is an administrative job that is easier to finish before an incident than during one.

A short action list

  • Map which mobile connections are used for outbound finance, procurement and customer calls, and which entity holds each.
  • Gather the GST registration certificate showing the trade name, or the trademark registration certificate, for each relevant entity.
  • Ask each operator account manager for the CNAP business name process and expected timelines.
  • Once live, write to key vendors and customers stating the name your genuine calls will display and the numbers they should expect.

Ask your banks and largest vendors whether they are doing the same. A vendor that has registered its trade name gives your accounts payable team a cleaner reference point.

Rewriting Call-Back and Payment Verification Rules

CNAP is a reason to revisit payment controls, but the direction of the change matters. The goal is to make sure the new on-screen name is used as a warning sign when it does not match, and never as confirmation when it does.

Control language to update

  1. Inbound calls never authorise anything. Any request received on an inbound call (change of bank details, urgent transfer, new beneficiary, release of a held payment) is treated as unverified, whatever name the screen shows.
  2. Call-back to a number on record. Verification happens by calling back a number taken from the vendor master or a signed contract, not a number given in the call, email or message. The call-back is placed by someone other than the person who received the request.
  3. Name mismatch triggers escalation. If a caller claims to represent an organisation and the displayed name is a personal name or a different business, staff end the call and report it. This is the one place where CNAP adds a clear control.
  4. No-name calls get the same scrutiny. WhatsApp, VoIP, landline, 2G or 3G and withheld-number calls show no network name. Policy should treat them exactly like a mismatch.
  5. Dual approval for master data changes. Changes to vendor bank details need two approvers and a documented call-back before the first payment to the new account.
  6. Record the verification. The person doing the call-back logs date, time, number dialled and person spoken to. This record is what an insurer will ask for after a loss.

Put the CNAP rule in one plain sentence in your treasury manual: "A name displayed on an incoming call is not proof of identity and must not be cited as a verification step." Train it alongside your existing call-back rule, not as a separate topic.

These steps line up with the verification conditions that insurers attach to social engineering cover, which is where the insurance question begins.

How Crime and Cyber Policies Treat Impersonation Fraud

When an employee is tricked into sending money, the loss is usually framed as a voluntary transfer. Many traditional crime and fidelity guarantee wordings were built around employee dishonesty, forgery and direct computer fraud, so a deceived but honest employee's authorised payment can fall outside the core insuring clauses. Coverage for this scenario typically depends on a specific extension, often titled social engineering fraud, fraudulent impersonation or fraudulent instruction cover.

What to check in your current wording:

  • Sublimit. Social engineering extensions are commonly written with a sublimit well below the main crime limit. Check whether that figure reflects the size of payments your finance team actually releases in a day.
  • Verification condition. Many extensions require the insured to have verified the instruction through a documented call-back or similar out-of-band check before paying. If the wording specifies how verification must be done, your treasury procedure should match it word for word.
  • Who can be impersonated. Some extensions cover impersonation of vendors, customers and employees; others name only some of these. A bank impersonation may not fit any category in a narrow wording.
  • Cyber policy boundary. A cyber insurance policy may pay forensic and response costs after a mailbox compromise, but the transferred funds are often excluded unless a cybercrime or funds-transfer fraud extension applies. Read both policies together so there is no gap and no assumption that the other one responds.

For market context on why buyers are asking for crime cover now, see our note on commercial crime and fidelity insurance demand.

What to Do Before and After 1 November

The rollout gives finance, risk and insurance teams a natural deadline to tidy up a set of controls that are often left to drift.

Before the rollout

  • Start trade name registration for the entities and connections used in finance, procurement and customer contact.
  • Amend the treasury manual and AP procedures so that a displayed name is never a verification step, and a mismatch or missing name is an escalation trigger.
  • Pull out your crime and cyber policies and read the social engineering sublimit, verification condition and impersonation definitions against your updated procedure.

After the rollout

  • Tell vendors and customers which name your genuine calls display.
  • Track reported mismatched-name calls as a simple near-miss log. It gives you data for the next insurance renewal and shows underwriters that controls are working.
  • Use the operators' complaint-handling systems if your trade name is being misrepresented, and record those complaints.

For sectors where impersonation is already causing real losses, such as freight and logistics, our post on cargo theft through freight platform impersonation shows how a single unverified call can turn into a full-load loss. CNAP will help with some of those calls. Procedures and the right policy wording will still carry most of the weight.

About the Author

Tarun Kumar Singh

Tarun Kumar Singh

Strategic Risk & Compliance Specialist

  • AIII
  • CRICP
  • CIAFP
  • Board Advisor, Finexure Consulting
  • Developer of the Behavioural Underinsurance Risk Index (BURI)

Tarun Kumar Singh is a seasoned risk management and insurance professional based in Bengaluru. He serves as Board Advisor at Finexure Consulting, where he advises insurance, fintech, and regulated firms on governance, growth, and trust. His work spans insurance broker regulatory frameworks across India, UAE, and ASEAN, IRDAI compliance and Corporate Agency model reform, VC governance in insurtech, and MSME insurance gap analysis. He is the developer of the Behavioural Underinsurance Risk Index (BURI), a framework applying behavioural economics to underinsurance and insurance fraud risk.

Frequently Asked Questions

When does CNAP start in India and do users need to opt in?
DoT has directed Airtel, Jio, Vodafone Idea and BSNL to roll out calling name presentation with effect from 1 November 2026. It is enabled by default on 4G and higher networks, so recipients do not need to opt in. 2G, 3G and landline networks are to be examined separately, and callers who use calling line identification restriction are exempt.
Can our company show its brand name instead of the legal entity name on outgoing calls?
Business and bulk-connection users may display a preferred name if it is backed by a registered trademark or a GST-registered trade name. The operator verifies the documents before the name is used. Contact your operator account manager for the process and gather the GST or trademark certificates for each entity that holds the relevant connections.
If a call shows our bank's correct name, can staff treat it as verified?
No. A correct name only tells you which registered connection placed the call. A compromised genuine phone, an insider, or a cloned voice on a real line will still show the right name. Payment and bank detail changes should only be verified by calling back a number held on record, placed by someone other than the person who received the request.
Will our crime policy pay if an employee is tricked into transferring funds by a phone call?
It depends on the wording. Many crime policies need a specific social engineering or fraudulent impersonation extension to respond to a voluntary transfer by a deceived employee, and that extension often carries a lower sublimit and a verification condition. Check the sublimit, the definition of who can be impersonated, and the verification steps the policy requires, and make sure your treasury procedure matches them.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada Intelligence

Ready to see Sarvada in action?

Explore the platform workflow or start a product conversation with our underwriting automation team.

Explore the platform