Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Missed destination TAG while transferring XRP funds #2644

Open
str4n63r opened this issue Dec 27, 2017 · 28 comments
Open

Missed destination TAG while transferring XRP funds #2644

str4n63r opened this issue Dec 27, 2017 · 28 comments

Comments

@str4n63r
Copy link

Dear Team,

I had transferred XRP from one X wallet to Y wallet. But while doing so I missed entering Y wallet's destination TAG number and entered correct Y wallet's address. When I was checking the transaction status it's showing as completed but I didn't receive the XRP in Y's wallet. Something can be done now to get my XRP funds back? Or for how long I need wait for funds to get back to my X's wallet. Help really appreciated. @sublimator

Regards,
Sateesh

@sublimator
Copy link
Contributor

You will have to contact Y with the transaction details (transaction hash) and perhaps they will kindly refund you :)

@str4n63r
Copy link
Author

Dear @sublimator ,

Correct me if I'm wrong, so what you're saying is now I can get in touch with my recipient wallet's support team with transaction hash from https://xrpcharts.ripple.com which has been provided by my originating wallet? Let me know if I'm missing something.

Regards,
Sateesh

@sublimator
Copy link
Contributor

Yes!

@str4n63r
Copy link
Author

str4n63r commented Dec 27, 2017

@sublimator Thanks a lot for the insight man! I did the same step already and not sure whether that is how I should approach and you cleared my doubt. Cheers :)

@sublimator
Copy link
Contributor

Wallet provider Y should also have requires destination tag flag set on their account, so that any transactions sending money to them REQUIRES a destination tag: https://ripple.com/build/ledger-format/#accountroot-flags

@str4n63r
Copy link
Author

@sublimator They(Wallet Y) got a valid "Destination TAG" for my account but I missed entering the same while transferring funds from wallet X.

Regards,
Sateesh

@sublimator
Copy link
Contributor

You used NO destination tag ? or WRONG ?

@str4n63r
Copy link
Author

@sublimator I didn't use any destination TAG and selected no destination TAG option from wallet X while transferring funds to wallet Y.

@sublimator
Copy link
Contributor

Wallet Y can enable a require destination tag flag in their account, so that your transaction would have failed, only claiming the fee. See: https://ripple.com/build/ledger-format/#accountroot-flags

You might ask them to enable it for the next unlucky guy :)

@str4n63r
Copy link
Author

@sublimator Just now I had seen this in my wallet Y's terms and conditions.

"If you send XRP tokens without mentioning your destination tag, your deposit will not be processed and Koinex will not be responsible for the loss of tokens in that case."

Any idea how to proceed now?

@sublimator
Copy link
Contributor

sublimator commented Dec 27, 2017 via email

@str4n63r
Copy link
Author

str4n63r commented Dec 27, 2017

@sublimator Even though I selected "No Destination TAG" while transferring still Ripple network created Flag: tfFullyCanonicalSig in the transaction page. You're referring to that?

@sublimator
Copy link
Contributor

sublimator commented Dec 27, 2017 via email

@str4n63r
Copy link
Author

@sublimator Thanks for the support. Will do.

@sublimator
Copy link
Contributor

Ripple network created some flag in the transaction page. You're referring to that?

I was saying that the wallet provider Y (Koinex) can enable some settings on their account that REQUIRE a destination tag to be set by clients otherwise the transaction will fail.

@str4n63r
Copy link
Author

I was saying that the wallet provider Y (Koinex) can enable some settings on their account that REQUIRE a destination tag to be set by clients otherwise the transaction will fail.

@sublimator Yeah! It completely makes sense.

@ghost
Copy link

ghost commented Jan 10, 2018

Hello ,
I withdraw 65.5 XRP from cex to hitbtc , and i checked wallet and tag address, but when i withdraw still no pending transaction came in hitbtc. Than i checked transcation id and i saw that destination tag was changed. I dont know what to do , i lost 65.5 XRP , can someone help me please!

@fasteddie5
Copy link

fasteddie5 commented Jan 13, 2018

I withdrew 1841 xrp from coinpayments wallet and sent it to binance. It never got there. When I pasted the tag it turns out that there was already an extra zero on the end of my tag. I know the order went through but it was never received by binance. I did make out an order on binance. Will that extra zero on the end of the tag mean that I've lost my funds ? This was 3 weeks ago

@sandeeptripathi06
Copy link

I also transferred from Wallet X to Wallet Y without mentioning the Destination Tag. The coins are deducted from Wallet X but have not made it to Wallet Y. Can you please help me to get this issue resolved.

@str4n63r
Copy link
Author

@sandeeptripathi06 You need to contact Y wallet's support team with all your transaction details and request them for funds.

@sandeeptripathi06
Copy link

In my case Wallet Y is from HitBTC. I opened a ticket with them but they are not responding at all. Did anybody else had the same issue with HitBTC

@sameer937
Copy link

I've same issue with UNOCOIN they are Saying
"Hello
As you can see in the screenshots - you have the wrong destination tag while doing the transaction. Hence it has reached a different destination altogether but not to your wallet at Unocoin. I am afraid we cannot reverse these transactions and credit it back to you.
As you might have noticed, the destination tag is the user id of the customer at unocoin. The destination tag you have mentioned belongs to a different user at unocoin. Even if it is not, due to our auditing purposes of how we operate - we wont be able to reverse a transaction or credit to a different account.
Please anyone tell me where I'll complaint.
Hash
https://xrpcharts.ripple.com/#/transactions/2E243C7BD144E3569DB71CE233312B2C000FCAB488CAFF7D3340EA8E30E5ED76

Instead of 408942 tag I put 40894 .

@Afroj01
Copy link

Afroj01 commented May 8, 2018

Sir your xrp recover your wallet

@Afroj01
Copy link

Afroj01 commented May 8, 2018

19.04.2018 my xrp264 zebpay to wazirx I QR scan but wazirx xrp Wong i sent 264ripple but not delivered my wallet I mistake my xrp so I request my friend any one help my problem solve me

@umitalptekin
Copy link

umitalptekin commented May 8, 2018

Guys ı wanna ask something . I have to send xrp from binance to poloniex. I have to control my xrp deposit adress its true. and control from txid its succes to transfer. but login my poloniex id than look to deposit no have xrp. ı dont use destination tag because poloniex ( no have deposit xrp des. tag ) ı select no tag from binance for transfer. ı cant see my transfer in history?
its problem for poloniex? or ı have false ? help me .

adsiz
adsiz
binance transfer
adsiz

@AnthonyBonilla808
Copy link

Dear @sublimator ,

Correct me if I'm wrong, so what you're saying is now I can get in touch with my recipient wallet's support team with transaction hash from https://xrpcharts.ripple.com which has been provided by my originating wallet? Let me know if I'm missing something.

Regards,
Sateesh

Would you please show me how you recovered your funds please. I just made the same mistake in sending the wrong destination tag

@jakerommel
Copy link

Dear @sublimator ,
Correct me if I'm wrong, so what you're saying is now I can get in touch with my recipient wallet's support team with transaction hash from https://xrpcharts.ripple.com which has been provided by my originating wallet? Let me know if I'm missing something.
Regards,
Sateesh

Would you please show me how you recovered your funds please. I just made the same mistake in sending the wrong destination tag

I did the same thing from uphold wallet to Vauld wallet, could you please tell me how you fixed this?

@sandeeptripathi06
Copy link

sandeeptripathi06 commented Nov 13, 2021 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants