Most losses come from five avoidable mistakes. A short routine before and after each payment removes most of them.
Most stablecoin losses come from five avoidable mistakes: a wrong network, a wrong or altered address, a payment request from a fake sender, a coin your address does not support, and a payment made outside the banking channel. A short checklist before and after each payment removes most of that risk. The last mistake also costs you paperwork, because a payment outside the banking channel leaves no eFIRA, as FEMA rules for freelancers explain.
Five common ways a payment goes wrong
| Mistake | How it happens | How to avoid it |
|---|---|---|
| Wrong network | The client sends the coin on a network your address does not support | Agree the network in writing and send a test payment first |
| Altered address | Software on a device swaps the copied address for another, or a lookalike address sits in the client's history | Copy the address from your dashboard each time and compare the first and last characters before sending |
| Fake payment instructions | An email that looks like yours says the address has changed | Confirm any change by a second channel, such as a call |
| Unsupported coin | The client sends a different token | Name the exact coin in the invoice |
| Payment outside the bank flow | The client pays a personal wallet | Use the address from your dashboard so a bank leg and an eFIRA follow |
Before the first transfer
-
Finish KYC on your DashX account.
-
Read the supported coins and networks in your dashboard.
-
Send your client the invoice, the coin, the network and the address in one message.
-
Ask for a small test payment first.
-
Confirm the test on a block explorer and in your dashboard.
-
Only then ask for the full amount.
Our network guide explains how to choose the network.
When you share your address
A payment address is meant to be shared, and sharing it does not give anyone access to your funds. Never share a seed phrase or a private key with anyone, including someone who claims to be support. Use the address from your dashboard each time, and do not reuse one from an old chat.
After the payment
Look up the transaction hash on the block explorer, check the status in your dashboard, and file the invoice, the hash and the eFIRA together. A tidy record is the easiest protection against a dispute later, and against questions from the tax department. Read tax notice red flags for freelancers and AIS and TIS reconciliation to see what gets flagged.
Red flags in a client request
-
A request to pay a fee first. Nobody legitimate needs you to send money before they release a payment.
-
An overpayment with a request to refund the difference. This is a well known scam, and the refund goes to a wallet that the scammer controls.
-
Pressure to change the coin, the network or the address at the last minute. Slow down and verify.
-
A client who refuses to use the address in your instructions. That payment will skip the bank leg, and you will not receive an eFIRA.
If something goes wrong
Stop and do not send anything again. Save screenshots, the transaction hash, the coin and the network, and write to DashX support with your invoice number. If you suspect fraud, report it on the National Cyber Crime Reporting Portal or call the helpline at 1930.
Frequently asked questions
Can a wrong network payment be recovered? Sometimes the receiving service can recover it, but it is not guaranteed, and many such coins are lost. Prevention matters more than the cure.
Is it safe to share my payment address? Yes. An address only receives funds. Keep your seed phrase and private keys to yourself.
What if my client overpays? Do not send a refund on your own. Contact DashX support, and verify the overpayment in your dashboard first.
How do I check that a request really comes from my client? Confirm it through a second channel that you already know, such as a call to a number you saved earlier.
Start with a payment address you can trust. Sign up for DashX
