Wallets and receiving networks

How receiving wallets are connected, verified and locked per network, why changes need an email code, and what the freeze rule protects.

Three separate steps

1. Connect: NervixPay reads your public address from MetaMask, a WalletConnect wallet, TronLink or your Telegram TON wallet.
2. Verify: you sign a message proving you own the address. It is free and moves nothing.
3. Assign and confirm: you choose the verified wallet on a network card and enter the code emailed to your account address.

The freeze rule

Once confirmed, a network card shows Ready, locked. New payments on that network go to that address, and it keeps receiving until you change it. Changing or removing it requires a fresh email code, every time.

• Orders that already exist keep the address they were created with. A change never redirects a payment in progress.
• Each email code is bound to one change (network, new address, current address), expires, allows five attempts and works once. Requesting a new code cancels the previous one.
• A wallet assigned to a network cannot be deleted while it is assigned.
• AI agents and API keys cannot change receiving addresses; there is no API for it.

One address, several networks

Polygon, Ethereum and BNB Chain share the 0x address format, so one verified wallet can be assigned to all three; each still needs its own confirmation. TRON and TON have their own address formats and wallets. A verified Telegram address does not switch on TON payments by itself: the TON card must be assigned too.