Getting-paid guides · 04

A client wants to pay in USDT. What's the catch?The compliance, counterparty, price and irreversibility risks to think through before taking stablecoins.

A client sends one line: "I'll just pay you in USDT, it's fast and saves on fees." It sounds tempting, especially when your local bank is slow and expensive. But before you nod yes, you need to understand one thing: USDT isn't simply "digital dollars". It hands part of the risk a platform would normally carry for you straight over to you. This guide spells out where it's convenient, what it costs, and which things you should pin down before you take it.

01Why clients love paying in USDT

USDT is a stablecoin pegged to the dollar, designed so that one USDT stays as close as possible to one dollar. Clients like paying with it usually because an on-chain transfer arrives in minutes, the network fee is fixed and often very low, and it sidesteps slow, expensive cross-border banking. For a client whose local rails on their side are poor, it really does save hassle.

Notice that what's convenient is the act of transferring. For you, the real problem starts after the transfer: how this USDT turns into local money you can actually spend, and what you have to carry along the way.

02The flip side: four risks you carry yourself

• Irreversible. Send to the wrong address or wrong chain and the money is basically gone; no support can undo it for you.
• Counterparty and compliance. Afterward you'll most likely turn it into local money via P2P, facing a stranger as the other party; rules on crypto also differ from place to place.
• Price and de-pegging. USDT sits near one dollar most of the time, but it has briefly drifted before; how much local money you end up with is set by the live market price.
• Knowledge barrier. No platform backstops you; you have to read addresses, networks and confirmations yourself, and if you can't, don't force it.

Accept these four, and USDT becomes a tool that's useful to you; if you can't accept any one of them, don't take it just to "save on fees".

The first time I took USDT, the "counterparty" one is exactly where I got burned. Receiving went smoothly; the trouble was converting it back into local money. I sold the coins to a buyer on a platform's P2P market, they paid, I released the coins, and a few days later that payment was flagged as problematic and my account balance was temporarily frozen for a review. The money wasn't lost in the end, but for two weeks I couldn't do anything with it, and that's when it really sank in: the hassle with USDT is almost never in the "receiving". It's in every step you have to face alone afterward. The sections below take those steps apart one at a time.

03Get the "chain" right first: TRC20 vs ERC20 vs BEP20

This is the single most common way people trip up when taking USDT, and the step beginners overlook most. You have to grasp one counterintuitive thing first: the same "USDT" running on a different chain is a different thing, and the chains aren't interchangeable. USDT the client sends on Tron (TRC20) can't arrive at your Ethereum (ERC20) address, and vice versa. Think of them as checks from the same bank that only clear in different settlement systems.

You'll usually run into these three:

• TRC20 (Tron). The most common one for freelance payments across Asia, Africa and Latin America. Its network fee is usually very low, often in the range of a few cents to a dollar or two per transfer, and it arrives fast. Most clients will default to wanting this one because it's cheap for them too.
• ERC20 (Ethereum). The most "canonical" chain, supported most widely by wallets and platforms, but its network fee is the highest of the three; when the chain is congested a single transfer's fee can jump from a few dollars into the tens-of-dollars range. On small amounts, the fee alone can eat a meaningful slice, so it's not worth it.
• BEP20 (BNB Smart Chain). Its network fee is also low, close to TRC20's level, and it's common among people in the Binance ecosystem. But be careful: a BEP20 address looks exactly like an ERC20 one (both start with 0x and are 42 characters), so you can't tell the chain apart by eye, only by agreement. Sending on the wrong chain is especially easy to do here.

Choosing is actually simple: go by which chain your "exit" can receive, then align with the client. Wherever you plan to withdraw the USDT — which exchange account, and which chains that account supports for this coin — check its deposit page first, then send the client the exact chain name and address you want to use, and have them send on that chain. Don't do it the other way around, letting the client pick the chain while you passively receive; that's how you end up with funds on a chain your exit doesn't support.

04Where it lands: exchange account vs self-custody wallet

Once the chain is settled, the next thing to think through is where this USDT actually lands. You have two kinds of destination, with completely different trade-offs.

• Exchange account (custodial). On a mainstream exchange you have a USDT deposit address, and the client sends there. The upside is it's easy: the platform manages keys and security, and once it arrives you can convert it to local currency and withdraw to your bank on the same platform, which is the shortest path. The cost is that you first have to complete KYC, your account is bound by platform rules, and there's platform-level risk too (freezes, regional shutdowns, policy changes). If you don't have an account yet, the account guide walks the whole route from signup and verification through to withdrawal.
• Self-custody wallet (non-custodial). A wallet app on your phone, say, where only you hold the private key (or seed phrase) and no one can freeze your assets. The cost is that all the responsibility is on you too: lose the seed phrase, get phished, or lose the phone with no backup, and that money is gone forever: no "reset password", no support. And after it lands in your wallet you usually still have to move it somewhere that can convert to local money, adding another fee and another transfer risk.

