FATF-flagged countries: Enhanced KYC/AML checks for co-op banks
No longer current — withdrawn, no replacement on file yet
Source: Reserve Bank of India · RBI/2009-10/254 · issued 10 Dec 2009 · ~1 min read
Quick answerRBI directs all StCBs/DCCBs to factor in AML/CFT risks from Iran, Uzbekistan, Pakistan, Turkmenistan, and Sao Tome and Principe, per FATF's October 16, 2009 statement. Principal Officers must acknowledge receipt to the regional office.
What changed
RBI issued a follow-up circular on December 10, 2009, reinforcing its November 9, 2009 advisory on AML/CFT deficiencies in five jurisdictions. It explicitly references FATF's October 16, 2009 statement and requires banks to account for risks from those countries.
What it means for you
Co-operative banks must treat transactions linked to Iran, Uzbekistan, Pakistan, Turkmenistan, and Sao Tome and Principe as higher risk under their KYC/AML frameworks. This may trigger enhanced due diligence, stricter monitoring, and reporting obligations. Non-compliance could expose banks to regulatory action.
Historical instruction — do not use for current compliance. This is what was required at the time; it no longer reflects current RBI requirements. If no replacement rule is linked above, that only means none is recorded on our register yet — it does not prove no later applicable rule exists. Confirm on the official RBI source below.
What banks were required to do at the time
Update your AML/CFT risk assessment to include the five flagged jurisdictions.
Instruct branch and compliance teams to apply enhanced due diligence on transactions involving these countries.
Ensure the Principal Officer sends acknowledgment of this circular to the concerned RBI Regional Office.
Who it affects
State Co-operative Banks (StCBs), Central Co-operative Banks (DCCBs), Principal Officers of co-operative banks
❓ Common questions
Regulatory timeline
Decoded by BankPulse2026-06-19 08:00 IST
repealed_by — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
Status change: withdrawn03 Aug 2026, 04:00 IST
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
Which countries are flagged in this circular?
Iran, Uzbekistan, Pakistan, Turkmenistan, and Sao Tome and Principe, as per FATF's October 16, 2009 statement.
What action must the Principal Officer take?
Acknowledge receipt of this circular to the concerned RBI Regional Office.
Does this replace the November 9, 2009 circular?
No, it reinforces and supplements the earlier advisory on AML/CFT deficiencies in those jurisdictions.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
Repealed byRBI/2025-26/100 — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
RBI’s words: “Official withdrawal register entry #1772: RPCD.CO.RF.AML.No.6548/07.02.12/2009-10 — "Know your Customer (KYC) Norms / Anti-Money Laundering (AML) Standards / Combating of Financing of Terrorism (CFT)"”
📜 Read the original circular — full text as issued by RBI
RBI/2009-10/254
RPCD.CO.RF.AML.No.6548/07.02.12/2009-10
December 10, 2009
The Chairmen / CEOs of all State / Central Co-operative Banks
Dear Sir,
Know your Customer (KYC) Norms / Anti-Money Laundering (AML) Standards /
Combating of Financing of Terrorism (CFT)
Please refer to our letter RPCD.CO.RF.AML.No.4863/07.02.12/2009-10 dated November 9, 2009 on risks arising from the deficiencies in AML/CFT regime of Iran, Uzbekistan, Pakistan, Turkmenistan and Sao Tome and Principe.
2. Financial Action Task Force (FATF) has issued a statement dated October 16, 2009 on the subject ( copy enclosed ). Banks are accordingly advised to take into account risks arising from the deficiencies in AML/CFT regime of Iran, Uzbekistan, Pakistan, Turkmenistan and Sao Tome and Principe.
3. Please advise Principal Officer of your bank to acknowledge receipt of this letter to our concerned Regional Office.
Yours faithfully,
(R.C.Sarangi)
Chief General Manager
Encl: As above
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2009-10/254 · issued 10 Dec 2009. The plain-English explanation above is BankPulse’s own independent summary.
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=5416&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.