The Hawala Operator Uses Nicknames and Codes - How Should Identity Be Tested Before Treating a Code Word as a Person?

HAWALA • NICKNAMES • CODE WORDS • IDENTITY • LEDGERS • DIGITAL EVIDENCE • FEMA • PMLA

The Hawala Operator Uses Nicknames and Codes - How Should Identity Be Tested Before Treating a Code Word as a Person?

Advocate Ankit Kumar Singh - hawala nicknames code words identity financial evidence research

Advocate Ankit Kumar Singh — FEMA, Hawala, PMLA, Digital Evidence & Financial Investigation Research

Legal research and analysis by Advocate Ankit Kumar Singh

Primary professional base: Patna, Bihar

Updated and legally reviewed: 2 September 2026

Direct Answer

A nickname or coded identifier in an alleged hawala ledger does not become a particular person merely because investigators believe that person fits the description.

The proper sequence is:

CODE

↓

PROVE WHAT THE CODE MEANS

↓

PROVE WHO THE CODE IDENTIFIES

↓

PROVE THE TRANSACTION ATTRIBUTED TO THAT PERSON

↓

APPLY THE RELEVANT STATUTORY INGREDIENTS.

“Tiger” Is Not Self-Identifying

Suppose a seized ledger states:

TIGER — 25 — DXB — DONE

The record raises questions.

It does not answer them.

Investigators must establish:

Who is Tiger?
What does 25 mean?
What does DXB mean?
What does “done” mean?
What transaction occurred?

Stage One: Is the Code Even a Person?

A coded entry may represent:

a person;
a company;
a location;
a transaction type;
a currency;
an account;
a project;
a branch.

Do not begin with the assumption that every code represents a human participant.

Location Codes Are Particularly Easy to Misread

Consider:

PATNA — 20

That could mean:

Patna branch;
Patna transaction;
Patna recipient;
a person nicknamed Patna.

Context is essential.

Company Codes Can Look Like Initials

“AK” may mean:

an individual's initials;
A.K. Enterprises;
an account classification;
a geographical code;
a customer group.

The abbreviation should not be personified without evidence.

The Unique-Nickname Test

A nickname becomes stronger identifying evidence when it is objectively and distinctively associated with one person.

Consider:

well-known nickname;
trade name;
business name;
residence name;
saved telephone contact;
consistent self-identification.

Sunil Kumar Agarwal 2025: A Modern Code-Identity Illustration

An ITAT Jaipur matter considered the identifier “Narnoli”.

The record linked that expression to the assessee through surrounding facts including:

use of the expression with his name/business;
business-group identity;
address connection;
broker explanation;
absence of an effective dispute regarding the attribution.

This illustrates how a distinctive identifier can become considerably stronger than a generic abbreviation.

Important: The Narnoli Decision Is Not a FEMA Hawala Precedent

It arose under Income-tax law.

Its relevance here is evidentiary:

A CODE CAN BE ATTRIBUTED TO A PERSON WHEN OBJECTIVE SURROUNDING MATERIAL ESTABLISHES THE CONNECTION.

Generic Initials Require Greater Caution

A code such as:

could refer to many things.

A generic shorthand requires a stronger identification foundation than a unique and consistently used moniker.

Ask: How Did the Investigator Decode It?

The investigation should be able to explain the methodology.

Was the attribution based upon:

operator's statement?
phone number?
contact list?
another ledger?
WhatsApp?
email?
independent witness?
self-identification?

The Author's Explanation Can Be Relevant

If the ledger writer states:

“TIGER MEANS RAJ KUMAR.”

that may assist identification.

But a careful investigation should ask:

Why was that code used?
Was it consistently used?
Is Raj Kumar saved as Tiger?
Do chats use the same nickname?
Does a counter-ledger use the same code?

Author's Explanation Is Not the End of the Inquiry

The writer may be:

mistaken;
protecting another person;
shifting responsibility;
reconstructing an old code from memory.

Objective corroboration is therefore valuable.

The Codebook Test

An alleged operator may maintain a separate mapping table:

Code	Mapped Entry
T-17	Raj Kumar
AK-7	A.K. Enterprises
B04	Blue Trading

Such a contemporaneous codebook can be significant.

But authenticate it like any other financial record.

A Codebook Created After the Investigation Began Is Different

Ask:

when was the mapping document created?
where was it recovered?
was it contemporaneous?
does metadata support its age?
does it reconcile with earlier records?

Mobile Contact Mapping

