Situation
Telling the payer what to send
Most lost payments go wrong at the handover, before any money moves. The sender picks a different network from yours, or copies half an address, or sends a coin your account doesn’t expect. The guides in this group are about that single message you send back after someone says “where do I send it?” They cover what the message must contain, when an internal ID is safer than an on-chain address, why the network name matters as much as the address, and how to settle the fee question before anyone gets short-paid. There’s a copyable template in more than one of them. Adapt it, but keep the structure, because each line answers a question the sender would otherwise guess at.
5 guides filed here.
-
How to Invoice a Client in USDT, With a Template
How to invoice a client in USDT: the fields to include, USD versus USDT pricing, the network and fee lines, a copyable template and what to record once paid.
-
Who Pays the Fee When Someone Sends You Crypto?
Who pays the fee when someone sends you crypto? The sender's side does, but a withdrawal fee taken from their amount is why 500 USDT can arrive as 499.
-
Binance Pay ID or Deposit Address: Which to Share
Binance Pay ID or deposit address: give a Pay detail only when the payer sends from their own Binance account, and an address plus network for everyone else.
-
What Should You Send the Person Paying You?
What to send the person paying you in crypto: the coin, the network, the address or ID and any memo, in one message, plus the checks to make before you send it.
-
Someone Wants to Pay You in USDT: What to Set Up
Someone wants to pay you in USDT? Set up five things first: a verified place to receive, the network, the fee, a way to confirm arrival and a cash-out plan.