A free tool from Payclose

Check USDT and USDC payout addresses before you send

An address that starts and ends like one you trust but differs in the middle. A typo that breaks the checksum. A TRON (TRC-20) address pasted into a Base column. Paste this month’s addresses and see all of that before the batch goes out.

Runs in your browser. Nothing you paste or upload is sent anywhere. Payclose never holds funds or keys and is not a wallet or an exchange: this page reads what you paste and shows you what it finds.

Your address list

One address per line, with a label and a network word if you have them. A CSV with a header row works too.

(optional)

Last month’s payout or your address book. New addresses are compared against these.

What a check looks like

Ten invented payout addresses, checked against four addresses paid before. It’s what the checker shows when you select Try with sample data: the rows that need attention first, the differing middle of each look-alike marked.

Sample data. 10 addresses: 1 look-alike, 1 wrong checksum, 1 wrong network, 2 share one address, 1 listed twice, 1 without checksum.
The sample list with what the check found for each address.
Attention Label Address Network Result
Needs attention Mei Lin
0x92C7eeC36Db7A94cAcaBaCB6d7df21e4Dc4F4aEd
Base EVM format
  • Wrong checksumMixed case doesn’t match the EIP-55 checksum, so at least one character is wrong. Copy it again from the source.
Needs attention Kofi Mensah
TJYpiMTFWRrs2Rh7s5JMvdM2xrWvxvHR8z
Base TRON format
  • Wrong networkA TRON address on a row marked Base. Either the network or the address is wrong.
Needs attention Tomás Silva
TUEFT3s6TL1XjuRUVgoo3ukid5N7bJ7r4A
TRON TRON format
  • Look-alikeStarts and ends like Tomás Silva’s trusted address, but the middle is different. This is how address poisoning works.
Needs attention Daniel Okafor
0xfAe48f710e9803C40c712e968eF38ef417E34769
Base EVM format
  • Shared addressSame address as Priya Nair (line 5). Check who owns it.
  • In your trusted listListed there as Priya Nair.
Needs attention Priya Nair
0xfAe48f710e9803C40c712e968eF38ef417E34769
Base EVM format
  • Shared addressSame address as Daniel Okafor (line 4). Check who owns it.
  • In your trusted list
Needs attention Hana Kim
TQ8NCiUA3SURTTg7dPpf6534ikxL11CpWP
TRON TRON format
  • Listed twiceAlready listed on line 9. Check it isn’t a double payment.
Fine Nadia Haddad
Checksummed form (EIP-55) 0xbB89129D14b45d569468A34134e891A3d98BCBB6
Not given EVM format
  • No checksumAll lowercase, so it carries no checksum and a typo can’t be caught. Fine if it was copied from a trusted source, not typed.
Fine Lucía Fernández
0x4bE0D1a793C5e240F18b6C3dA0579E21b4C607FD
Base EVM format
  • ValidFormat and checksum pass.
Fine Arjun Mehta
TRGGYPn9yMhvhw7u4qPtxw1MTwiJx9QQQk
TRON TRON format
  • In your trusted list
Fine Hana Kim
TQ8NCiUA3SURTTg7dPpf6534ikxL11CpWP
TRON TRON format
  • ValidFormat and checksum pass.

What it checks

It recognises TRON addresses as well as EVM ones. Payclose itself pays on EVM networks today; TRON comes later.

  • Look-alikes. An address that starts and ends like one you trust but differs in the middle: the trace of address poisoning. Each address is compared with your trusted list and with the rest of the list, on the first four and last four characters of the address body.
  • Checksums. EVM addresses (0x…) carry an EIP-55 checksum in their mixed case, TRON addresses (T…) one in their base58 form, and a typo breaks it. An all-lowercase EVM address has no checksum; the results show its checksummed form for you to copy.
  • TRC-20 and ERC-20 mix-ups. USDT runs on TRON and on EVM networks, and the two address formats end up in the wrong column. With a network word or column next to each address, a TRON address on a Base row is flagged, and so is the reverse. Ethereum, Base and Arbitrum share 0x addresses, so the format can’t tell them apart.
  • Shared and repeated addresses. One address on two people’s rows, or the same row twice: a copy-paste slip, or a payment made twice.

