New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fee reimbursement for trade 4955784 #141
Comments
Hey @cbeams I'm contacting you regarding tradeID 4955784
|
No payment should have been made, because the transactions for this trade never completed. The deposit transaction was never broadcast, and you should not have had the opportunity to see and/or click on a 'Payment Started' button. Are you saying that you've paid 226 EUR to the seller and never received the seller's BTC for this trade? Are you absolutely sure? We would have to re-open this dispute, contact the seller, confirm that he received your payment, and ask him to send you the BTC directly, outside of the Bisq app. Please make absolutely certain this is necessary, because it's a bit of a hassle to make that happen. To be clear, this GitHub issue was created to reimburse you and the seller for lost transaction fees due to this failed trade—not to "reimburse" your EUR payment. The EUR payment never should have been made in the first place. Nevertheless, we'll get this sorted out if indeed you did send payment to the seller prematurely.
These should be handled independently, in their own disputes. If you have not opened disputes for them yet, please do with CMD-O. Please let me know what the trade IDs for each are, and I'll see if I'm the arbitrator. We can follow up from there. |
Yes
Yes
I know, I just thought it would be best to ask here first as I don't know how to proceed. I deeply apologise for that mistake. To my defence, I'm also on another issue regarding N26 MoneyBeam and mistook one for the other, realising my error only too late.
Don't worry they have been opened on their own channel and haven't been mixed. The only issue at hand here is that if you are in the middle of 2 trades of the same amount and through MoneyBeam, then are asked a request through MoneyBeam, it's hard to know if it was for trade A or B. My mistake I am now only looking for either getting the BTC or my money back. |
Understood, @regnarock. I've sent an (encrypted) email to the seller letting them know what happened and asking them to either send you the BTC trading amount or to refund your 226 EUR. I'm waiting for their response now. In the meantime, please send me a bitcoin address to which they can send the BTC if they go for that option. You can send it to me via email at chris@beams.io with the trade ID in the subject line. |
Rodger that! Sent. Thank you =) |
The fee reimbursement was added to batch file. @cbeams let me know if I need to move this issue out of it. I will leave it on the list, unless you say otherwise. I am not sure how the above issue affects this, so want it documented here. |
Thanks for calling this out, @KanoczTomas. We actually did work together to settle the trade in the end, so I would revert this reimbursement. This is effectively the equivalent of someone opening a dispute because of a non-broadcast tx, and that trade getting settled via arbitration. We don't award fee reimbursements in those cases, so for consistency's sake, we shouldn't do so here, either. |
Closing as reimbursed via the batch transaction documented at #101 (comment). |
Disregard. This reimbursement was reverted as described above. Should have been closed as invalid. |
Maker: 621c468c9b67f271e649561c7edb225d271080a907b855f2d263e4dec208a319
Taker: 734cc6e4dad11324fc0519e663cab461e2abd6a73fc33ff6dc73af54d27d45d8
Deposit: fe598ab3e405f526ff4407379753e939371d6c824cbcf320baaa692923c11409
Bisq version:
The text was updated successfully, but these errors were encountered: