Por que Bancos Brasileiros Bloqueiam Contas por Crypto: Bacen Compliance e AML Review

Quando Itaú bloqueia sua conta por “movimentação atípica”, ou Banco do Brasil suspende PIX por “operations inconsistent with profile”, o que realmente está happening? Banks não bloqueiam arbitariamente — existe framework regulatório e institucional que drive these decisions.

Entender por que bancos bloqueiam é first step para prevent bloqueios. Este artigo analyses cada component: Bacen regulations, Coaf reporting, bank internal policies, and how they intersect to create bloqueio triggers for crypto users.

O Framework Regulatório

Bacen Circular nº 3.978/2020

O Banco Central do Brasil (Bacen) emitiu Circular 3.978 em agosto 2020, establishing comprehensive framework for AML/CFT (Anti-Money Laundering/Combating Financing of Terrorism) compliance.

Key requirements for banks:

1. Política de Prevenção: cada banco deve ter written policy for identifying and reporting suspicious activity
2. KYC Enhanced: banks must enhanced-diligence clients with “higher risk” profiles — including clients with crypto-related activity
3. Monitoring Systems: banks must implement automated monitoring for atypical transactions
4. Reporting: suspicious activity must be reported to Coaf within 24 hours
5. Record Keeping: all client data and transaction records must be maintained for 5+ years

Impact on crypto users: Circular 3.978 classifies crypto-related activity as “higher risk” category — banks must apply enhanced monitoring and diligence to clients who transact in crypto.

Coaf (Conselho de Controle de Atividades Financeiras)

Coaf is the Brazilian financial intelligence unit — receives reports from banks about suspicious activity and coordinates with law enforcement.

Reporting thresholds:

• Any suspicious activity: bank must report regardless of amount
• Transactions > R$ 10.000: automatic flag in monitoring systems
• Pattern anomalies: multiple small transactions that appear structured (structuring/smurfing)
• Cross-border: international transfers trigger additional scrutiny

What Coaf does with reports:

• Analysis: reviews report, compares with other reports, identifies patterns
• Investigation: may request additional information from bank or client
• Sharing: shares with law enforcement if criminal activity suspected
• No direct action: Coaf doesn’t block accounts — they report, banks block

Key insight: Coaf reporting is mandatory for banks — banks cannot choose not to report. If monitoring system flags transaction, bank must report to Coaf. This creates strong incentive for banks to block proactively (prevent future flags) rather than wait for Coaf instructions.

Lei 9.613/98 (Lei de Lavagem de Dinheiro)

The AML law establishes criminal penalties for money laundering and requires financial institutions to cooperate with prevention efforts.

Relevance for crypto users:

• Banks must identify clients and verify source of funds
• Crypto transactions can be flagged as “potential laundering” without evidence — bank’s interpretation
• Banks are penalized if they fail to report suspicious activity — R$ 200.000+ fines
• This penalty risk creates incentive for banks to be over-cautious — blocking accounts proactively

Bank Internal Policies: Why Each Bank Behaves Different

Banco do Brasil (BB)

Policy: Most restrictive for crypto

• TED to international exchanges: frequently blocked — BB considers crypto exchanges “high risk institutions”
• PIX pattern monitoring: BB flags PIX patterns consistent with P2P crypto trading
• Account suspension: BB has suspended accounts for sustained crypto activity
• Rationale: BB is public bank — more regulatory scrutiny, less risk appetite for crypto

Trigger threshold:

• Single TED > R$ 5.000 to exchange CNPJ: likely block
• PIX pattern > 5 PIX/week to different CPFs: possible flag
• Cumulative crypto-related PIX > R$ 30.000/month: probable investigation

Itaú Unibanco

Policy: Very restrictive

• TED to exchanges: blocked with high probability
• PIX monitoring: sophisticated pattern detection — flags regular PIX to different recipients
• Enhanced KYC: may request client visit branch for “profile review”
• Account restrictions: PIX limits reduced, TED requires pre-approval

Trigger threshold:

• Any TED to known exchange CNPJ: likely block
• PIX pattern > 3 PIX/day to different recipients: flag
• Monthly PIX volume > R$ 20.000: enhanced review

Bradesco

Policy: Moderate restriction

• TED to exchanges: sometimes blocked, depends on amount and frequency
• PIX: less aggressive monitoring than BB/Itaú
• Client communication: more likely to contact client before blocking
• Documentation request: may request explanation before action

Trigger threshold:

• TED > R$ 10.000 to exchange: possible block
• PIX pattern suggesting P2P: flag but not immediate block
• Cumulative > R$ 50.000/month: review

Santander

Policy: Moderate restriction

• TED: may block large international transfers
• PIX: moderate monitoring
• Proactive communication: tends to contact client before blocking
• Documentation: accepts crypto transaction explanation

Trigger threshold:

• TED > R$ 15.000 to exchange: possible review
• Regular P2P pattern: monitoring but not immediate block
• Very high volume: investigation

Nubank

Policy: Least restrictive (most crypto-friendly)

• PIX: minimal monitoring of crypto-related patterns
• TED: allows TED to exchanges (within daily limit R$ 20.000)
• Account blocking: rare for crypto activity alone
• Communication: transparent if issues arise

Trigger threshold:

• PIX > R$ 50.000/month: possible review
• TED > R$ 20.000/day: limit (not block)
• Extreme patterns: investigation (very rare)

