ERC-1400 Security Token Transfer Tool (Compliance-Restricted)

WHAT IT DOES

This tool verifies compliance for ERC-1400 security token transfers, helping users determine if a proposed transfer complies with all on-chain restrictions before execution. Given an ERC-1400 token contract address, sender and receiver addresses, an amount, and an optional partition, it reads the token's symbol, decimals, balances, total supply, and calls the canTransfer or canTransferByPartition functions to check if the transfer is allowed. It then displays a clear compliance status—Passed or Failed—along with the compliance code and message explaining why a transfer might be blocked. The tool also checks the sender's balance to verify sufficient funds and displays all relevant transfer details with block explorer links. All data is pulled directly from the blockchain in real time, providing a transparent, auditable compliance check before any security token transfer is executed.

HOW TO USE

Connect your wallet using the Connect button in the header. Select the target network from the dropdown—Ethereum Mainnet, Polygon, Optimism, Arbitrum One, Base, or Sepolia testnet. Enter the ERC-1400 token contract address, the sender address, the receiver address, and the transfer amount. Optionally, provide a partition name or bytes32 partition identifier if the token uses partitioned balances. Click "Check compliance." The tool will fetch the token details, balances, total supply, and call the compliance check functions. Results appear in the card below with a prominent compliance status badge, a detailed compliance message if the transfer is blocked, transfer details including balances and total supply, and a breakdown of compliance factors with checkmarks or crosses. Use this information to verify transfer compliance before initiating a security token transaction.

ERC-1400 SECURITY TOKEN TRANSFER COMPLIANCE VERIFICATION WITH PARTITION SUPPORT

The tool provides comprehensive ERC-1400 security token transfer compliance verification through multiple on-chain reads. First, it retrieves the token's symbol and decimals via standard ERC-20 view functions. It then reads the sender's balance, receiver's balance, and total supply using balanceOf and totalSupply. For the compliance check, it attempts to call canTransferByPartition if a partition is provided, passing the partition, sender, receiver, amount, and empty data bytes. If no partition is specified, it calls canTransfer instead. Both functions return a boolean indicating whether the transfer is allowed and a uint8 compliance code. The compliance code is mapped to a human-readable message—0 for allowed, 1 for general failure, 2 for invalid partition, 3 for insufficient balance, and others for specific restriction reasons. The tool also verifies that the sender has sufficient balance as a basic check. All compliance factors are displayed with visual indicators to help users understand exactly why a transfer is allowed or blocked.

WHAT IT CANNOT SEE

This tool cannot verify off-chain compliance requirements, including legal documentation, KYC/AML status, accredited investor status, or regulatory approvals. It cannot ensure that the transfer is legally valid or that the transaction complies with applicable securities laws. It cannot detect fraudulent documents or verify that the receiver is a legitimate counterparty. It cannot validate controller decisions or ensure that the controller (if any) has properly approved the transfer. It cannot guarantee regulatory compliance in any jurisdiction. It cannot assure that the security token contract is free from vulnerabilities, bugs, or malicious code. It cannot verify that the token contract address is correct or that the partition identifier is valid. It cannot detect front-running or other execution risks. It cannot provide legal or financial advice or guarantee that executing the transfer is safe. All data is provided as-is for informational purposes only; any reliance on the tool's output for transfer decisions is the sole responsibility of the user.

PLEASE NOTE

This tool supports EVM-compatible chains only: Ethereum Mainnet (1), Polygon (137), Optimism (10), Arbitrum One (42161), Base (8453), and Sepolia testnet (11155111). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool requires a Web3 provider (MetaMask or WalletConnect) and access to an RPC endpoint for the selected chain. It does not store any wallet data, token addresses, or transfer records. All queries are performed directly against the blockchain in real time. The tool only provides read-only information and does not execute any transactions. Compliance checks are based on the token contract's implementation and do not guarantee legal or regulatory compliance. Always verify critical data independently through a block explorer and consult with legal counsel before executing any security token transfers.