Give a Binance Pay detail only when the payer will send from their own Binance account. For everyone else, give a deposit address and the network, together, in one message. The table covers the usual cases:
| The payer’s situation | What to give them |
|---|---|
| Has a verified Binance account and will send from it | Binance Pay: your QR code or Binance ID (your account email or phone also work) |
| Uses another exchange | A Binance deposit address and the network it belongs to |
| Uses a personal crypto wallet app | A Binance deposit address and the network it belongs to |
| Isn’t sure where they’ll send from | Nothing yet. Ask which app they’ll send from, then pick a row |
| Is ready, but your own account isn’t verified | Nothing yet. Finish verification first |
The two routes aren’t interchangeable. A Pay ID means nothing to another exchange, and a Pay transfer never uses a deposit address. Picking the row first saves a failed transfer and an awkward message.
When you’re both on Binance: use Pay
If the payer has a Binance account, Pay is usually the simpler route: no address to copy, no network to match, and the money is credited straight away. It moves money between two Binance accounts inside Binance, so nothing is sent on a blockchain.
Three rules from Binance’s own help page on sending with Pay shape how you use it.
The recipient must be verified. Pay sends only to a Binance user who has completed identity verification. If you haven’t finished yours, the payer can’t send to you this way yet. The guide to opening and verifying a Binance account covers that step.
It’s immediate. Binance says transfers by email, phone number or Binance ID “are immediately credited.” There’s no waiting for confirmations, which is a real advantage when someone is paying you while you’re both on the phone.
Wrong details can’t be fixed. The same sentence goes on: “They cannot be recovered if you entered the wrong details.” If the payer types an email with one wrong letter and that email belongs to another Binance user, the money goes to that person. That’s why I’d rather give a QR code or a Binance ID the payer can paste, instead of an email they type from memory.
On cost: because nothing goes on-chain, there’s no blockchain network fee for a Pay transfer. If Binance charges any platform fee for a particular transfer, the Pay screen shows it before the payer presses [Confirm], so that’s where to check. There are also monthly send limits on the payer’s side, which they can see in their own Pay settings. For a large payment, it’s worth asking them to look before the day.
For the payer, the steps on Binance’s page are [Pay] → [Send] → [Send to Binance User], then your email, phone or Binance ID, the amount, [Confirm], and their two-factor code or Pay PIN. You don’t need to walk them through it; they’ll see it in their own app.
Here’s a message you can adapt. It points the payer to the right screen and asks them to paste rather than type.
Pay details for a payer who is on Binance
You can pay me with Binance Pay from your Binance app: Pay, then Send, then Send to Binance User. My Binance ID: [paste your Binance ID here] Please paste the ID rather than typing it. Pay transfers are credited straight away and can't be reversed if a detail is wrong. I'll confirm as soon as it shows in my account.
Pay suits family money well when both sides already use Binance: a relative abroad can send without learning about networks, and you see it at once. Whether USDT is a better route home than a remittance app is a separate question, weighed in the guide on family money through USDT or a remittance app.
Where to find your Pay receive options
Your receive details are in the Binance app under [Pay] → [Receive]. That screen shows a QR code, or you can create a payment link. You can share the QR code, the email address on your Binance account, your phone number or your Binance ID.
Which one to share is partly about privacy. Your email and phone number are personal and get reused elsewhere. A Binance ID or a QR code identifies your account without handing out either. With a new client or someone I don’t know well, I’d share the Binance ID or the QR code. With family who already have your number, the phone number is fine.
Money received through Pay lands in your Funding wallet, not your Spot wallet. People who check Spot first often think a payment hasn’t arrived. Open the Funding wallet, or your Pay history, and look there.
Confirm it yourself. A screenshot of the payer’s “sent” screen proves nothing about your balance; screenshots are easy to edit, and fake proof is a common trick. Open Binance yourself and check that the amount is in your Funding wallet before you tell anyone it arrived or hand over anything in return. The guide on checking whether a crypto payment has arrived covers both routes.
Where this comes from checked September 2026
The Pay steps and rules come from Binance’s help pages How to receive cryptocurrency payments in Binance Pay (updated 2 June 2026) and How to send cryptocurrency to an individual with Binance Pay (updated 8 June 2026). The deposit steps and the network warning come from How to deposit crypto to Binance. The send page doesn’t state Pay fees, so we don’t either.
When the payer is elsewhere: give a deposit address and network
If the payer sends from another exchange or from a wallet app, they need a deposit address, and the address only works on the network it was created for. On Binance’s website the steps are [Deposit] → [Deposit Crypto], choose the coin, choose the network, then copy the address or show the QR code. You may also be offered a choice of where the deposit lands, Spot or Funding.
Ask the payer which networks they can send USDT on before you choose. Binance’s instruction is: “Please make sure that the selected network is the same as the network of the platform you are withdrawing funds from.” If the payer sends on a different network from the one your address was given for, the funds may be lost and not recoverable. Crypto transfers can’t be reversed by either side, so this is the one place where a careless moment costs the whole payment.
Two more details belong in the same message. If the deposit page shows a memo or tag field, the sender must include it; USDT on the common networks normally has none, but the page is what counts. And the page shows a minimum deposit amount, which matters most if you ask for a small test first.
Unlike Pay, an on-chain transfer costs the sender a network fee and takes some time to confirm. The guide on what to send your payer has ready-made wording for the address, the network and the test request.
What not to share, and fixing the usual mistakes
Share a receive detail, never an access detail. Your QR code, Binance ID or a deposit address let someone send you money. Nothing else is needed. Never share:
- your password or the email and password together;
- any code from text messages, email or your authenticator app;
- a screen share or remote-access session with your Binance app open;
- photos of your ID document, sent to a payer “for their records”.
Anyone who says they need one of these to pay you is not trying to pay you. Real payments only need the receive detail.
When something goes wrong, the fix depends on which route was used.
The payer has a Pay ID but uses another exchange. Their exchange can’t send to a Binance ID. Nothing was lost; give them a deposit address and a network instead.
The payer sent through Pay to the wrong email, phone or ID. Binance says these transfers can’t be recovered. The only realistic route is the person who received it sending it back, which is why a pasted ID or a scanned QR code beats a typed email.
The payer sent on-chain on the wrong network. Get the transaction ID from them, check the address and network on it, and contact Binance support from inside your account with the TxID, coin, amount and time. Recovery isn’t something to count on.
The payment “hasn’t arrived”. For Pay, look in the Funding wallet. For an address deposit, check which wallet you chose on the deposit page and whether the transfer is still confirming.
You gave the address without the network. Send the network now, before they send, in the same thread. If they’ve already sent, ask for the TxID and look up which network it went on.