You need to pay a supplier $50,000 in USDT. You copy an address, check the first and last four characters and send the full amount.

The transaction confirms. The supplier receives nothing.

The blockchain did not malfunction. It executed the signed instruction exactly as submitted. The problem began before the transaction reached the network.

This is the uncomfortable truth about digital assets: the network can complete a transaction perfectly while your business loses the money.

Assets are commonly lost because a team sends to the wrong destination, chooses the wrong network, signs a malicious permission, exposes the keys that control a wallet or repeats a payment that was already processing.

The strongest protection is not one warning screen. It is an operating process that makes a dangerous instruction difficult to approve.

First understand what lost means

Not every missing payment is permanently lost.

A transfer may be delayed, pending, sent on an unsupported network, waiting for a provider to credit it or held for review. In some cases, a recipient or custodial provider may be able to recover the funds. Recovery may take time, attract a fee or be impossible.

The critical distinction is control. If nobody can access the destination address, the private key has been destroyed or an attacker has moved the assets, recovery becomes far less likely.

Once a transaction has been confirmed, the sender cannot simply ask the blockchain to reverse it. Prevention matters because recovery often depends on the cooperation and technical capability of whoever controls the receiving address.

The wrong address

A wallet address is a routing instruction. One changed character can point to a different destination or create an invalid address.

Never retype a long address from memory. Copying is safer than typing, but copying alone is not verification.

For a new beneficiary, obtain the address through a trusted channel and confirm it through a second channel. A supplier might submit the address through an approved payment form, while an authorised contact confirms it on a known phone number.

Then send a small test payment before sending a material amount. The recipient should confirm that the correct asset was credited to the expected account.

Address poisoning makes a wrong address look familiar

Checking only the beginning and end of an address is no longer enough.

In an address-poisoning attack, a scammer creates an address that resembles one your wallet has used before. The attacker then sends a tiny or zero-value transaction so the lookalike address appears in your transaction history. The hope is that you will later copy that address instead of the real beneficiary's address.

The first and last characters may match. The middle is different.

The MetaMask address-poisoning guide recommends checking the middle characters as well and avoiding addresses copied from transaction history.

For a business, the safer process is:

· Never treat transaction history as a beneficiary directory.

· Save verified addresses in an approved address book or allowlist.

· Verify the full address when adding or changing a beneficiary.

· Require a second person to approve a new address before money moves.

· Confirm the destination shown on the signing device or approval screen.

A test payment helps only if the recipient confirms it and you save the verified address. The larger payment must use the same saved, verified address that received the test, never a fresh address copied from history.

Address poisoning and dusting are related but different

People sometimes use the terms interchangeably, but they describe different risks.

A traditional dusting attack sends a tiny amount to a wallet as a tracking tag. If the wallet later spends that dust together with funds from other addresses, an observer may infer that those addresses belong to the same person or business. If one address is connected to a known identity, more of the owner’s transaction history and balances may become traceable.

Some unsolicited tokens also contain suspicious names or links designed to lead users to phishing sites. Address poisoning uses a small or zero-value transaction to place a lookalike address in the victim's history.

Unexpected dust does not give the sender control of your wallet. The danger grows when someone interacts with the unknown token, follows its link or copies the attacker's address. The Coinbase dusting guidance recommends leaving unexpected dust alone. Do not visit a URL embedded in an unknown token or try to “claim” its value.

The right address on the wrong network

“Send USDT” is not a complete payment instruction.

The sender must know the asset, network and recipient address. USDT on TRON and USDT on Polygon are separate tokens moving on separate blockchains.

This becomes dangerous on Ethereum-compatible networks because the same 0x address can appear valid across several chains. A correct-looking address does not prove that the recipient's platform supports the selected network.

Bitnob adds a useful safety check. If the address entered does not match the selected network, it shows an error before the user can continue. Treat the warning as a safety check, not a guarantee. Some networks use compatible address formats, and a technically valid address may still belong to the wrong recipient. Before sending, always confirm the full address, asset and network against the recipient's instructions.

Copy and paste can be compromised

Clipboard malware can monitor a device's clipboard and replace a copied wallet address with an attacker's address. A QR code can also encode the wrong destination if the source page, invoice or device has been compromised.

After pasting or scanning, compare the displayed address with the verified source. For high-value payments, verify it on a separate trusted device or hardware signing screen. If the address changes after it was approved, stop the payment and repeat verification.

Keeping payment devices and software up to date, limiting browser extensions and separating treasury activity from everyday browsing reduces the number of ways an attacker can alter the instruction before signing.

A signature can authorise more than a payment

Not every wallet prompt sends a fixed amount to one recipient.

A contract approval can give an application permission to move tokens later. A malicious or compromised application may request a very large allowance.

Contract approvals are not the only way to lose control. Anyone who obtains a private key or recovery phrase can control the related account. The Ethereum security guidance warns users never to share either one. Never enter a recovery phrase into a website, support chat or unsolicited application.

Businesses should review and remove unused permissions, whitelist approved contract addresses and require stronger approval for unfamiliar transaction types. A test payment does not protect a wallet from a malicious approval.

Access can be lost even when nothing is stolen

A non-custodial wallet depends on its signing keys and recovery design. If the only key is destroyed, the only authorised employee leaves or every backup is unreadable, the assets may remain visible on-chain but impossible to move.

A business recovery plan should cover:

· Who can approve transactions

· How many approvals are required

· Where encrypted backups or recovery material are held

· How access is removed when a team member leaves

· What happens if one signer is unavailable

· How the recovery process is tested without exposing live secrets

Do not keep a seed phrase in screenshots, personal email, chat messages or an unencrypted shared drive. Recovery material should be protected against both theft and accidental loss.

Process errors can create a second payment

An API timeout does not always mean a transaction failed. The request may have reached the network while the application stopped waiting for the response.

If a system immediately creates and signs a new transaction, the business can pay twice. Before retrying, check the original transaction hash, sender address, and provider status.

Turn good advice into controls

Training matters, but controls work when people are tired, rushed or under pressure.

Bitnob lets teams save beneficiaries instead of re-entering recipient details for every payment. The beneficiary guide explains the workflow.

Bitnob Enterprise policies can restrict transactions to approved addresses, apply transaction limits and require multiple approvals. The policy guide also allows rules to consider the chain, network, destination address and token contract. Address screening provides another check for sanctions or risk flags, although screening does not prove that an address belongs to the intended beneficiary.

No control makes every transaction recoverable. The goal is to make the wrong instruction easier to detect before it is signed.

Before a material payment moves

Confirm the beneficiary through a trusted channel. Verify the full recipient address and confirm that you have selected the correct asset and network. Do not copy from transaction history. Send a test payment for a new or changed route and obtain confirmation. Review the amount and fee. Inspect what the signature authorises. Apply the required approval policy. After broadcast, verify execution, finality and recipient credit before marking the payment complete.

The most dangerous part of a blockchain transaction is often the moment before signing.

Slow down there.