Fee reimbursement for trade lztkmdl

>_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: 662522d2a30e28cb125bf8ef22221cf3aad84fb7165eff381ebeaeece40b3048
BTC mining fees lost: 0.000075 BTC
Trade fees lost, please state if BSQ or BTC: 0.015 * 0.0015 = 0.0000225 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: bc1qd9x2rqr4fznda0t5ac0aqjj8ucwrcx92hrwhn7

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

Other notes: Deposit tx was never published so not concerned with trade amount or security deposit.

>_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 this request with issue #197 and the Bisq 1.10.7 trade details. Verify that Maker, Taker, and Deposit TXIDs are supplied in text and that the screenshot redacts private data; done means the reimbursement request is complete and ready for review.

Written by the indexing model from the issue text.