Networks and wallet addresses
Why the network must match, what a checksum is, and how a wrong-network send can be lost.
On this page
USDC exists on several blockchains ("networks"). Your provider gives you a deposit address for one specific network. The address and the network must be used together, every time.
In beta
The automatic address and network checks on this page run on RailFi payment links, which are in beta for invited contractors. For invoices we handle by hand, the RailFi team checks your address and network before sending payer instructions.
Supported networks
RailFi supports native USDC on these networks, where your provider supports them too:
| Network | Address looks like | RailFi checks |
|---|---|---|
| USDC on Ethereum | 0x + 40 hex characters | EIP-55 checksum |
| USDC on Polygon PoS | 0x + 40 hex characters | EIP-55 checksum |
| USDC on Base | 0x + 40 hex characters | EIP-55 checksum |
| USDC on Arbitrum | 0x + 40 hex characters | EIP-55 checksum |
| USDC on Solana | 32–44 base58 characters | Must decode to exactly 32 bytes |
Not supported Tron, Bitcoin, and bridged USDC (USDC.e) on any network.
Why the network must match
Ethereum, Polygon PoS, Base and Arbitrum all use the same address format, so the same 0x… address is valid on all four. RailFi can't tell from the address alone which network your provider credits. That's why:
- There is no default network. You pick the one your provider shows next to the deposit address.
- You tick "This is my provider's deposit address for USDC on {network}" before the invoice is created.
- The network name is shown in large text on every screen and in every email, next to the address.
- Your payer re-selects the network before the sending instructions appear.
A Solana address looks different from an EVM address, so RailFi blocks a Solana address on an EVM network, and the reverse, with a network mismatch error.
Wrong-network loss
Sending on the wrong network can lose the money
USDC sent on a network your provider doesn't credit may never reach your account and may not be recoverable. RailFi never holds or moves money, so RailFi can't reverse or retrieve a transfer. Only your provider can say whether a wrong-network deposit can be recovered.
Checksums
EVM addresses use a mix of upper and lower case letters as a built-in typo check (EIP-55). If one character is mistyped, the capitals no longer add up and the checksum fails. Example of a valid checksummed address:
- Mixed case, checksum fails: blocked. You'll see a checksum error.
- All lowercase (or all uppercase): there is no checksum to check, so RailFi warns "No checksum on this address. Double-check every character" and you must retype the last 6 characters.
- Solana: the address must decode from base58 to exactly 32 bytes.
RailFi shows every address in 4-character chunks, with the first 6 and last 6 characters highlighted, so it can be compared against a wallet screen at a glance.
Addresses RailFi blocks
- Anything that isn't a valid address for the chosen network
- The zero address (
0x000…000) - The USDC token contract itself. It's a common copy-paste mistake: it's not a deposit address
- Addresses on the U.S. Treasury OFAC SDN list. See Sanctions screening
Spaces and invisible characters at the start or end are removed; spaces in the middle are rejected.
Getting it right
- Open your provider's USDC deposit page and note the network it names.
- Copy the address with the copy button. Never type it from memory or from a screenshot.
- Pick the same network in RailFi, paste the address, then retype its last 6 characters.
- Compare the first 6 and last 6 characters against your provider's page.
- Ask your payer to send the small test amount first.
Last updated 30 September 2026. Something unclear or wrong? Tell us.