Solution for compliance and KYC
KYC that sees beyond the score
Court history as a primary due diligence signal. Vigilant cross-checks the full judicial footprint of any CPF/CNPJ in seconds, with an audit trail ready for compliance and LGPD.
What traditional KYC misses
Bureau score ≠ real risk
A counterparty with a clean score can have 30 active labor claims and an ongoing tax enforcement. The score misses it — the court history catches it.
Counterparty "active" at the IRS, litigious in court
Federal IRS status is checked in almost every KYC, but says nothing about the counterparty's litigation pattern in the last 5 years. The court does.
Audits demand a trail that spreadsheets can't provide
Central bank (Bacen), CVM, and internal audit require documentary evidence of due diligence. Manual lookups on tribunal websites leave no auditable record.
How it fits into your KYC workflow
API called on onboarding/renewal
Your KYC/AML flow calls Vigilant with the counterparty's CPF or CNPJ. Response in seconds, ready for the decision engine.
Structured judicial history
Active and passive cases by instance, area, and court. Litigation patterns, tax enforcements, and labor liabilities surfaced.
Auditable log per query
Each call generates a timestamped record with consulted CPF, source, response, and user. Ready for compliance and regulatory audit.
The numbers that matter for compliance
12
Court sources
Federal + 10 states covering ~70% of volume
<60s
Per query
Vs 30min manual research
100%
Queries with audit trail
LGPD + regulatory record
R$ 0.10
Per court queried
No minimum, no commitment
Court history as a primary due diligence signal. Vigilant cross-checks the full judicial footprint of any CPF/CNPJ in seconds, with an audit trail ready for compliance and LGPD.
Score-only KYC vs judicial-history KYC
- Bureau score + IRS status as baseline
- Judicial history ignored or consulted ad hoc
- Diligence evidence via screenshots and spreadsheets
- "Clean" counterparty with 30 active claims slips through
- Regulatory audit becomes a recurring pain
- Full judicial history cross-checked in the flow
- Litigation, tax enforcement, and labor liabilities visible
- Audit trail per query, exportable to regulator
- Aggregated patterns (habitual litigant) identified
- Diligence evidence ready-to-regulator
Plugs into your compliance stack
REST API standardized on OpenAPI 3.1. Integrates with any KYC/AML platform that consumes external APIs — or runs straight from your internal engine.
Architecture compatible with KYC/AML, Due Diligence, and Enhanced Due Diligence (EDD) workflows. Documentation and examples at vigilant.trackjud.com.br/api/docs.
Frequently asked questions
Legitimate interest (art. 7 IX of LGPD) and, when applicable, compliance with legal obligation (Bacen Circular 3.978, AML Law 9.613/98). Court data comes from public tribunal sources. We keep consent records plus a per-request audit trail.
Every query generates an immutable record with: timestamp, consulted CPF/CNPJ, API user, source IP, accessed source(s), and returned response. Exportable via API or dashboard for regulatory audit.
Yes. The circular requires diligence proportional to counterparty risk. Vigilant serves as input for Enhanced Due Diligence on PEP or high-risk counterparties, complementing (not replacing) your compliance assessment.
Court data stays in cache for up to 2 days and is automatically refreshed. Audit logs are retained for 10 years (Bacen standard) or per your enterprise contract.
Enterprise contracts include 99.5% SLA, dedicated rate limits, regional endpoint, and 24x7 support. Talk to sales for sizing.
Strengthen your KYC with judicial history?
Start free with 5 credits. No credit card. For banks, fintechs, and insurers, book a compliance call with our team.