When to use it

  • Before the monthly payout. Paste this month’s addresses, and last month’s as the trusted list.
  • When a contractor sends a new address. Check it before it goes into the sheet, then confirm it with them on another channel than the one it came by.
  • When someone else prepared the sheet. A second pair of eyes before you approve it.
  • Before a batch goes to your Safe. The Safe CSV Airdrop file builder runs the same checks while it builds the file; more on contractor payouts from a Safe multisig.
  • When you tidy an address book. Duplicates, and one address saved for two people.

What a check can’t prove

  • Who owns the address. A valid checksum proves there’s no typo, nothing more. An attacker’s address has a valid checksum too.
  • Look-alikes of addresses you didn’t paste. An address is compared with the list and the trusted addresses you give it, and with nothing else.
  • Anything on-chain. No balances, no history, no sanctions or scam lists, and no way to tell a personal wallet from a contract or an exchange deposit address.
  • Which EVM network. Ethereum, Base and Arbitrum addresses look the same; only your network column says which one a row pays on.

The proof is the person: confirm a new or changed address with them through a channel other than the one it arrived on. In Payclose, a new address is approved by someone other than the person who added it and can’t be paid for 24 hours, and a contractor can confirm their own address with a signature from their wallet: see recipients and addresses.

Your addresses stay here

Everything runs in this browser tab. The list is read on your device and checked there; it’s never sent to a server, saved, or kept in cookies or browser storage. There’s no wallet to connect and no account to make.

The page counts how many addresses were checked and how many were flagged, never an address, a label or a name.

Checking addresses by hand every month?

Payclose runs these checks on every payout automatically, before anything is sent: look-alikes of every address you’ve paid before, checksums and networks, approvals recorded, and every new address approved and held for 24 hours before its first payout.

Free during the beta. EVM networks, from a Safe or a regular wallet; TRON later.

Questions

Is anything uploaded?

No. Everything runs in your browser: the list is read on your device, checked there, and never sent to a server or saved. Nothing goes into cookies or browser storage; close the tab and it’s gone. The page only counts how many addresses were checked and how many were flagged, never what they were or whose they are.

What is a look-alike, and what is address poisoning?

An attacker generates an address that starts and ends like one you already use, plants it in your transaction history with a tiny transfer, and waits for someone to copy the wrong one, hoping nobody reads the middle. Wallets and explorers show only the first and last few characters, so the swap is easy to miss. The pattern is documented at scale in a 2025 USENIX Security paper. This checker compares each address with the trusted list you paste and with the other rows: same first four and last four characters of the address body, different middle, and the row is flagged. Paper: Tsuchiya et al., Blockchain Address Poisoning, USENIX Security 2025.

What does “no checksum” mean?

An EVM address written in mixed case carries a checksum (EIP-55): the pattern of upper- and lower-case letters is derived from the address itself, so a typo breaks the pattern and can be caught. An all-lowercase address has no checksum, so a typo can’t be caught this way. That’s fine when the address was copied from a trusted source, and worth a second look when it was typed or retyped. TRON addresses always carry a checksum in their base58 form, so a typo there shows up as a wrong checksum.

How do I get the checksummed (EIP-55) form of an address?

Paste it here and run the check. Every valid EVM address in the results is shown in its EIP-55 form, and one you pasted in lowercase is labelled “Checksummed form (EIP-55)”, ready to copy. The downloadable report carries the same form.

Does it check USDT TRC-20 and ERC-20 addresses?

Yes. It reads EVM addresses (0x followed by 40 hex characters), which USDT and USDC use on Ethereum (ERC-20), Base, Arbitrum and every other EVM chain, and TRON addresses (T followed by 33 characters), which USDT uses on TRON (TRC-20), and checks each one’s checksum. The format alone can’t tell Ethereum from Base, so wrong-network detection needs a network word next to the address or a network column in your CSV: a TRON address on a row marked Base is flagged, and so is the reverse. Payclose itself pays on EVM networks today; TRON comes later.

Does it show balances, or whether an address is a scam?

No. It doesn’t look anything up on-chain, so it shows no balance or history, and it doesn’t check whether an address is a contract, sanctioned or on a blocklist, or whether it really belongs to the person you think. It doesn’t connect to a wallet and never sends anything. It’s a second pair of eyes, not a guarantee: confirm a new address with the person directly, not in the chat where it was sent.