Retail Payments

P2P Wallet Transfer

Self-custodial wallet-to-wallet transfer. Travel Rule compliance is thin — honesty marker territory.

Vendors

Self-Custodial Wallets

Compliance Center

Travel Rule gap at Facilitation. Compliance thin on self-custodial P2P.

R4 — P2P wallet transfer · Rails: retail · Protocols: ERC-20 transfer · Origin: United States — Federal
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
R4 — P2P WALLET TRANSFERYOU ARE HERE● Sender WalletPOLICY⬣ On-Chain Transf…CODE● Recipient WalletPOLICYIntentIdentityDiscoveryNegotiationTransportAuthorizationFacilitationFinalitySTEP 1STEP 2STEP 3BASEVisual system: StablecoinAtlas.com · Steps mapped to 8 STP Stages
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 1 · Sender Wallet (Base)Policy-EnforcedBlockchain-Native

A cash handoff — the sender decides to pay, but unlike a bank transfer, there's no institutional identity gate.

Self-custodial wallet on Base. No KYC gate — the wallet is permissionless. Identity is established only to the extent the wallet provider (MetaMask, Coinbase Wallet, Rainbow) collects it, which for self-custody is typically none. L4 Account and L5 Application lit, but the identity layer is hollow. **Honesty marker:** the D1 (Identity) domain is technically present but not meaningfully enforced.

⚠ ENHANCED-DUE-DILIGENCE triggered at USD 50,000 — 31 CFR § 1010.312 — Enhanced Due Diligence (United States — Federal)
Counterparty
Self (sender holds private keys)
Latency
Instant · no on-chain tx yet
Finality
N/A — payment not yet submitted
Vendors
Coinbase Smart Wallet · ERC-4337 Smart Account · Coinbase Paymaster
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 2 · On-Chain TransferCode-EnforcedBlockchain-Native

Handing someone cash — the transfer executes, no intermediary screens it, no Travel Rule data accompanies it.

USDC transfers via a single ERC-20 transaction on Base. If the USDC contract's blocklist includes either address, the transfer reverts — this is the only code-enforced compliance gate. No sanctions oracle fires unless the wallet app adds one at the UX layer. L2 Consensus and L3 Execution lit. **Honesty marker:** Stages 3-6 compress because there is no Discovery, no Negotiation, and Authorization is reduced to the USDC blocklist check.

⚠ TRAVEL-RULE triggered at USD 3,000 — 31 CFR § 1010.410(f) — Funds Transfer Recordkeeping (United States — Federal)
Counterparty
Recipient wallet address
Latency
~2s · single Base block
Finality
Final on Base block confirmation
Vendors
ERC-4337 Smart Account · Coinbase Sequencer · Uniswap v4 · Chainalysis OFAC Oracle
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 3 · Recipient Wallet (Base)Policy-EnforcedBlockchain-Native

Receiving cash — the recipient has the funds, but no reporting happened, no Travel Rule data was exchanged, no record exists outside the blockchain itself.

USDC arrives at the recipient's self-custodial wallet. L4 Account and L5 Application lit. **Honesty marker:** D7 (Travel Rule) is listed because FATF Recommendation 16 requires it, but in practice no mechanism exists to transmit originator/beneficiary data in a permissionless self-custodial transfer. This is the structural compliance gap the industry has not solved. Recordkeeping (D11) relies entirely on on-chain transparency — no off-chain report is filed.

Active Compliance Checkpoints
C2 OFAC SDN/SSI list screening — OFAC 50 USC § 1702 (United States — Federal) · GENIUS §6
C7 Notabene IVMS101 or Chainalysis Connect — FATF Rec. 16; 31 CFR 1010.410(f) (United States — Federal) · GENIUS §7, §8
C11 SAR/CTR filing via BSA E-Filing — 31 CFR § 1010.320 (United States — Federal) · GENIUS §9
⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
Counterparty
Recipient (unknown identity in self-custodial case)
Latency
Instant on block confirmation
Finality
Final · irrevocable — and unreportable
Vendors
Coinbase Smart Wallet · ERC-4337 Smart Account · Coinbase Paymaster

Resolved 3 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.

TOOL 01 · IVMS101 MESSAGE BUILDER

Travel Rule Validator

Build FATF Rec 16 Travel Rule messages with TRUST, Notabene, Sygna, and OpenVASP protocol compatibility.

Transfer Details
Quick Scenarios
Originator
Beneficiary
IVMS101 Message
Click "Validate IVMS101" to generate message.
TOOL 02 · 4 TOKEN STANDARDS

Token Freeze/Burn Simulator

Simulate freeze, burn, and deny-list operations across ERC-20, Token-2022, TRC-20, and ERC-3643 — with bypass risk analysis.

Input Parameters
Operation Trace
Select parameters and click "Evaluate Operation" to see the trace.