Fee reimbursement for trade rp3dpv5j

>_The 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: ..........
Taker: ...........
Deposit: ..........
BTC mining fees lost: .......... eg 0.00005 BTC
Trade fees lost, please state if BSQ or BTC: .......... eg 5.43 BSQ or 0.000088 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: v.10.9
BTC address for reimbursement: bc1qxln8hc7j3nukr7skw24lg05zf8nmvtj575jjh2

>_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._

Review the reimbursement requirements in this issue and compare the submission with issue #197, which is linked as an example. Confirm that the Trade ID, Maker, Taker, and Deposit TXIDs, fee amounts, Bisq version, screenshot, and reimbursement address are supplied in the requested form; completion means the request is complete for support review.

Written by the indexing model from the issue text.