For anyone just starting to take USDT, the realistic choice is often: receive into an exchange account and cash out on the same platform. It puts "receiving" and "converting back to local money" in one place, one fewer transfer and one fewer thing to get wrong, and it's easier to read the arrival status. Once you genuinely understand private keys, seed phrases and on-chain transfers, self-custody is worth considering. This isn't saying custodial is always better; it's that custodial hands the part you're not yet fluent in over to somewhere with a process and support.

05Before you take it, pin these down

Before you agree to be paid in USDT, answer these four questions first:

• Which chain? The same USDT is a different thing on different chains, so you must align with the client before the transfer.
• Which address receives it? You need an address that can receive, checked carefully; if the address is wrong, the money is gone.
• How will you turn it back into local money? Think the exit through first; don't wait until it arrives to find you can't cash out.
• Is it compliant where you are? Rules vary by region, so if you're unsure, look into it first; this site doesn't give legal advice.

06Send one small transfer before anything else

The first time you take USDT, don't have the client send the whole large amount up front. Run the whole flow with a small amount first. In crypto payments, that is the cheapest insurance you can buy. Why it's worth testing: an on-chain transfer is irreversible, so once the address or chain is wrong there's no fix; and the act of "testing" verifies three things at once, before you've put real money on the line: whether the address you gave is right, whether the chain you agreed on connects, and whether your exit can actually convert it back to local money. If any one of the three is broken, the cost of finding out with a small amount is far lower than finding out with the whole payment.

How much? An amount small enough that losing all of it wouldn't hurt, yet large enough to cover the network fee. Too small (say, exactly the fee) is pointless, because you can't see the net amount that lands. A few dollars to a dozen or so is usually enough to run the whole path. Have the client carve this small amount out of the total they owe; don't make it extra money on top.

Pass the small-amount test, then have the client send the rest. The few minutes and few dollars of fee this costs are the cheapest peace of mind you can buy yourself.

07Address and chain: there is no undo button

USDT can move on several chains, commonly Tron (TRC20) and Ethereum (ERC20). They aren't interchangeable: if the client sends on one chain and you give an address on another, the money is very likely lost, and it's irreversible. So before the transfer, always do two things: confirm with the client that you're both on the same chain, and check the receiving address character by character, ideally by copy-paste and comparing the first and last characters, not by typing it out.

One more word on "confirmations": once a transfer is broadcast on-chain, it doesn't count instantly: the network has to confirm it a number of times before it's final. Different chains and platforms require different confirmation counts; TRC20 is usually fast, tens of seconds to a few minutes; ERC20 can take a bit longer when congested. When receiving on an exchange, the platform shows "N confirmations needed", and the balance may not be usable until then. If the confirmations aren't there and the status is still Pending, don't treat the money as arrived, and certainly don't release or refund anything to the client on that basis.

08One USDT payment, converted back: how much is left

"Saves on fees" is the client's favorite line, but it only holds for the transfer leg. What actually decides how much you keep is the spread on the step where you convert USDT back into local currency, and that cost is often more hidden than a bank wire fee. Let's walk one concrete example.

Say the client sends you 1,000 USDT as agreed, on TRC20:

• Network fee: the client pays a small network fee to send this (TRC20 is usually in the single-digit-dollar range), and it's mostly borne by the client; even if it lands on you, it's just a few dollars. At this point you have close to 1,000 USDT.
• The spread to convert back to local money: you'll most likely sell the USDT to someone via a platform's P2P or over-the-counter to get local currency. The cost here isn't a labeled "fee". It's how far below "1 USDT = 1 dollar" you can actually sell. That discount floats with the market and with supply and demand in your region; it might be one or two percent, or more; the more urgently you sell and the more niche your currency, the wider the spread tends to be. Estimate a 1.5% discount, and 1,000 USDT converts to roughly the local-money equivalent of 985 dollars.
• Withdrawing to your bank: moving the local currency from the platform to your bank card may carry a small withdrawal fee too, depending on the platform and where you are.

Add those legs up, and 1,000 USDT reaching your bank card might be the local-money equivalent of 975–990 dollars, depending on your selling spread and the withdrawal fee. Now compare that with a channel like Wise: Wise lays the exchange rate and fees out plainly on a single statement, and for a four-figure cross-border transfer the total cost is usually a single-digit percentage or lower. In other words, the wire fee USDT saves may well be eaten back by the FX spread, so "saves on fees" doesn't necessarily hold: it just moves the cost from a visible place to one you don't easily spot.

So don't just go by "USDT is cheaper". Work out the total cost of each path and then decide. To quickly estimate what one payment nets you, run the network fee and the spread through the USDT cash-out calculator; to understand exactly how the convert-back-to-local-money leg works and where you lose the most, read cashing out USDT to local currency.

09Scam signals specific to getting paid in crypto

Ordinary payments have scammers too, but the crypto setting — irreversible and hard to claw back — has spawned a few plays aimed specifically at the person receiving money. What they share: getting you to do an irreversible action before you've checked things properly. When you see the signals below, stop.

