Fee reimbursement for trade F6WVE413

>_The XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash)._

>_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!**_

Maker: ef77510631ebaf67639a8e741dd629905bf9bd63eb46fdae94d6082d678b5238
Taker: 989be83467c009d78c9795a73b776229e6fd675650f35618ca0699670a6bafce
Deposit: N/A
BTC mining fees lost: 0.00002330 BTC
Trade fees lost, please state if BSQ or BTC: 0.00007500 BTC

>_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: 1.10.7
BTC address for reimbursement: bc1qmh6kfyjy22xqpmx38esv0qapa3kawt8f6cft2t

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

Other notes: Trade failed with BuyerVerifiesPreparedDelayedPayoutTx:
TxIds of myPreparedDelayedPayoutTx and peersPreparedDelayedPayoutTx must be the same.

The deposit transaction was not created.

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

Start by comparing the request with support issue #197 and verify that the screenshot and textual Maker, Taker, and Deposit TXIDs meet the stated template. Done means the support team has enough information to decide and process the reimbursement; no repository file or test is identified.

Written by the indexing model from the issue text.