# Problem with transaction TIMEOUT, BTC tax and security deposit paid

**URL:** <https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332>\
**Category:** Support\
**Created:** [April 25, 2018, 3:58pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332 "2018-04-25T15:58:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rpseng](https://bisq.community/letter_avatar/rpseng/32/5_5575768a8748004e209b776fc1b2916d.png) [@rpseng](https://bisq.community/u/rpseng)\
**Post date:** [April 25, 2018, 3:58pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332/1 "2018-04-25T15:58:22Z")

</div>

Just took an order, paid the tax and the security deposit. Somehow it got stuck and I got a TIMEOUT error message.

Transaction id is 9hoaam0e-4df2b5cb-4dbe-403b-bffd-d3b3349b73aa-067. Apparently the order is still opened. How to actually take the order or get my funds back??

Thanks.

---

<div class="post-metadata">

**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\
**Post date:** [April 25, 2018, 6:10pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332/2 "2018-04-25T18:10:31Z")

</div>

Your funds probably didn’t move anywhere, Bisq just might not be showing it, so there is nothing to worry about. You can always access them with an emergency wallet tool by pressing cmd+e.

In case the trade actually successfully opened and your funds got locked in a multisig, you would need to open a dispute with cmd+o or contact the arbitrator over this forum.

That looks like a trade id, not a transaction, so I can’t help you with that. Arbitrators will be able to look at your trade id and see if it is their trade.  
You can look for deposit transaction id and use a block explorer to determine if your funds ever moved from your wallet.

---

<div class="post-metadata">

**Author:** ![rpseng](https://bisq.community/letter_avatar/rpseng/32/5_5575768a8748004e209b776fc1b2916d.png) [@rpseng](https://bisq.community/u/rpseng)\
**Post date:** [April 25, 2018, 6:28pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332/3 "2018-04-25T18:28:41Z")

</div>

Thank you for the response. I could retrieve most of my funds.

However, ended up loosing 0.0015 BTC in fees/taxes which translates today to more than 10 USD. It is just sad to loose some money on a bug…

---

<div class="post-metadata">

**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\
**Post date:** [April 25, 2018, 7:05pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332/4 "2018-04-25T19:05:39Z")

</div>

Don’t worry, you can contact @cbeams about that.

---

<div class="post-metadata">

**Author:** ![Noah](https://bisq.community/letter_avatar/noah/32/5_5575768a8748004e209b776fc1b2916d.png) [@Noah](https://bisq.community/u/Noah)\
**Post date:** [May 8, 2018, 2:53pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332/5 "2018-05-08T14:53:31Z")

</div>

This happened to me yesterday twice! In bth cases I got TIMEOUT message. I lost the miner fee; the “locking” key of 0.1 BtC was refunded.

Trade shows in history, and trade state says: TAKER\_FEE\_PUBLISHED

---

<div class="post-metadata">

**Author:** ![rpseng](https://bisq.community/letter_avatar/rpseng/32/5_5575768a8748004e209b776fc1b2916d.png) [@rpseng](https://bisq.community/u/rpseng)\
**Post date:** [May 8, 2018, 3:33pm UTC](https://bisq.community/t/problem-with-transaction-timeout-btc-tax-and-security-deposit-paid/5332/6 "2018-05-08T15:33:17Z")

</div>

Dear Noah, sorry to hear that you also lost the fees.

In my case I did not requested any refund and let it be. Mainly because in my second attempt all went well and I got a very nice deal in that transaction.

I hope this bug (or whatever it is) can be prevented in future versions.

All the best.
