Skip to main content
Rain holds funding in collateral contracts on-chain, not in an account it controls on your behalf. The wallet address a customer provides stays theirs: it’s an admin on their collateral contract, not a funding source Rain owns.

Wallet roles by management model

Whether a customer needs a wallet, and what that wallet controls, depends on your management model: If your Rain-Managed users don’t have wallets, you can use a provider such as Turnkey, Zerodev, Dynamic, or Privy to provision them. See Flow of Funds for the full comparison between the two models.

EOAs and smart contract wallets

Rain’s collateral contracts accept two kinds of admin address:
  • Externally Owned Accounts (EOAs): wallets controlled by a private key, such as MetaMask or Ledger.
  • Smart contract wallets: wallets like Safe or an ERC-4337 account abstraction wallet, verified through the ERC-1271 standard. These add multi-signature approval, spending limits, and gas abstraction.
See Smart Contract Wallets for the full setup process and signature verification details.

Supported chains

Rain supports EVM chains (Polygon, Base, Celo, Optimism, BNB Smart Chain, Avalanche, Arbitrum, ZKsync, Plasma, Monad), plus Solana and Stellar. Token support (USDC, USDT) varies by chain. See Supported Chains and Tokens for the full chain ID and token contract address reference.

What’s next

Fund the Card

How collateral works in each management model.

Smart Contract Wallets

EOAs, ERC-1271, and account abstraction with Rain’s collateral contracts.

Supported Chains and Tokens

Chain IDs, mainnet and testnet, and token contract addresses.