Reimbursement for trade 4QF5BMW

>_The screenshot from the Bisq client must have the **Trade ID**, **Deposit**, **Maker** and **Taker** TXIDs visible. Of course some trades do not have all 3 types, that is ok. Make sure all private information is covered (like bank accounts, name, etc). **Do not upload images where sensitive private data is visible!**_

Reimbursement for trade 4QF5BMW

I am BTC buyer as taker for EUR.
Trade amount and asset: [AMOUNT] BTC for [X ASSET]
Deposit amount: 0.0003 BTC

Maker: 685d0b5e9fae16916ddb2b2d9cf02ca748f0ba8c7a8d5d1ca154f5b1d15dcab0
Taker: d30d7f0aa06ffb4afd521435ce69b231a92e3ba7fb3aa8e2b0853305e2b7bb7a
Deposit: 0.0003 BTC
Mining fee: 0.000033090 BTC
Delayed payout: ..........
BuyerMultiSigPubKeyHex: ..........
SellerMultiSigPubKeyHex: ..........

Reimbursement amount: 0.000339 BTC
Reason for reimbursement: BuyerVerifiesPreparedDelayedPayoutTx

BTC address ownership proof:

>_Repeat the above for each trade you need to be reimbursed_

>_A reimbursement request has to contain textual representation of **Maker**, **Taker** and **Deposit** TXIDs (copy them from the client to the issue). **All TXIDs that are visible in the screenshot must be copied to the issue in text form! Please use exact form for Maker/Taker/Deposit - no abbreviations like M:, T: or adding extra characters like "Maker TX:", etc. Leave those fields as they are and replace the "........" with the appropreate txid**_

Bisq version: Bisq-64bit-1.10.6

>_Provide the Bisq client version to help developers identify the causing issue._

Other notes:

>_Issue [#197](https://github.com/bisq-network/support/issues/197) can be used as a good example of a correct reimbursement request._

>_Ping @refund-agent2 and your mediator_

No repository files, tests, or code entry points are identified. This issue is a trade reimbursement request for Bisq version 1.10.6, requiring maintainer review of the transaction details and reimbursement reason rather than a newcomer code change.

Written by the indexing model from the issue text.