P2P & OTC Crypto Address Verification

Peer-to-peer and over-the-counter crypto trades move billions monthly through Telegram groups, Binance P2P, LocalCoinSwap, and private desks. Every trade shares one property: final settlement is irreversible. P2P OTC verification means validating the counterparty's wallet address, on-chain history, and stated source of funds before you release bank transfer, cash, or crypto.

P2P vs OTC: same verification principles

P2P typically means retail-scale trades on marketplace platforms or informal chats — individuals buying $500–$50,000 of USDT with local payment rails. OTC (over-the-counter) usually describes negotiated block trades between parties, often with minimum tickets of $25,000 or more and relationship-based pricing.

The compliance stakes scale with size, but the verification checklist is identical: confirm address ownership, screen AML risk, match chain and asset type, and document the trade. A $800 P2P scam hurts; a $200,000 OTC mistake can end a business.

Why address verification is not optional

Crypto scams in P2P channels follow repeatable scripts:

• Mule addresses — Seller gives you a wallet recently funded from hacked exchange accounts. You pay fiat; victim's lawyers trace your inbound transfer.
• Chain mismatch — Buyer sends ERC-20 USDT to your TRC-20 address. Funds burn.
• Impersonation — Attacker intercepts chat and substitutes their address for the legitimate desk's wallet.
• Triangulation fraud — Scammer uses your fiat to pay another victim's invoice while routing crypto through you as an unwitting layer.
• Sanctions exposure — Counterparty wallet linked to SDN-listed entities exposes you to legal and banking risk when you interact.

Platform escrow protects some P2P flows, but off-platform settlement — common in OTC — removes that safety net. Your only technical defense is rigorous address verification before payment.

The verification checklist

Run this checklist for every new counterparty. Store results in your trade log.

1. Identity and channel integrity

Confirm you are speaking with the same entity across sessions. Use PGP-signed messages, verified exchange merchant badges, or voice verification for large OTC. Never trust addresses forwarded in screenshots — demand copy-paste text or QR you scan yourself.

2. Address format and chain

Bitcoin: native segwit (bc1), nested segwit (3), or legacy (1). Ethereum and EVM tokens: 0x plus 40 hex characters. Tron USDT: T prefix. Solana: base58 public key. One wrong character loses funds.

3. Ownership proof

Ask the counterparty to sign a short message with the private key controlling the address — "I control wallet 0x… for OTC trade dated 2026-06-09." Verify the signature locally. This prevents address substitution attacks mid-chat.

4. AML / KYT screening

Paste the address into a screening tool. Review:

• Direct sanctions / SDN matches (hard stop)
• Mixer hop distance and indirect exposure percentage
• Labels: scam, ransomware, stolen funds, darknet market clusters
• Address age and transaction pattern (fresh wallet vs established OTC desk)

Elevated risk does not always mean cancel — but it demands enhanced due diligence and a written source of funds explanation from the counterparty.

5. Source of funds narrative

Technical screening shows graph risk; documentation shows business logic. For OTC, request invoice, contract, or exchange withdrawal history supporting why they hold the asset. Mismatched stories — "salary" wallet with peel-chain inflows from gambling clusters — are red flags.

6. Test transaction (optional)

For large trades, agree on a $50–$500 test leg both ways before main settlement. Confirms routing, block times, and counterparty responsiveness.

Platform P2P vs off-platform OTC

Binance P2P, OKX P2P, and similar venues hold fiat in escrow until crypto confirms. You still should screen the crypto address you receive — inherited taint can affect your next CEX deposit even if the P2P leg completed successfully.

Off-platform OTC removes escrow. Common pattern: wire USD to a corporate account, receive USDT TRC-20 within minutes. Verification order:

1. Screen USDT receiving address before wire.
2. Confirm corporate account matches verified OTC desk entity.
3. Wire with explicit trade reference.
4. Monitor Tron blockchain for inbound USDT to your screened cold wallet — not an address the desk "just created."

Receiving crypto as a seller

If you sell BTC for bank transfer, screen the buyer's sending address before accepting on-chain payment. Stolen funds routed through you can trigger bank account freezes when victims file fraud reports. Document the screening result and buyer KYC if your jurisdiction requires it for virtual asset service providers.

Red flags that should stop the trade

• Counterparty refuses message signing or ownership proof
• Address created hours ago with single large inbound from mixer-adjacent cluster
• Pressure to skip screening ("rate expires in 3 minutes")
• Different addresses across platforms without explanation
• Direct SDN or sanctions list hit
• Buyer requests you send crypto before fiat clears
• Unsolicited "OTC desk" outreach with rates far below market

Documentation for disputes and banking

When a bank or exchange asks about a transfer, screenshots of chat are weak evidence. Stronger packets include: signed ownership messages, AML screening exports with timestamps, signed invoices, wire confirmations with matching references, and on-chain transaction IDs linked to verified addresses.

This documentation also supports legitimate source of funds demonstrations if your own wallet later inherits exposure from a P2P counterparty.

Free local screening for active P2P traders

High-volume P2P merchants screening dozens of addresses daily face hundreds of dollars in monthly API fees from cloud KYT vendors. AegisAML on Windows provides local graph and sanctions screening without per-address billing — paste counterparty wallets from Telegram, scan, and archive results before confirming each trade.