Ethereum and the networks built like it share one address format. A private key gives the same 0x… address on all of them. Valtu uses this: each customer wallet has one EVM address, and it works on every EVM network we support.
What that means for your customers
- One address to show. "Send USDT or USDC to this address on Ethereum, BNB Chain, Polygon, Base or Lisk."
- A wrong network is often still right. If a customer meant Polygon but sent a coin Valtu supports on Base, it still arrives at the same address, and Valtu records it as a Base deposit.
- Each deposit is tagged with its network and coin, so
deposit.confirmedtells you exactly what arrived where.
What it doesn't mean
- Networks Valtu doesn't support aren't watched. The same address exists on other EVM networks too, but Valtu only records deposits on the networks it supports. List those networks clearly. The current list is on the networks page.
- Coins are separate per network. USDC on Base and USDC on Ethereum are different tokens, recognized by their contracts. Valtu counts only each network's real contract, so look-alike tokens are ignored.
Tron and Bitcoin are separate
Tron addresses (T…) and Bitcoin addresses (bc1q…) use different formats, so each customer wallet also has its own Tron and Bitcoin address. One call gives a customer all of them:
const wallet = await valtu.wallets.forCustomer("cus_42");
depositAddress(wallet, "base"); // 0x… (same for ethereum, bsc, polygon, lisk)
depositAddress(wallet, "tron"); // T…
depositAddress(wallet, "bitcoin"); // bc1q…Network pages: Ethereum · BNB Chain · Polygon · Base · Lisk.