Run Detekta as your full platform, or alongside the stack you already have. Brazilian data, entity and team on the ground; the same orchestration scales across the region when you are.
A pattern shows up across the Brazilian fintech, crypto and payments segment. These are the signals we have observed. We would like to hear which ones match your reality.
Every Brazilian user onboarded by passport must re-submit RG or CNH by 25 June. A passport shows citizenship origin, not fiscal residence. In Brazil the tax ID is the only enforceable key.
Global watchlists publish around 4 million records worldwide · less than half of São Paulo city alone. Brazilian users frequently trigger false positives that local data resolves in seconds. The manual review backlog grows.
Re-screening millions of existing users requires querying by CPF or CNPJ alone, without a fresh document ceremony. Most KYC tools were built for onboarding, not the long tail of ongoing review at scale.
PEPs from the federal CGU registry, judicial process via CNJ, negative media in Portuguese, UBO mapping from official sources. Global tools treat Brazil as one of 200 countries.
Authority-grade evidence in Brazil, continuous review by tax ID, local sanctions and PEP, investigation depth. All auditable. All ahead of the BCB authorization window.
Brazil moved virtual-asset providers into the financial system. The new rules reward exactly the model we run: continuous monitoring over periodic reviews, tax-ID-bound diligence, and beneficial-owner depth.
BCB 519/2025 is live. VASPs (SPSAVs) are now part of the Sistema Financeiro Nacional, supervised by the Banco Central.
The norm replaces periodic reviews with active, continuous monitoring. That is OCDD · exactly what Model A delivers.
Authorization must be filed by end of October 2026. After 30 Oct, authorized firms cannot transact with unregulated entities.
| The obligation | How Detekta delivers |
|---|---|
| Continuous active monitoringreplaces periodic reviews | ✓ OCDD: re-screening of the existing base by CPF / CNPJ, in real time, with no fresh document ceremony. |
| PEP · sanctions · adverse media | ✓ BR (CGU, Lei 13.810) plus OFAC / UN / EU, and Portuguese named-source media, namesake-excluded. |
| Beneficial owner (UBO)natural person over 25% for PJ | ✓ Corporate-tree mapping to the controlling person, kept current as part of ongoing diligence. |
| Risk-based approach (ABR)documented and auditable | ✓ Risk scoring per subject with a full, examiner-ready audit trail behind every decision. |
| CPF-bound attributionthe namesake control that fails today | ✓ Court data (CNJ) is not CPF-indexed by law · our engine binds every finding to the tax ID and excludes namesakes. |
| STR to COAF / UIFwithin 24h of detection | ✓ Flagged subjects packaged with the investigation dossier, ready to file. |
Detekta is an orchestration layer, not a single-provider KYC tool. It runs as a parallel layer to your existing flow and routes every check to the right source by jurisdiction, document type and risk. Global vendors handle global. Local sources handle local. The platform decides.
Detekta routes each check to the best source by jurisdiction, document type and risk, fires them in parallel, and resolves one verdict with one audit trail. Your existing KYC stays in the loop.
One workspace. One decision per case, every source behind it, every step auditable.
Validated vs Receita in 1.2s.
Serpro DatavalidLiveness 98.7%, face 96.4%.
UnicoCGU plus OFAC / UN / EU. No hit, namesake excluded.
CGU · global listsCNJ DataJud, all courts. No active case.
CNJ DataJudApprove. 38s end to end. Full trail captured.
DetektaA name-only watchlist hit is noise. Real Brazilian compliance separates the signal: it binds findings to the tax ID, verifies them on official court portals, and excludes namesakes. Here is a real Detekta due-diligence report · redacted · on a high-risk subject.
AUSTRAC holds Australian identity and beneficial-ownership data the way Receita, CGU and CNJ hold it in Brazil. Most global vendors skip that depth. We did the work. Figures below are from a regulated payment facilitator across five markets.
Before: 4 KYC/KYB vendors, 2 transaction-monitoring engagements, outsourced AML training. AUD 197K annual spend, fragmented data, 30% straight-through.
After: one Detekta workflow orchestrating 10 providers incl. direct government-registry integrations. Multi-market residency built in.
Australia and Brazil share the same dynamic: the regulator holds the data, direct integration is required, and global vendors skip the depth.
AU sources: AUSTRAC, ABR, ASIC, OAIC. BR sources: Receita Federal, CGU, CNJ, COAF. The orchestration architecture is what made it possible.
Most vendors hand you their flow and ask you to retrofit. Detekta runs as a parallel layer that mirrors your journey, on your policy.
Users see Bybit, never Detekta. We mirror your screens, tone and decisioning order on a smarter backend.
You write the rules, we execute them. Smart routing is configurable, transparent and auditable end to end. One toggle per policy decision.
Webhooks into your event bus, cases into your ticketing, decisions into your warehouse. We connect, we do not replace.
A dedicated implementation engineer from day one. Direct channel, same timezone. No tier-1 ticket queue.
If your onboarding takes seven steps today, Detekta delivers a seven-step Bybit flow tomorrow. Not a vendor template. A Bybit flow, on a smarter compliance backbone.
This is a Brazil proposal. We earn the right in Brazil first, with a local entity, team and data. The same platform expands to Latin America and the world the moment Bybit does · no new vendor, no new procurement cycle.
One platform, one contract, one implementation team. We are not flying in to sell and disappearing · our Latin American posture is permanent.
Detekta was founded by Brazilians, headquartered in Australia, built for global delivery. The Brazilian commitment is already in place: infrastructure, team and entity.
Brazilian client data hosted in AWS São Paulo. ANPD Standard Contractual Clauses in place. LGPD aligned with BCB Resolution 4658 posture.
Engineering team in Brazil supporting deployments. Direct line to product for integration questions and field-level customization.
Local account management for Brazilian and Latin American clients. Same-timezone support for Brazilian operations.
Detekta Brasil entity in operation. Local contracting, billing in BRL, tax residency in country. Direct contracts with Brazilian providers.
"Detekta is founded by Brazilians. Our Latin American posture is permanent, not opportunistic. We are not flying in to sell and disappearing."
Two distinct models, exactly as we framed them with you. Model A, a specialist depth layer alongside your stack, or Model B, Detekta as your primary compliance platform. Either one scales across Latin America when you are.
Brazilian judicial proceedings, regional Portuguese media, consolidated COAF / UN / OFAC / EU lists, and PEP family-tree analysis · the depth a global-only stack misses in Brazil.
CPF-bound, court-verified due-diligence dossiers on flagged subjects · the redacted DD report you already have, on demand.
For cases your stack flags incomplete or fails. Run directly against Datavalid, Receita, BigDataCorp and Serasa · returned fully resolved.
Periodic re-screening of your Brazilian base by CPF / CNPJ, if in scope. Continuous, with no fresh document ceremony.
Our rates are fixed and step down with volume. Set your scenario above · the figures update on the right.
Model A · US$ 2.50 to 1.50 per check (500K to 2M). Completion billed only when actioned.
We do not want to push for a specific commitment today. Here are options that might fit, depending on what makes sense after this conversation.
Another working session on the specific pain points or use cases that came up here. Useful if there is more discovery before specifics.
A walkthrough of the orchestration layer on a real Brazilian KYC or KYB scenario you describe. Roughly 30 minutes. We prepare sample data on your use case.
A meeting with your KYC engineering team to map fields, latency and integration. Outcome: a draft integration spec within 48 hours and sandbox access.