Skip to content

A product by Paiva Gomes Advogados

Clav
Brazilian Regulatory Compliance

Everything your VASP needs

Clav brings your VASP's regulatory work into one platform, from Banco Central authorization to the routine that comes after it.

Clav Dashboard Preview
Compliance management

Compliance designed to operate continuously

We structure requirements, verify evidence and keep your operation's compliance running continuously.

Controls in operation

We define and organize the compliance structures applicable to your VASP operation, with clear requirements, traceable scope and well-defined regulatory base.

Protocol Submission
Pre-Protocol
Protocol Submission
Phase 1
Recurring Report
BCB Phase 1 Decision

Regulatory Framework for Virtual Asset Service Providers

We structured and implemented a comprehensive regulatory framework for virtual asset service providers (VASPs), aligned with the requirements of the Central Bank of Brazil and international best practices.

Evidence completion
35%

of C-VASP Authorization Process evidence are passing

Automated tests
78%
Documents
6%
Control status
35%

of C-VASP Authorization Process evidence are passing

Ok
3
Needs evidence
13

Verifiable evidence

We centralize documents, tests and other compliance evidence, linking each delivery to the corresponding requirements in a verifiable way.

Evidence completion1/4 evidence completed
38%
  • CompletedRisk Management Structure (Market, Credit, Operational, Liquidity)
  • In ReviewCybersecurity Policy + Incident Response + Cloud Computing Service Contracting
  • PendingAML/CFT Policy and Procedures + Internal Controls
  • PendingBusiness continuity plan

Living policies

We monitor progress, pending items and deviations so that your operation remains in permanent compliance ready for auditing at any time.

Overall Progress
21%
3 / 17 Requirements
Submission Deadline
9 Months
Deadline:29/10/2026
Risk Level
Medium
Based on compliance status
Clav Dashboard

Regulatory base

We organize and structure all the regulatory requirements of your operation in a single system, with clear scope, dependencies and continuous progress.

Tests and validations

We run automated and manual compliance tests, with approval traceability, exception management and deviation monitoring.

Clav's content and legal frameworks produced by Paiva Gomes Advogados

Paiva Gomes Advogados

Co-founders: Eduardo de Paiva Gomes · Daniel de Paiva Gomes

Clav AI Assistant

Ask about your compliance work and the norms behind it

Clav AI Assistant reads your frameworks, evidence, deadlines and certification review, plus the official text of the norms your frameworks cite. It answers with links to each evidence, reviews documents against their requirement and only changes something after you confirm.

Questions about your own work

What is left for me, how each framework is going, which evidence is overdue, what a colleague did this week. Every evidence in the answer is a link that opens it.

The norm behind each requirement

It reads the official text of the resolutions, normative instructions and laws your frameworks cite, article by article, and says when an article is about to change.

Document review

Compares the attached files with the requirement and the expected evidence. Findings are graded blocking, warning or informational and quote the passage and page.

Changes only after you confirm

It can fill in an information evidence, attach a link, duplicate an evidence or remember a fact for the organization. Each change shows up as a card, and nothing is written until you click Confirm.

See how Clav AI Assistant works

Files stored with client-side encryption can't be reviewed, because the server can't read them.

Clav AI Assistant

What does the regulation say about keeping customer assets segregated?

Reading the norm

BCB Resolution 520/2025 covers it in a few articles:

  • Art. 28: customer funds stay in individual payment or deposit accounts, apart from the provider's own
  • Art. 29: the provider's own virtual assets stay apart from its customers'
  • Art. 30: the segregation is set out in a policy, with proof of reserves and an independent audit

Related evidence in your framework: A.1 Asset segregation policy

Wallet verification

Proof of who owns each self-custody wallet

Before you release a withdrawal to an external wallet, send your customer a verification link. The result is stored in Clav with the full history of the request.

1

Create the request

In the dashboard or through the API, enter the network, the address and your customer's ID. Clav generates a verification link.

2

Your customer signs

The link opens a page with your name and logo. The customer signs a message with the wallet, which costs nothing, moves nothing and gives no one access to the wallet.

3

The wallet is verified

The address shows up as verified in Clav, with every attempt recorded. Your systems receive a signed webhook.

Supported networks

  • Ethereum
  • Polygon
  • Arbitrum
  • Optimism
  • Base
  • BNB Smart Chain
  • Avalanche
  • Bitcoin
  • Solana
  • Tron

Mainnet only. Test networks are rejected.

How your customer can prove ownership

  • Wallet connection via WalletConnect
  • Manual signature, for hardware wallets and command-line tools
  • Bitcoin micro-transaction, from 546 to 2,000 sats
  • REST API with a dedicated token scope
YE
Your Exchange
Prove this wallet is yoursIt costs nothing, moves nothing and gives no one access to your wallet
NetworkEthereum
Address0x71C4…9A3f
Waiting for signature
Wallet verified
Regulatory reports

CCS and ACAM212 generated, validated and sent by Clav

Each file comes from your VASP's own data, and every deadline shows up on a calendar. The reports live next to the rest of your compliance work, with the same team and access controls.

Choose how it runs: on your infrastructure or managed by Clav

Files ready in the right layout

Clav builds each file from your VASP's customer and transaction data, in the format the Banco Central expects.

Checked before it goes out

Errors and inconsistencies show up before submission, while there is still time to fix them.

Sent from Clav

The validated file goes to the Banco Central without leaving the platform, and every submission stays in the history.

Deadlines in one calendar

The team sees what is due and when, gets reminders before each deadline and can look up everything already sent.

CCSNational Financial System Customer Registry
Regulation
Resolução BCB 179/2022
Frequency
Whenever a customer relationship starts or ends
ACAM212Document C212: virtual asset services in the FX market
Regulation
IN BCB 693/2025
Frequency
Monthly, by the 5th of the following month
Delivery
XML file through the STA
Security

Built for regulated data

Controls your security team usually asks about when assessing a vendor.

Client-side encryption

Optional. Files are encrypted in the browser with AES-256-GCM before upload, so the server stores content it can't read.

SSO with SAML and OIDC

Connect your identity provider and require SSO for every member of the organization.

Two-factor authentication

Authenticator app with backup codes. Administrators can make it mandatory for the whole organization.

Audit log

Changes to keys, members, SSO and security settings are recorded along with who made them.

API with scoped tokens

REST API with per-scope tokens, rate limiting and an access log, documented in OpenAPI.

Portal for auditors

Audit firms get their own portal to read evidence and approve it or request changes, only in the organizations they certify.

Technical

Technical foundations of Clav

A technical overview of how Clav ensures security, compliance and data integrity in regulated operations.

Auditable

Transparency and audit

We believe in transparency. Our technical documentation is publicly available so you can understand exactly how we protect your data and maintain compliance.

See all documentation
FAQ

Frequently asked questions

Compliance management for Banco Central frameworks, Clav AI Assistant for questions about your work, the norms behind each requirement and document review, and verification that a self-custody wallet belongs to your customer. Clav also generates and sends CCS and ACAM212 to the Banco Central. Everything runs on the same account, with the same team and access controls.

It builds the CCS and ACAM212 files from your VASP's data, validates them before submission, sends them to the Banco Central and tracks each deadline. ACAM212 is the monthly C212 document set by IN BCB 693/2025, due by the 5th of the following month.

What is left for you, how each framework is going, which evidence is overdue, what the auditor asked and what a norm cited by your framework says. It answers with links to each evidence and the article it relies on, and any change it proposes waits for your confirmation.

It compares the attached files with the requirement and the expected evidence and lists what is missing or inconsistent. Each finding quotes the passage and the page it relies on, and your team decides whether to apply it.

No. With client-side encryption on, the server can't read the document, so the review isn't available for those files. Files kept in the default storage mode can be reviewed.

Ethereum, Polygon, Arbitrum, Optimism, Base, BNB Smart Chain, Avalanche, Bitcoin, Solana and Tron, on mainnet. Your customer can sign through WalletConnect or paste a signature made elsewhere, and on Bitcoin there is also a micro-transaction option.

No. Signing a message costs nothing, moves no funds and gives no one access to the wallet.

With evidence continuously collected and organized, your company is always ready for audits. No more scrambling to gather documents at the last minute.

Live and running in production

One account for all of your VASP's regulatory work

Request access and tell us which products your operation needs. We turn on the ones you choose.