Sent a duplicate deposit to the same crypto order?
Keep both transaction hashes and stop sending. One order can be configured for one expected deposit, so an additional transfer may need separate provider review.
Reviewed September 1, 2026 · General guidance, not a promise of recovery
DIAGNOSIS FIRST
Identify what actually happened
A duplicate can happen after a wallet retry, a delayed status update or manual resubmission. Two transactions reaching the same address are still separate on-chain events. The second may not inherit the quote, amount or automatic matching of the first.
SAFE NEXT ACTIONS
Work through the evidence in order
- 01Confirm that two distinct transaction hashes exist and both reached the deposit address.
- 02Record the amount and confirmation status of each transfer.
- 03Keep the original order and do not create a third payment.
- 04Allow the tracker to process the expected deposit.
- 05Submit both hashes for review of the additional transfer.
KEEP THIS EVIDENCE
- Original order ID
- First and second transaction hashes
- Amounts, network and deposit address
- Broadcast times and confirmation status
STOP BEFORE YOU DO THIS
- Do not assume the second deposit uses the same rate.
- Do not open another order for the duplicate funds.
- Do not send a third test payment.
SITUATION-SPECIFIC FAQ
Answers before you escalate
Open a ticketWill both deposits exchange automatically?
Do not assume so. The order and quote can expect one deposit, while the second transaction needs provider matching and review.
Can the duplicate be refunded?
Eligibility depends on the provider, asset, network and return cost. Recovery is not guaranteed.
Why did my wallet send twice?
Review the wallet history for two unique hashes. A display duplicate is different from two actual on-chain broadcasts.
CONNECTED REFERENCES