--- url: https://deepvue.ai/use-cases/screen-legal-risk/ title: "Screen for Legal Risk in India | Court, FIR, Sanctions | Deepvue" description: "Screen any India counterparty for legal risk in one decisioning call. Court records, FIR, sanctions, PEP, adverse media, and DPDP-aligned audit trail." last_modified: 2026-06-19T14:32:36.926Z --- 1. [Home](/) 2. Use Cases 3. Screen for Legal Risk Workflows  ·  Screen for legal risk # Screen any India counterparty for *legal risk* in one call. Court record search, FIR signal lookup, sanctions, PEP, adverse media — chained into one legal-risk decisioning call on individuals or entities. Built for legal, compliance, and M&A teams. One workflow, every screening context — counterparty, customer, partner, M&A target, regulator filing [Talk to a Specialist](/contact/) [Request a Demo](/demo/) ## One Workflow, *Every Legal-Risk Screen* Counterparty diligence, customer onboarding screen, M&A target review, partner contracting, regulator filing — the legal-risk decision chain is the same shape. Configurable per use-case. ![DollarPe](/logos/kyc/dollarpe.png) ![iMocha](/logos/kyc/imocha.png) ![Lark Finserv](/logos/kyc/lark-finserv.png) ![NAMCO Bank](/logos/kyc/namco-bank.png) ![Nest](/logos/kyc/nest.png) ![SafeTree](/logos/kyc/safetree.png) ![SwitchMyLoan](/logos/kyc/switchmyloan.png) ![Times Internet](/logos/kyc/timesinternet.png) ![Yenmo](/logos/kyc/yenmo.png) ![DollarPe](/logos/kyc/dollarpe.png) ![iMocha](/logos/kyc/imocha.png) ![Lark Finserv](/logos/kyc/lark-finserv.png) ![NAMCO Bank](/logos/kyc/namco-bank.png) ![Nest](/logos/kyc/nest.png) ![SafeTree](/logos/kyc/safetree.png) ![SwitchMyLoan](/logos/kyc/switchmyloan.png) ![Times Internet](/logos/kyc/timesinternet.png) ![Yenmo](/logos/kyc/yenmo.png) ![DollarPe](/logos/kyc/dollarpe.png) ![iMocha](/logos/kyc/imocha.png) ![Lark Finserv](/logos/kyc/lark-finserv.png) ![NAMCO Bank](/logos/kyc/namco-bank.png) ![Nest](/logos/kyc/nest.png) ![SafeTree](/logos/kyc/safetree.png) ![SwitchMyLoan](/logos/kyc/switchmyloan.png) ![Times Internet](/logos/kyc/timesinternet.png) ![Yenmo](/logos/kyc/yenmo.png) court records + FIR signals in one call structured + searchable, not PDF blobs UN, OFAC, EU sanctions + Indian PEP adverse media, multilingual entity OR individual screening recurring re-screen on schedule per-screen immutable audit trail court records + FIR signals in one call structured + searchable, not PDF blobs UN, OFAC, EU sanctions + Indian PEP adverse media, multilingual entity OR individual screening recurring re-screen on schedule per-screen immutable audit trail court records + FIR signals in one call structured + searchable, not PDF blobs UN, OFAC, EU sanctions + Indian PEP adverse media, multilingual entity OR individual screening recurring re-screen on schedule per-screen immutable audit trail ## Three reasons legal teams collapse risk screening into one call. Legal-risk screening in India breaks across three axes — coverage of fragmented court systems, speed (especially for M&A windows), and defendable audit. Deepvue's **screening chain** is built around all three, configurable per use-case. Every Indian court, one search 01 · Coverage Indian court systems are fragmented across Supreme Court, High Courts, district courts, tribunals. Manual searches miss. One unified search returns matches across all of them. Supreme + High + district courts unified NCLT + DRT + tribunals included FIR signal lookup where available M&A and contract-window-fast 02 · Speed External counsel diligence takes weeks. M&A timelines and contract windows don't wait. Parallel API screens return verdicts in minutes — defendable, with citations. Parallel court + sanctions + media calls Sub-minute decisioning for most screens Async webhook for slow court systems Per-screen citations + trail 03 · Audit Legal-risk screens need to be defensible. Every match cites case number, court, date. Every clear is timestamped against source. Audit-ready for board, regulator, or counterparty challenge. Citations on every match Source + timestamp on every clear Replayable trace per screen External counsel diligence is slow and expensive; ad-hoc court searches miss tribunals; sanctions screening is a separate vendor; adverse media is another. Deepvue collapses all of these into one screening call with citations. ## Why ad-hoc legal-risk screening misses signals. If your funnel is leaking 25%+ between "Apply" and "Approved" — or your audit team is rebuilding decision history from logs — here's where the breakage usually starts. Stitched-vendor onboarding Sequential KYC → face → bank calls, latency stacks PAN parsed as a string, not source-validated No bank ownership check — mule accounts slip through Audit trail across four systems, never reconstructable Deepvue onboarding chain Parallel KYC + face + bank + screening, single response PAN, GST, CIN validated against source registries Penny-drop bank ownership match before payout DPDP + RBI-aligned audit trail, single API export External counsel diligence taking weeks? 15-min walkthrough — bring a sample counterparty, leave with a side-by-side risk verdict + citations. [Talk to a Specialist](/contact/) [Request a Demo](/demo/) ## The screening chain — six primitives, one call. Every primitive a legal-risk screen needs, wired to call in parallel — configurable per use-case. Court record search Supreme Court, High Courts, district courts, NCLT, DRT, tribunals — unified structured search by name + identifiers. [Explore](/court-record-check-api/) FIR signal lookup FIR signal indicators where available. Configurable severity threshold per use-case (M&A vs. routine onboarding). [Explore](/fir-check-api/) Sanctions + PEP UN, OFAC, EU, UK sanctions + PEP database (incl. Indian-flagged PEPs). Structured risk indicators. Adverse media Multilingual adverse-media scan, English + major Indian languages. Categorised by risk type (financial, criminal, reputational). Entity registry signals CIN status, MCA charges, NCLT proceedings, regulatory enforcement actions on entities. [Explore](/company-verification-api/) Recurring re-screen Periodic re-screen on critical counterparties — court updates, sanctions delta, new media. Webhook on hit. ## How the screening chain runs. From a name + identifier to a defendable risk verdict with citations — a typical screening cycle. 01 Submit subject Name + identifier (PAN, CIN, Aadhaar) submitted. Use-case (counterparty, M&A, customer, partner) selects the ruleset. 02 Sources fan-out in parallel Court, FIR, sanctions, PEP, adverse media, entity registry — all queried concurrently. Slow sources go async. 03 Hits scored + cited Each match scored for relevance + severity. Citations attached: case number, court, date, source URL where available. 04 Verdict + audit logged CLEAR / REVIEW / FLAGGED with structured citations. Replayable trace. Audit-ready for board / regulator / counterparty. End-to-end median: **under a minute** for sync sources, async webhooks for slow court systems. 15-min walkthrough comparison available. Sub-minute legal-risk verdict, today. Test the full chain in our sandbox — court, FIR, sanctions, PEP, adverse media, verdict — before you wire anything in. [Talk to a Specialist](/contact/) [Request a Demo](/demo/) ## A legal-risk screening call, end-to-end. What a single legal-risk screen looks like — parallel sources, structured citations, replayable trace. The check chain CHAIN // Parallel + async, citations attached 1. POST /v1/legal/court-record-search 2. POST /v1/legal/fir-signal 3. POST /v1/screening/sanctions 4. POST /v1/screening/pep 5. POST /v1/screening/adverse-media 6. POST /v1/business/mca-charges 7. POST /v1/decision/legal-risk What you wire in Auth header single API key, all endpoints Subject inputs name, PAN/CIN/Aadhaar, optional DOB Webhooks decision events post back to your stack Decision rules severity thresholds per use-case Decision response 200 OK · JSON { "subject\_id": "sub\_8a4f2b9e", "verdict": "CLEAR", "sources": { "court\_records": "NO\_MATCH", "fir\_signal": "NO\_MATCH", "sanctions": "NO\_MATCH", "pep": "NO\_MATCH", "adverse\_media": "NO\_MATCH", "mca\_charges": "NO\_MATCH" }, "trace\_id": "trc\_2026\_04\_29\_17\_42", "compliance\_format": "DPDP\_v2", "data\_residency": "IN" } ## Compliance map for legal risk screening. The frameworks legal-risk screens get challenged on — DPDP, sanctions, AML, sectoral KYC — and which Deepvue capabilities map to each. DPDP DPDP Act, 2023 Digital Personal Data Protection. Consent, purpose limitation, data-fiduciary duties for all onboarded customers. RBI RBI Master Direction on KYC Defines acceptable KYC flows for Indian users. Aadhaar e-KYC, OVDs, video-KYC, periodic refresh. AML PMLA, 2002 Prevention of Money Laundering Act. Mandates customer due diligence, record-keeping, suspicious-transaction reporting for regulated entities. FATF FATF Recommendations R10 (CDD), R12 (PEPs), R16 (Travel Rule). Applies to financial institutions via home regulator. CONSUMER Consumer Protection Rules Marketplace + e-commerce: seller-due-diligence + grievance officer + return/refund disclosure obligations. IT ACT IT Act, 2000 (Sec 43A + 79) Reasonable security practices + intermediary safe harbour. Documented onboarding strengthens both. SCREENING UN, OFAC, EU sanctions Sanctions list screening at onboarding and monitored throughout the customer lifecycle. SCREENING PEP & Adverse Media Politically Exposed Persons screening per FATF R12. Adverse media flags reputational risk. This map is informational, not legal advice. Your specific licensing posture (NBFC, Bank, marketplace, gig aggregator) layers on top — Deepvue's audit trail is built to support all of them. ## Where legal-risk screens miss signals — and where Deepvue catches them. From submitted name to risk verdict — the missed signal usually fits one of these five patterns. Common miss patterns 1 — High Court / tribunal case missed (only district searched) 2 — FIR signal absent, criminal exposure undetected 3 — Sanctions hit found late (batch, not real-time) 4 — Adverse media in vernacular missed (English only) 5 — No defendable trail, finding overturned in dispute Deepvue runs all sources in parallel — Supreme + High + district + tribunals; FIR signals; UN/OFAC/EU sanctions in real-time; multilingual adverse media. Every match carries a **citation**, every clear carries a **source + timestamp**. Defendable to the board, regulator, or counterparty. Show me the screening report my GC will sign off on. 15-min walkthrough — bring a sample counterparty, leave with a side-by-side risk verdict + citations. [Talk to a Specialist](/contact/) [Request a Demo](/demo/) ## Wire it in over a coffee. Most legal + compliance teams drop the Deepvue screening chain into their workflow in **under a week**. One sandbox key, one chained endpoint, webhooks back to your CRM / contracting system. Day-by-day rollout 1 Day 1 — sandbox keys + sample request templates 2 Days 2-3 — wire into your contracting / CRM workflow 3 Days 4-5 — webhooks back to your decisioning + audit stack 4 Day 6 — production keys, go live with a small traffic split ## What you get out of the box. Capabilities every legal-risk screen needs — without coordinating outside counsel and three separate screening vendors. Integration features Single REST endpoint One chained call wraps the full onboarding flow. Sandbox first Run sample subjects end-to-end before any production traffic. Webhook decisioning Decisions, retries, and step-level events post back to your stack. Exportable audit trail Citations + source URLs per match, on-demand export. Out of the box Court records (unified) Supreme Court, High Courts, district courts, NCLT, DRT, tribunals — single search, structured response with citations. FIR signal lookup FIR signal indicators where available. Severity threshold tunable per use-case. Sanctions + PEP UN, OFAC, EU, UK sanctions + global + Indian-flagged PEP database. Real-time, not batched. Adverse media (multilingual) English + major Indian languages. Categorised by risk type — financial, criminal, reputational, regulatory. Citations + audit trail Every match cites case number, court, date, source URL. Every clear is timestamped against source. Replayable. Per-call trace ID Every decision tagged with a retrievable trace ID. Plug into your audit pipeline without custom logging. Ship sub-minute legal-risk screens in a week, not a quarter. Sandbox keys today. Production traffic by Friday next. [Talk to a Specialist](/contact/) [Request a Demo](/demo/) ## One workflow, five legal-risk contexts. Five use-case configurations — same chain, different thresholds and source weighting per context. Counterparty diligence Court + sanctions + media Pre-contracting screen on a counterparty entity + key directors. Standard severity threshold; clear / review / flag. M&A target review Deeper court + NCLT Heavier chain: full court history, NCLT proceedings, MCA charges, regulator enforcement, multilingual adverse media. Customer onboarding screen Light, fast, repeat Sub-minute screen at customer signup. Sanctions + PEP + recent court hits. Recurring re-screen on schedule. Partner / channel screen Standard + recurring Pre-onboarding screen on channel partners + agents. Periodic re-screen catches stale partners before brand exposure. Regulator filing prep Audit-ready bundle Pre-filing screen on directors / KMPs. Citations + structured trail bundled for the regulator package. ## Built to defend every screening verdict. DPDP, sanctions enforcement, AML, sectoral KYC, contractual representations — overlapping audit needs. Deepvue's per-screen citation + trail satisfies all of them. Screening commitments Citation + source URL on every match Per-screen audit trail, on-demand export Sources via authorized partner integrations Paperwork & controls SOC 2 Type II controls (in audit) ISO 27001 aligned GDPR-compatible DPA available Sub-processor list under MSA Deepvue is not a law firm and does not provide legal advice. Legal and compliance teams retain full responsibility for risk-acceptance decisions. Deepvue provides structured signals + citations; the legal interpretation and decision is yours. Applicable regulations All API interactions are protected using encryption, role-based access controls, and audit logging. ## Volume pricing per screen. Screening bundles tier with monthly screen volume. Pay per chained screen, not per individual source. INR-first invoicing. Pricing scales with monthly screens runprimitives per decision (3, 5, 7+)sources per screen (3, 5, 7+)dedicated SLA & support tierINR-first, USD on request Most legal + compliance teams running 100-50k screens per month land in a **per-screen** range materially under outside-counsel + multi-vendor stitching. No per-source surcharges. [Talk to a Specialist](/contact/) [Request a Demo](/demo/) ## Common questions from compliance and product leads. Real questions, asked in evaluation calls. If yours isn't here, book a 15-min walkthrough — we'll answer it live. We use external counsel for diligence. Why move to an API? External counsel adds judgment on top — keep them for that. The API replaces the slow + expensive raw-source pulling underneath. Most teams use the API to seed counsel's review with structured signals + citations, dropping diligence cycles from weeks to days. How comprehensive is the court-record coverage? Supreme Court, all High Courts, district courts via eCourts, NCLT, DRT, and major tribunals. Coverage gaps and source URLs surface in the response so reviewers know where signals come from. Can we screen entities + their directors in one call? Yes. Pass a CIN; the chain pulls director list from MCA and screens each director in parallel against court, sanctions, PEP, adverse media. Returned as a single nested verdict. Where is screening data stored? Indian servers by default. Storage arrangements are negotiated per MSA, with defaults aligned to DPDP and applicable sector regulations. Are findings legally defendable? Every match carries case number, court, date, source URL where available. Every clear is timestamped against source. Replayable trace per screen. Defendable to board, regulator, or counterparty — but legal interpretation is your team's call. How long does integration take? Sandbox in a day. Production wired into your CRM / contracting / ATS workflow inside 1-2 weeks for most teams. ## How does Deepvue's "Screen for legal risk" workflow compare to outside-counsel diligence? **Deepvue**'s legal-risk screening chain runs unified court record search (Supreme + High + district + NCLT/DRT/tribunals), FIR signal lookup, UN/OFAC/EU sanctions, PEP database, multilingual adverse media, and MCA charges + entity status in one parallel API call — with citations on every match. External counsel diligence cycles take weeks; this returns a sub-minute structured verdict that legal teams use to seed counsel review or directly clear/flag counterparties. Configurable per use-case: counterparty, M&A, customer onboarding, partner, regulator filing. ## Screen any India counterparty in under a minute. Court + sanctions + media + entity registry. Citations on every match. [Talk to a Specialist](/contact/) [Request a Demo](/demo/)