• Fake escrow / fake "platform guarantee". They give you an official-looking "third-party escrow" site or support agent, saying the money is already in escrow and you just complete some step to release it. These sites and agents are usually forged, aimed at getting you to pay an "unlock fee" or "deposit" first, or to hand over account details. Real escrow never asks you to pay first to unlock money that should already be yours.
• Overpayment, asking you to refund the difference. They "accidentally" send an extra amount, or send a screenshot showing an overpayment, and ask you to return the excess. What you send back is real money, while their "overpayment" may never have arrived at all, or is a forged deposit notice. Anything that asks you to refund first is almost always this play.
• "You release the coins first, I'll pay right away." In P2P or OTC trades, they ask you to send the USDT out first on a promise to pay local currency afterward, or send a "payment made" screenshot to rush you into releasing. Don't release until the money is in your account and confirmed in your own records. Screenshots and SMS notices can be faked.
• Rushing you to skip the check. Constant urgency — "limited time", "expiring now", "stop checking and just send the address" — is really about not letting you take the time to verify on a block explorer or to get suspicious. The harder they rush you, the more you slow down. A legitimate client won't fall through because you spent two extra minutes checking.

One general rule to protect yourself: reverse any "pay out first, confirm later" order. Confirm on-chain and in your own account that the money truly arrived, the amount is right and the chain is right, before you do the next thing; screenshots, notifications and a support agent's verbal promise don't count.

10It already went wrong: what is still on the table

Everything above is about staying out of trouble. If you landed here mid-search, you are probably already in it. Four cases below, including the one where all I can honestly tell you is that the money is gone.

Whichever case you are in, the first move is the same: freeze the evidence. Screenshot the messages where you and the client agreed the amount, the coin, the chain and the address; save whatever transaction id they gave you; note the time. Whether you end up asking a platform for help or just need it for your books later, that is the only material you will have.

The client says they paid and you cannot find it

Do not jump to fraud yet. Ask for the transaction id (TXID), the long string, not a screenshot of a success page. Look it up the way section 6 describes and you will land on one of three answers:

• It is there, still confirming. The money is on its way; pushing the client to send again from here is how people end up paid twice.
• It is there, but the receiving address is not yours. It was sent, just not to you. Read the next two cases.
• Nothing comes up on any chain. Check you are on the right explorer first, since they may have used a different chain, and try that one. If no chain has a record of it, then as far as the chain is concerned the payment does not exist. A client who cannot produce a transaction id you can look up has not paid yet.

Right address, wrong chain

This is the one case with a real chance, because the Ethereum-style chains (ERC20, BNB Chain, Polygon and the rest) share a single address format, so the same address exists on all of them. The money did not vanish; it is sitting at your address on a different chain. Whether you can get it back comes down to who controls that address:

• It is your own wallet (you hold the seed phrase or private key): switch the wallet to that chain and the balance usually appears, ready to move normally. You may need a small amount of that chain's native coin first to pay the network fee.
• It is a deposit address an exchange gave you: you cannot touch it yourself, so the platform is the only route. Some run a recovery process, normally a support ticket, normally a fee, normally a wait, and with no guarantee. Others state plainly that they do not. Go by your platform's own published policy rather than someone's summary of it.

One caveat: Tron (TRC20) uses a completely different address format, so an Ethereum-style token sent to a Tron address, or the reverse, usually is not this case at all. See the next one.

The address itself was wrong

Sent to an address that is not yours and is not anybody's, the money is gone. On-chain transfers have no undo, and no institution can claw one back for you. The job here is not recovery, it is stopping the bleeding: write down the amount, the time and the transaction id, agree with the client how the rest of the payment will now be made (who absorbs the loss is a commercial conversation the two of you have to have), then go back to section 6 and start again from a small test.

It arrived, but it is not the coin you think

Token names in a wallet or an explorer are whatever the issuer typed in, and anyone can mint something called USDT and send it to you. What settles it is the issuing contract, and the place to read that is the deposit page of the exchange you will actually be using, where the platform labels the coin and the chain itself. Never copy contract details out of a chat, an email or a search result, because that is precisely the door this scam walks in through.

There is a blunter version too: you never agreed to take crypto, and a token you did not ask for simply appears in your account. Leave it alone, and above all do not follow whatever instruction its page gives you to connect a wallet or approve something. That prompt is usually aimed at the rest of what is in your wallet.

11When to just say no to USDT

In some situations, the best move is to politely decline and switch to another way to get paid:

• You don't understand concepts like address, chain and confirmations, and you don't have time to learn them.
• This is a large amount that matters to you and you can't afford to lose, yet it's your first time taking USDT.
• The other side manufactures urgency, pushes you to "send the address quick" or "just take it first", or asks you to do something else first. That's often a scam signal, so stop right away.

12Clear up a few myths before taking USDT

13FAQ

14What to read next

One final check is worth making routine: put the asset, network, address, amount and confirmation method in the payment instructions you send the client, and have both sides verify them independently. For a large payment, send a small test first and release the balance only after it arrives. A few minutes here is usually far cheaper than tracing a wrong network, address or amount later.