Suppose the operator's phone stores:

TIGER — 98XXXXXXXX

and telecom/account records reliably establish that the number belongs to the person alleged.

That can provide strong code-to-person evidence.

But One Saved Contact Does Not Automatically Decode Every Historical Entry

A nickname can:

change;
be reused;
refer to different persons at different periods;
exist separately across operators.

The date and coding system matter.

The Self-Identification Test

Potentially strong evidence includes:

“SAVE MY NUMBER AS TIGER.”

or:

“THIS IS TIGER — RELEASE MY PAYMENT.”

if the communication is authentically attributed to the person alleged.

Consistent Communication Matters

A stronger pattern may be:

CONTACT: TIGER

WHATSAPP: “Tiger 20 Dubai today?”

LEDGER: TIGER / DXB / 20

FOREIGN RECORD: common transaction code.

Multiple consistent data points may support attribution.

Do Not Mistake Repetition for Independence

If the:

second ledger;
statement;
investigation chart

all merely copied the first diary's nickname attribution, the evidence may still originate from one source.

COUNT INDEPENDENT SOURCES, NOT REPEATED ASSERTIONS.

Reverse-Mapping Is Essential

Do not ask only:

“COULD TIGER BE PERSON A?”

Also ask:

“IS PERSON A INDEPENDENTLY KNOWN AS TIGER?”

And:

“DOES TIGER REFER TO ANYBODY ELSE IN THE RECORD?”

The Exclusion Test

If there are four possible persons with initials “RK”, the investigation should not simply select one.

Look for:

unique phone number;
address;
company;
location;
counterparty;
transaction history.

The Time-Period Test

A code-to-person mapping established for 2019 should not automatically be transplanted to 2026.

Ask whether the same:

operator;
phone;
coding convention;
business relationship

continued throughout the relevant period.

Different Operators May Use the Same Code Differently

“Boss” may mean Person X in one network.

It may mean Person Y in another.

There is no universal hawala dictionary.

Number Codes Require Their Own Decoding

Suppose:

TIGER — 25

Even if Tiger is identified, “25” may still require proof.

It might represent:

₹25 lakh;
USD 25,000;
a balance;
a transaction code;
25 units.

Code-to-Person and Code-to-Amount Are Separate Exercises

The prosecution/investigation should not reason:

TIGER = PERSON A

therefore:

25 = ₹25 LAKH.

Each decoding proposition needs its own factual foundation.

V.C. Shukla and the Jain Hawala Diaries

The Supreme Court's landmark decision involved diaries and records containing abbreviated identities, figures and alleged receipts/disbursements.

The case remains foundational when analysing coded financial records.

What V.C. Shukla Does Not Say

It does not create a rule:

“CODED RECORDS CAN NEVER BE PROVED.”

Its broader importance is the need to distinguish:

the record;
its evidentiary character;
the meaning of the notation;
independent proof of the alleged transaction.

Section 28 BSA: Even Regular Accounts Do Not Finish the Case

Current Section 28 makes regularly maintained book-of-account entries relevant, including electronically maintained accounts.

But the statute expressly states that such entries alone are insufficient to charge a person with liability.

Three Separate Evidentiary Steps

STEP 1:

Code → Person.

STEP 2:

Entry → Real transaction.

STEP 3:

Transaction → Legal liability.

Success at Step 1 does not automatically prove Steps 2 and 3.

Section 33 BSA: Read the Code in Context

A coded word forming part of a document, book, electronic record or conversation should be understood with enough surrounding material to explain its nature and effect.

Inspect:

full page;
previous page;
next page;
column heading;
abbreviation legend;
running balance;
related communications.

Do Not Decode a Cropped Screenshot

A screenshot containing:

TIGER — 20

may omit a heading such as:

“PENDING CONTACTS”

or:

“DUBAI PAYMENTS.”

Context can completely change the interpretation.

Electronic Code Records: Sections 61–63 BSA

Where the coded ledger is electronic, investigate:

source device;
file owner;
metadata;
creation date;
modification history;
complete file;
certificate requirements;
extraction integrity.

A Screenshot Is Not the Entire Digital Ledger

The underlying data may contain:

hidden columns;
comments;
revision history;
formulae;
linked worksheets;
user information.

Those elements can be important for decoding.

2026 Muthulakshmi Vellaisamy: The Need for Precise Identity

A January 2026 ITAT Chennai decision concerned third-party loose sheets and notepads interpreted as alleged unaccounted cash transactions.

Important weaknesses included:

author not adequately examined;
third-party recovery;
disputed interpretation;
retracted explanation;
lack of sufficient corroborative inquiry;
uncertainty concerning the precise nature and identity of the transaction.

Important: Muthulakshmi Is an Income-Tax Decision

It is not a FEMA hawala precedent.

Its relevance is evidentiary:

THIRD-PARTY CODES AND NARRATIONS REQUIRE A RELIABLE NEXUS TO THE PERSON AND THE PARTICULAR TRANSACTION.

Harminder Singh Bhatia: A Nickname Can Be Proved

An ITAT Indore matter considered seized records referring to “P. Bhaiya”.

The surrounding evidence supported that the assessee was known as “Pintu Bhaiya”.

This is an example of code attribution becoming stronger through established nickname usage and surrounding business records.

The Correct Balance

Wrong proposition:

NICKNAMES ARE NEVER RELIABLE.

Also wrong:

INVESTIGATOR SAYS “TIGER” MEANS X, SO IDENTITY IS PROVED.

Correct:

TEST THE ATTRIBUTION AGAINST INDEPENDENT, CONSISTENT AND TRANSACTION-SPECIFIC EVIDENCE.

Witnesses Can Help Decode a Nickname

A witness may say:

“EVERYONE IN THE BUSINESS CALLED HIM DOCTOR.”

This may be relevant.

But stronger proof can include:

multiple independent witnesses;
contacts;
chats;
invoices;
business records using the same nickname.

Five Witnesses May Still Represent One Source

If every witness learned:

“TIGER MEANS X”

from the same broker after the search, the apparent corroboration may not be truly independent.

Counter-Ledger Example

INDIA LEDGER:

T-17 / ₹25,00,000 / DXB.

CODEBOOK:

T-17 = Raj Kumar / Mobile 98XXXXXXXX.

FOREIGN LEDGER:

T-17 / AED equivalent / completed.

WHATSAPP:

Message from verified Raj Kumar account concerning the same transaction.

This cumulative record is materially stronger than a single unexplained code.

The Matching-Transaction Test

After code identity is proposed, ask whether the coded transaction matches the person's objectively proved conduct:

cash withdrawal;
meeting;
message;
foreign beneficiary;
exchange rate;
transaction date.

Identity Does Not Prove Payment

Even if:

TIGER = PERSON A

is conclusively established, the investigation still needs to prove whether the ledger means:

Person A paid;
Person A received;
Person A owed;
Person A instructed;
Person A was merely a contact.

FEMA: Code Mapping Is Only the First Step

Where FEMA Section 3 is invoked, investigators still need the actual statutory transaction.

Depending upon the allegation:

what foreign exchange was dealt with?
who was resident outside India?
who paid or received?
was an authorised person involved?
was there corresponding inward remittance?
what foreign-side value existed?

“Tiger Is X” Does Not Itself Prove Section 3(c)

Section 3(c) requires analysis of the actual payment/receipt and foreign-resident instruction structure.

Code identification cannot substitute for the substantive ingredients.

PMLA: Identity Is Not Proceeds of Crime

Even if a code is mapped to a person, PMLA still requires examination of:

scheduled offence;
proceeds of crime;
connection with such proceeds;
relevant Section 3 activity.

A coded nickname cannot manufacture proceeds of crime.

BNS Section 111

Hawala transaction appears within the economic-offence framework of the organised-crime provision.

But identifying a coded participant does not itself establish all ingredients of organised crime.

Section 8 BSA and Conspiracy

Current Section 8 addresses statements, acts or writings by conspirators in reference to a common design where there is reasonable ground to believe the conspiracy exists.

A coded ledger may become relevant in an appropriate conspiracy case.

But foundational evidence of the common design remains important.

Avoid the Circular-Conspiracy Argument

Wrong:

TIGER = X BECAUSE X IS PART OF THE CONSPIRACY.

Then:

X IS PART OF THE CONSPIRACY BECAUSE TIGER APPEARS IN THE LEDGER.

Independent foundational evidence should break that circle.

The Code-to-Person Identity Matrix

Evidence	Potential Significance	Limitation
Generic nickname	Possible identifier	May fit many people
Unique moniker	Stronger identity clue	Still prove usage
Matching phone number	Strong identity link	Check ownership/time period
Operator explanation	Decodes terminology	Seek corroboration
Self-identification	Strong alias evidence	Authenticate communication
Independent codebook	Potential direct mapping	Authenticate date/source
Repeated consistent code	Pattern evidence	Check source independence
Counter-ledger	Cross-record corroboration	Ensure not copied
Matching transaction	Connects identity with conduct	Still apply statute

The Code Attribution Reconstruction

EXACT CODE / NICKNAME:
____________________

DOCUMENT / DEVICE:
____________________

DATE:
____________________

WHO CREATED RECORD:
____________________

IS CODE A PERSON / COMPANY / LOCATION / ACCOUNT?
____________________

PROPOSED PERSON:
____________________

WHY INVESTIGATORS SAY CODE = PERSON:
____________________

KNOWN NICKNAME?
YES / NO

PHONE NUMBER:
____________________

PHONE OWNERSHIP PROVED?
YES / NO

CONTACT SAVED UNDER CODE?
YES / NO

FULL NAME APPEARS ELSEWHERE?
YES / NO

CODEBOOK EXISTS?
YES / NO

AUTHOR EXPLAINS CODE?
YES / NO

EXPLANATION RETRACTED?
YES / NO

SELF-IDENTIFICATION?
YES / NO

MATCHING WHATSAPP / EMAIL?
____________________

COUNTER-LEDGER:
____________________

COMMON TRANSACTION CODE:
____________________

MATCHING FINANCIAL EVENT:
____________________

FOREIGN-SIDE EVENT:
____________________

ALTERNATIVE PERSON USING SAME CODE:
____________________

CODE USED DIFFERENTLY ELSEWHERE?
____________________

TIME PERIOD CONSISTENT?
YES / NO

INDEPENDENT CORROBORATION:
____________________

AFTER IDENTITY IS PROVED:

WHAT TRANSACTION IS ALLEGED?
____________________

WHAT FEMA / PMLA / BNS PROVISION?
____________________

The Practical Identity Ladder

WEAKER:

generic nickname;
initials;
investigator assumption;
mere acquaintance;
one ambiguous entry.

MORE SIGNIFICANT:

known nickname;
writer's explanation;
repeated usage;
matching business/location;
communications near relevant dates.

STRONGER CUMULATIVE IDENTITY RECORD:

unique phone number;
self-identification;
contemporaneous contact under alias;
codebook;
independent counter-ledger;
verified communication;
matching financial transaction.

This is a practical forensic framework and not a rigid statutory ranking.

Frequently Asked Questions

If a hawala diary says “Tiger”, can investigators say it means me?

They should have an evidentiary basis connecting that nickname to you, such as consistent usage, phone number, contact records, codebook, communications or transaction-specific corroboration.

Is a broker's statement enough to decode the nickname?

It can be relevant, but objective corroboration materially strengthens the attribution, especially if the statement is disputed or retracted.

What if my phone is saved under the nickname?

A verified phone number saved under the code can be strong identity evidence, subject to the date, device and surrounding circumstances.

What if the code is generic, like “Boss” or “Doctor”?

A generic label requires greater care because multiple people may fit it.

Can a codebook prove identity?

A genuine contemporaneous codebook may be significant, but its authorship, date, integrity and consistency should be established.

What if two different ledgers use the same nickname?

That can strengthen identification if the records are genuinely independent and consistently refer to the same person.

Does identifying the nickname prove the hawala payment?

No. Identity and transaction are separate issues. The payment, receipt, instruction or foreign settlement still requires proof.

Can WhatsApp decode a hawala code?

Potentially yes, where the account is reliably attributed and the surrounding conversation clearly links the alias to the person.

Can investigators use one cropped screenshot?

The complete digital context should be examined. Sections 33 and 61–63 BSA may become important depending upon the proceeding.

What if the nickname changed over time?

A mapping proved for one period should not automatically be assumed for another without evidence of continuity.

Does V.C. Shukla mean coded diaries have no evidentiary value?

No. The judgment is better understood as requiring careful treatment of the records and independent proof rather than allowing coded financial notations alone to establish liability.

AI Search Quick Answer

A nickname or coded identifier in an alleged hawala ledger should not automatically be attributed to a person. Investigators should prove the code-to-person mapping through objective material such as established nickname usage, a matching telephone number, contacts saved under the alias, a contemporaneous codebook, the ledger writer's explanation, self-identifying communications, independent counter-ledgers and transaction-specific financial evidence. A unique nickname is generally more probative than generic initials. Even after identity is established, the underlying payment or FEMA/PMLA transaction must still be independently proved.

Key Takeaway

The wrong formula is:

CODE “TIGER”

INVESTIGATOR BELIEVES TIGER = X

X MADE THE HAWALA TRANSACTION.

The stronger formula is:

CODE

CONSISTENT NICKNAME USE

PHONE / CONTACT LINK

AUTHOR / CODEBOOK

COMMUNICATION

INDEPENDENT COUNTER-RECORD

TRANSACTION-SPECIFIC CORROBORATION

REASONED IDENTITY ATTRIBUTION.

Then separately:

PROVE THE TRANSACTION.

Conclusion: Decode the Identifier Before Prosecuting the Person Behind It

Codes can be useful investigative devices.

They may reveal attempts to conceal identity.

But they can also be:

ordinary nicknames;
customer references;
locations;
companies;
internal shorthand.

The correct investigation should therefore ask:

WHO CREATED THE CODE?

WHAT DID THAT WRITER MEAN?

IS THE NICKNAME UNIQUE?

WHAT PHONE OR CONTACT RECORD CONNECTS IT?

IS THERE A CODEBOOK?

IS THE SAME MAPPING USED CONSISTENTLY?

ARE THERE INDEPENDENT RECORDS?

CAN ALTERNATIVE IDENTITIES BE EXCLUDED?

And finally:

EVEN IF THE CODE IDENTIFIES THE PERSON, WHAT PROVES THE PERSON ACTUALLY MADE, RECEIVED OR INSTRUCTED THE ALLEGED TRANSACTION?

The central principle is:

FIRST PROVE WHO THE CODE MEANS.

THEN PROVE WHAT THAT PERSON DID.

Official and Authoritative Sources

Bharatiya Sakshya Adhiniyam, 2023 — Sections 8, 28, 33, 61, 62 and 63
Central Bureau of Investigation v. V.C. Shukla & Others — Supreme Court of India, 2 March 1998
Common Cause v. Union of India — Supreme Court of India, 11 January 2017
Sunil Kumar Agarwal v. ACIT — ITAT Jaipur, 14 October 2025 — evidentiary illustration
DCIT v. Muthulakshmi Vellaisamy & connected matter — ITAT Chennai, 20 January 2026 — evidentiary illustration
Harminder Singh Bhatia v. ACIT — ITAT Indore, 18 April 2022 — nickname-identification illustration
Foreign Exchange Management Act, 1999 — Sections 1, 3 and related provisions
Prevention of Money Laundering Act, 2002 — Sections 2(1)(u), 2(1)(y), 3 and Schedule
Bharatiya Nyaya Sanhita, 2023 — Section 111 where independently applicable

Add Advocate Ankit Kumar Singh as a Preferred Source on Google

Readers who want more FEMA, PMLA, ED, hawala, digital-evidence and financial-investigation research from Advocate Ankit Kumar Singh can add advocateankitkumarsingh.in as a Preferred Source on Google.

Add advocateankitkumarsingh.in as a Preferred Source on Google

Professional Consultation

Advocate Ankit Kumar Singh

Primary professional base: Patna, Bihar

Phone: 8294431232

Email: ankitsingh.legum@gmail.com

Website: advocateankitkumarsingh.in

Professional assistance in FEMA, alleged hawala, PMLA and coded-financial-record matters may include nickname and code attribution analysis, seized-ledger review, contact and mobile mapping, codebook examination, counter-ledger comparison, electronic-evidence review, transaction reconstruction, FEMA Section 3 analysis, Directorate of Enforcement proceedings, PMLA overlap and connected adjudicatory or High Court strategy according to the evidence, governing law, jurisdiction and accepted professional engagement.

Complex digital or financial reconstruction may require coordination with chartered accountants, forensic accountants, digital-forensics professionals, foreign counsel or other appropriate experts.

No particular code attribution, FEMA/PMLA finding or adjudicatory/judicial result can be guaranteed.

Professional / Legal Disclaimer: This article is general legal research and professional information. A nickname, alias, initials or coded identifier found in a diary, loose sheet, telephone contact, chat or electronic ledger should be interpreted according to the complete evidentiary context. Code-to-person attribution and proof of the underlying transaction are separate questions. V.C. Shukla and Common Cause arose under the Indian Evidence Act, 1872; current proceedings should additionally be examined under the Bharatiya Sakshya Adhiniyam, 2023. Income-tax decisions discussed above are used only as evidentiary illustrations and should not be represented as FEMA or PMLA precedents. No person should alter, destroy, fabricate or backdate codebooks, ledgers, chats, contacts or financial records.