Resold by Frayme. No client API key required. Credentials and billing are managed end-to-end.
What it returns
| Signal | Detail |
|---|---|
| CPF / CNPJ validation | Registry status (situação cadastral), full canonical name, date of birth. |
| Address history | Last N declared addresses + geocoding, with timestamps. |
| Related parties | Family (spouse, parents, siblings), business partners, declared associates. |
| Employment & income | Eyes on RAIS / eSocial signals where available. |
| Lawsuits, debts & protests | Civil suits, labour suits, criminal record exposure, debt registries (SPC/Serasa adjacency), notarial protests. |
| Email & phone reputation | Known bindings, signal age, abuse markers. |
| Digital footprint | Social-media presence, leaked-credential exposure, scoring. |
Use across Frayme workflows
Natural-person KYC enrichment
Natural-person KYC enrichment
Called immediately after the address-rewrite branch. Output is fed to the AI Risk Synthesis node alongside Sumsub identity + AML.Used as the Brazil-specific complement to Sumsub: CPF registry status, lawsuits, related parties, digital footprint. Forms part of the natural-person risk band.
KYB UBO background
KYB UBO background
Brazil-jurisdiction-only branch. For each declared UBO (by CPF), pulls PEP + sanctions + lawsuits + corporate links. Output is fed to the Corporate Risk Synthesis alongside Sumsub KYB.Foreign-jurisdiction companies skip BDC and go through AI documentary review instead.
Counterpart background (transaction monitoring)
Counterpart background (transaction monitoring)
Paid-per-query rule for high-risk PIX originators. After DICT resolves the counterpart CPF/CNPJ, BDC enriches it. Output feeds the alert plus any downstream regulator-report narrative.
Rate-limit posture
Frayme caches BDC responses by CPF/CNPJ for 24h to avoid duplicate paid queries during multi-step workflows. Cache is invalidated on:- Operator-issued refresh from the Decision Console.
- Inbound BigDataCorp webhook indicating record change.
- Per-rule TTL override (counterpart enrichment has a tighter 1h cache because counterparts churn faster than applicants).