Fee reimbursement for trade CPINE-da6edf14-542b-4ffb-a6db-cd2afa394cc4-1106

Dears, this first time I have this issue, please help! Thx

trade CPINE-da6edf14-542b-4ffb-a6db-cd2afa394cc4-1106

>_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: 588735447cba8b75a34f62800b42457093e050e90b6aea0273c2c2887ac0aa04
Taker: 86baa0234454b9b75ed7468f75c056ec31a7beed03f40eef3fe7488715aa346d
Deposit: N/A

BTC mining fees lost: 0.00003070 BTC
Trade fees lost, please state if BSQ or BTC: 0.000102 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: Bisq-64bit-1.10.6
BTC address for reimbursement: bc1qk7382eq9cymq2qdk72k6675r94ftzu6mf409v5

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

Start by reviewing the textual Maker and Taker transaction IDs, the listed fee amounts, Bisq version, and reimbursement address. Compare the request with issue #197 and verify the transaction details; done means the reimbursement request has a documented decision.

Written by the indexing model from the issue text.