STABLEVASP · TRAVEL RULE COMPLIANCE

The Travel Rule compliance architecture.

S1 Intent S2 Identity S3 Discovery S4 Negotiation G S5 Transport G S6 Authorization M S7 Settlement STATE TRANSITION O S8 Finality SCREENING ZONE Gate (code-enforced) Monitor Obligation (policy-enforced)

Why This Matters

CCTP bridging triggers the Travel Rule at S5.

When a developer uses Circle's bridge-stablecoin skill to move USDC cross-chain via CCTP, the Travel Rule Gate fires at S5 Transport. The VASP-to-VASP PII transmission is a policy-enforced Obligation at S8 Finality. The code below shows where each checkpoint fires.

// S5 Transport — CCTP bridge call (code-enforced Gate)
const tx = await cctpBridge.depositForBurn(
  amount, destinationDomain, mintRecipient, burnToken
);

// S6 Authorization — OFAC screening gate (code-enforced)
const screenResult = await chainalysis.checkAddress(mintRecipient);
if (screenResult.sanctioned) throw new ComplianceError('OFAC_HIT', 'S6');

// S7 Settlement — on-chain finality monitor
const receipt = await provider.waitForTransaction(tx.hash, 1);
assert(receipt.status === 1, 'Settlement failed at S7');

// S8 Finality — Travel Rule obligation (policy-enforced)
await travelRuleProvider.transmitPII({
  originator: { name, account, institution },
  beneficiary: { name, account, institution },
  txHash: tx.hash,
  amount, asset: 'USDC',
});

Compliance Depth

Three chains. Three compliance architectures.

Each chain encodes FATF compliance at different architectural layers. Hover any mechanism to see enforcement details.

ETHEREUMEthereum ArchitectureL5ApplicationL4MiddlewareChainalysis KYTChainalysisT7L3ExecutionERC-20 Freeze/BurnERC-20 (USDC)T1Blacklist MappingUSDC ContractT1L2ConsensusPoS ValidatorsCasper FFGT1L1NetworkP2P NetworkT1STATEGateMonitorObligationCodePolicy
BASEBase ArchitectureL5ApplicationSmart WalletERC-4337T3L4MiddlewareAgentKit OFAC/KYTAgentKitT6L3ExecutionUSDC Freeze/BurnERC-20T1OP Stack EVMOP StackT1L2ConsensusEthereumSuperchain BridgeOP StackT5L1NetworkEthereumEthereum PoSCasper FFGT1STATEGateMonitorObligationCodePolicy
ARCArc ArchitectureL5ApplicationInstitutional WalletsInstitutionalT3L4MiddlewareRegulatory View KeysArc PrivacyT6L3ExecutionEVM + Confidential TXArc EVMT1L2ConsensusMalachite BFTPermissionedT1L1NetworkP2P NetworkT1STATEGateMonitorObligationCodePolicy

Three Reports, Three Compliance Layers

The FATF March 2026 Mandates

Skills Pairing

Circle bridge-stablecoin + Atlas Compliance Mapping

The Mapping

CCTP bridging lives at S5 Transport (T5 teal). The Travel Rule Gate fires at S5. The VASP-to-VASP PII transmission is a policy-enforced Obligation at S8 Finality (T7 crimson).

The Developer Story

Install Circle Skills. Write your CCTP bridge. Then check StableVASP.com to see what compliance checkpoints your bridge traverses.