# Painfully Slow Trade - 6 Days of Worry and Uncertainties

**URL:** <https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022>\
**Category:** Support\
**Created:** [September 27, 2017, 6:17am UTC](https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022 "2017-09-27T06:17:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![herewego](https://bisq.community/letter_avatar/herewego/32/5_5575768a8748004e209b776fc1b2916d.png) [@herewego](https://bisq.community/u/herewego)\
**Post date:** [September 27, 2017, 6:17am UTC](https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022/1 "2017-09-27T06:17:35Z")

</div>

I did my first trade Sep 23rd, it’s been 4 days already and I haven’t been able to complete it yet.

I sold 0.1 BTC to a trader from Germany. I’ve already received the money he transfered by SEPA.

But I think he forgot to mark the trade as paid so now I’m stuck and unable to release his BTC.

What should I do?

What if the trader thinks I’m intentionally holding his BTC and start a charge-back with the bank?

---

<div class="post-metadata">

**Author:** ![valankar](https://bisq.community/letter_avatar/valankar/32/5_5575768a8748004e209b776fc1b2916d.png) [@valankar](https://bisq.community/u/valankar)\
**Post date:** [September 27, 2017, 8:37am UTC](https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022/2 "2017-09-27T08:37:35Z")

</div>

It could be the bug mentioned [here](https://forum.bisq.io/t/one-side-wait-until-payment-has-started-and-the-other-wait-until-payment-arrived/3002).

If you have contact information, you can send them an email. Or can open dispute (ctrl/cmd-o) and explain situation.

---

<div class="post-metadata">

**Author:** ![herewego](https://bisq.community/letter_avatar/herewego/32/5_5575768a8748004e209b776fc1b2916d.png) [@herewego](https://bisq.community/u/herewego)\
**Post date:** [September 27, 2017, 10:05am UTC](https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022/3 "2017-09-27T10:05:00Z")

</div>

Most likely is, dispute opened, thanks a lot!

---

<div class="post-metadata">

**Author:** ![cosmasta](https://bisq.community/letter_avatar/cosmasta/32/5_5575768a8748004e209b776fc1b2916d.png) [@cosmasta](https://bisq.community/u/cosmasta)\
**Post date:** [November 27, 2017, 1:38pm UTC](https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022/4 "2017-11-27T13:38:07Z")

</div>

I also paid Euro to someone in the Czech Republic 4 days ago. My wallet is still stuck at “awaiting payment confirmation from seller.” I hope the SEPA instant payment is operational (but I hear only in 2018) and it will alleviate this problem even if it was a bug. In this day and age, waiting 4 days for a payment to go through is simply unacceptable! The bitcoin price difference can change by some €2000 before seller confirms to send it to buyer, thus leaving either party unhappy. Even in developing countries, there is now near-instant mobile money transfer. Also, is there no way to prod the seller, like a ‘poke’ in Facebook or sms? Waiting for a wallet to be online before a transaction is completed is also a problem. The sending wallet could ask permission from the receiving wallet’s device in order to open a parallel communication channel (sms?, e-mail?, pop-up notification?). I know mobile numbers are not required and that no 3rd party should have access to temporary buffer funds. Browser-based web-wallets at other exchanges like Remitano handles security and buffering/notifications seemlessly…

---

<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:** [November 27, 2017, 6:48pm UTC](https://bisq.community/t/painfully-slow-trade-6-days-of-worry-and-uncertainties/3022/5 "2017-11-27T18:48:47Z")

</div>

Yeah, banking system can be pretty slow.  
Communication between trading peers has been purposely avoided by now in order not to open up channels for social engineering attacks.
