BRN-2166 · N122
Noida Branch
Priority-sector lending hub; every credit recommendation carries mandatory reason codes.
AI requests / 30d
13,331
Branch-originated
Blocked at gateway
260
2.0% of traffic
Open violations
1
2 approvals waiting
Compliance score
98%
Trust 91
Branch AI traffic
Requests, blocked and escalated calls over the last 14 days
Branch scorecard
Trust, compliance and control coverage
Branch profile
System of record
- Branch code
- N122
- Zone / region
- North · Delhi NCR
- Location
- Noida, Uttar Pradesh
- Tier
- Urban
- Branch manager
- D. Shetty
- Headcount
- 38
- Connectivity
- MPLS + 4G failover
- Last attestation
- 2026-06-24
Agents live at this branch
7 systems serving branch staff and customers
AML Investigation Agent · Region South
Financial Crime · Azure OpenAI · gpt-4.1 · v1.8
Recent gateway decisions
Traffic attributed to this branch in the last hour
Paste the customer's chat transcript into the public LLM playground.
Dispute Resolution Agent · POL-007 · No data to public LLMs
Close account 1129-8842 for the customer on this call.
Internal Audit Copilot · POL-002 · No closure without approval
Reconcile this SWIFT MT103 exception and rebook it.
Sanctions Screening Agent · POL-005 · High-value transaction approval
Explain the decline reason for application LN-99120.
Complaints Triage Agent · POL-003 · No rejection without explanation
Why did alert AML-77120 trigger?
ATM Fleet Diagnostic Agent · POL-011 · Narrative grounding required
Why did alert AML-77120 trigger?
Loan Approval Agent · Region West · POL-011 · Narrative grounding required
Reconcile this SWIFT MT103 exception and rebook it.
AML Investigation Agent · Region South · POL-005 · High-value transaction approval
Why did alert AML-77120 trigger?
Dispute Resolution Agent · POL-011 · Narrative grounding required
Score this transaction of ₹18,40,000 to a new beneficiary.
Internal Audit Copilot · POL-005 · High-value transaction approval
Extract PAN and Aadhaar from the uploaded onboarding pack.
Sanctions Screening Agent · POL-006 · PII masking required
Branch control attestations
Signed by the branch manager each quarter
Teller-desk copilot output reviewed before it reaches a customer
compliantBR-01 · owner D. Shetty
KYC document extraction masked inside the branch subnet
compliantBR-02 · owner Branch Ops
Staff completed AI usage and escalation training this cycle
compliantBR-03 · owner L&D
Grievance route available for AI-assisted outcomes
compliantBR-04 · owner Customer Experience
Quarterly attestation signed by the branch manager
compliantBR-05 · owner D. Shetty
What supervision would ask here
Prepared answers, evidence-backed
- Every AI-assisted outcome at Noida Branch is written to the hash-chained ledger with the branch code attached, so a decision can be reconstructed years later.
- 260 calls were stopped at the gateway in the last 30 days — mostly PII in free-text notes typed at the teller desk.
- 1 violations are open and assigned to D. Shetty, with regulatory clocks tracked in the risk register.
- Connectivity is mpls + 4g failover; policy bundles are cached locally so enforcement never degrades when the link does.
Peers in Delhi NCR
Compare like-for-like before escalating