Inter

Policy: Crypto-friendly

• TED: allows TED to exchanges without issues
• PIX: minimal crypto-specific monitoring
• Account blocking: almost never for crypto alone
• Customer support: helpful for crypto-related questions

Trigger threshold:

• Very high volume only: investigation
• No specific crypto triggers

What Triggers a Block: Pattern Analysis

Pattern 1: Regular PIX to Multiple Different CPFs

Looks like to bank:

• PIX to 10+ different people per month → possible money laundering, structured transactions
• Bank sees: money going out to many recipients — inconsistent with normal salary earner

Why crypto users do this:

• P2P trading on Gate.io — each purchase/sale involves PIX to different merchant
• Normal crypto behavior looks abnormal to bank monitoring

Solution:

• Use same merchant repeatedly (favorite merchants)
• Limit number of different PIX recipients per month (<5)
• Larger individual transactions instead of many small ones

Pattern 2: PIX Amounts Just Below Thresholds

Looks like to bank:

• Multiple PIX of R$ 4.900, R$ 9.900, R$ 29.900 — suspiciously close to R$ 5.000, R$ 10.000, R$ 30.000 thresholds
• “Structuring” (smurfing) — deliberately avoiding reporting thresholds

Why crypto users might do this:

• Trying to stay under per-transaction limits
• Not deliberately structuring — just being cautious

Solution:

• Don’t make transactions at suspicious thresholds (R$ 4.900, R$ 9.900)
• Use natural amounts (R$ 3.000, R$ 5.000)
• Vary amounts slightly — R$ 2.850, R$ 3.200, R$ 1.500

Pattern 3: Rapid In/Out PIX Pattern

Looks like to bank:

• PIX receives R$ 5.000 → immediately PIX sends R$ 5.000 → receives R$ 3.000 → sends R$ 3.000
• “Pass-through” behavior — money laundering pattern

Why crypto users do this:

• Buy USDT (PIX out) → sell USDT (PIX in) → buy again (PIX out)
• Normal P2P trading creates in/out pattern

Solution:

• Space transactions over days, not hours
• Don’t buy and sell same day
• Keep USDT on Gate.io for days/weeks between buy and sell

Pattern 4: TED to Known Exchange CNPJ

Looks like to bank:

• TED to CNPJ associated with international crypto exchange
• Bank has list of exchange CNPJs — automatic flag

Why crypto users do this:

• Depositing BRL to exchange via bank transfer

Solution:

• Use PIX P2P instead of TED to exchange
• If TED needed, use crypto-friendly bank (Inter, Nubank)
• Declare purpose proactively to bank before TED

Pattern 5: Unusual Volume for Profile

Looks like to bank:

• Client with salary R$ 5.000/month moves R$ 30.000/month in PIX
• Volume inconsistent with declared income

Why crypto users do this:

• Crypto trading adds transaction volume beyond salary level
• Investment capital from savings, family, or previous crypto gains

Solution:

• Declare crypto activity and capital in IRPF
• Provide source documentation if bank asks
• Don’t exceed reasonable volume relative to declared income

The Bank’s Decision Process

When monitoring system flags transaction:

1. Automated flag: system identifies pattern anomaly → creates alert
2. Analyst review: AML analyst reviews alert — determines if suspicious
3. Enhanced diligence: if suspicious, analyst requests client information
4. Risk decision: analyst determines risk level — low/medium/high
5. Action:
   • Low risk: no action, flag closed
   • Medium risk: restrictions applied (PIX limits, enhanced monitoring)
   • High risk: account blocked, Coaf report filed
6. Client notification: bank should notify client (often doesn’t until client discovers)

Timeline: 1-3 days from flag to action for medium/high risk decisions.

How to Reduce Block Probability

1. Use Crypto-Friendly Banks

• Primary: Nubank, Inter — least restrictive
• Avoid: BB, Itaú for crypto transactions — most restrictive

2. Reduce Transaction Patterns

• Use same merchant (favorite) for P2P — fewer different PIX recipients
• Space transactions over days — not rapid in/out
• Natural amounts — not threshold-adjacent values
• Volume proportional to declared income

3. Use P2P Instead of TED

• PIX P2P to CPF individual — less monitored than TED to CNPJ
• P2P looks like normal person-to-person PIX

4. Declare Everything

• Declare crypto in IRPF annually
• Inform bank of crypto activity if asked
• Have documentation ready — source of funds, Gate.io history, employment proof

5. Multi-Bank Distribution

• Spread crypto transactions across 3 banks
• Each bank sees lower volume — below thresholds
• If one blocks, others still operational

Conclusão

Bancos bloqueiam contas crypto por combination de regulatory compliance (Bacen Circular 3.978), AML procedures (Coaf reporting), e internal risk policies. Understanding these mechanisms allows strategic behavior that reduces block probability.

Key strategies: use crypto-friendly banks (Nubank, Inter), reduce pattern triggers (same merchant, spaced transactions, natural amounts), prefer P2P over TED, declare crypto in IRPF, and distribute across multiple banks.

Prevention is 10× easier than resolution — implement strategies before block happens.

CTA

Prevent bloqueios operando strategically. Registre-se na Gate.io, use P2P com PIX em bancos crypto-friendly, e mantenha documentation para desbloqueio rápido se necessário.

Gate.io注册链接