# Bisq\>=v1.5.5 empty field for reason of payment in bank transfers

**URL:** <https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334>\
**Category:** Payment methods\
**Created:** [January 31, 2021, 9:40am UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334 "2021-01-31T09:40:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bitsquareuser2306874](https://bisq.community/user_avatar/bisq.community/bitsquareuser2306874/32/2800_2.png) [@bitsquareuser2306874](https://bisq.community/u/bitsquareuser2306874)\
**Post date:** [January 31, 2021, 9:40am UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334/1 "2021-01-31T09:40:47Z")

</div>

Hi,

I checked out the master git branch, compiled & started it and was welcome with this information:

 ![image](https://bisq.community/uploads/default/original/2X/0/0b252edf2a40822c14cad1deae8d935b9db137a6.png)

saying, the field for reason of payment in bank transfers should be empty in future. Is there a any date this will be applied? I wonder If two peers have version v1.5.5 and v1.5.4 but do trade what will happen. Or one would be missing the tradeid from payments?

In my opinion, there is PRO:

- increased privacy.
- less oblivious you trade on bisq for bank account statement.

Contra:

- could open some type of scam,
- where you as seller have less way to verify the payment come from trade partners own bank account…

By quick search couldn’t find more information regarding this. So if you have please link to. 🙂

[https://github.com/bisq-network/bisq/pull/5080#discussion\_r557970830](https://github.com/bisq-network/bisq/pull/5080#discussion_r557970830)

---

<div class="post-metadata">

**Author:** ![tieck](https://bisq.community/letter_avatar/tieck/32/6_22734026db12803ebb3e059622ac3534.png) [@tieck](https://bisq.community/u/tieck)\
**Post date:** [January 31, 2021, 2:41pm UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334/2 "2021-01-31T14:41:35Z")

</div>

This change has been announced on twitter

[https://twitter.com/bisq\_network/status/1354110098486874112](https://twitter.com/bisq_network/status/1354110098486874112)

It will be in effect as soon as version 1.5.5 will be released.

---

<div class="post-metadata">

**Author:** ![Pazza](https://bisq.community/user_avatar/bisq.community/pazza/32/2703_2.png) [@Pazza](https://bisq.community/u/Pazza)\
**Post date:** [February 1, 2021, 2:46am UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334/3 "2021-02-01T02:46:24Z")

</div>

> [@bitsquareuser2306874](#):
>
> By quick search couldn’t find more information regarding this. So if you have please link to. 🙂

Here is some background info:

> <https://github.com/bisq-network/bisq/issues/2869>
>
> Its pretty easy for a bank that has recognized the format of a Bisq trade "reaso…n" to identify which its customers are trading bitcoin with Bisq.
> 
> Could you make an option for the user to pick a randomly-generated trade reason that's less obvious?
> 
> Maybe source a couple hundred reasons from Venmo's public data or something and then randomly pick form that, or something...I dunno

> <https://github.com/bisq-network/bisq/pull/5080>
>
> Implements https://github.com/bisq-network/bisq/issues/2869
> 
> \- Adds popup at s…tartup with rule change for users who have already a fiat account.
> \- Change TAC text to leave field empty and not use Bisq, BTC or trade id
> \- Change buyer popup in trade process to tell to leave field empty
> \- Remove text fields with reason for payment in trade process
> \- Remove text from popup for seller to check for reason for payment to match trade id
> 
> Hope I did not missed some...
> 
> @m52go @pazza83 I am not 100% sure if the popup at startup is enough to announce the change. I think we should additionally communicate it clearly in all our channels and of course to our support guys.

---

<div class="post-metadata">

**Author:** ![Conza](https://bisq.community/user_avatar/bisq.community/conza/32/2807_2.png) [@Conza](https://bisq.community/u/Conza)\
**Post date:** [February 3, 2021, 1:00am UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334/4 "2021-02-03T01:00:34Z")

</div>

_\> “You are free to discuss via trader chat if an alternate “reason for payment” would be suitable to you both.”_

---

<div class="post-metadata">

**Author:** ![bitsquareuser2306874](https://bisq.community/user_avatar/bisq.community/bitsquareuser2306874/32/2800_2.png) [@bitsquareuser2306874](https://bisq.community/u/bitsquareuser2306874)\
**Post date:** [February 3, 2021, 10:12am UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334/5 "2021-02-03T10:12:22Z")

</div>

> I see the Subject does not match the tradeID. the reason of payment is just called empty?

> Bisq’s latest official directions dictated that nothing more should be written in the payment description. I did not understand: so the payment has not arrived?

> Yes, I read the changes too. I just thought, it applies to bank wire transfer payments only. I’m not sure if “blank payment reason” rule now includes moneybeam and/or revolut payments?

> I don’t think for MoneyBeam / Revolut it is any different… I think leaving the field blank causes even less suspicion for the bank, but I don’t know.

Not clear for everyone now what all applies the rule changes to?

---

<div class="post-metadata">

**Author:** ![Conza](https://bisq.community/user_avatar/bisq.community/conza/32/2807_2.png) [@Conza](https://bisq.community/u/Conza)\
**Post date:** [February 3, 2021, 10:50am UTC](https://bisq.community/t/bisq-v1-5-5-empty-field-for-reason-of-payment-in-bank-transfers/10334/6 "2021-02-03T10:50:14Z")

</div>

Rule changes apply to everything currently. See end of github #2869 above regarding _“I think leaving the field blank causes even less suspicion for the bank, but I don’t know.”_ = most likely yes.

There was point of contention/issue raised by a seller of SEPA. I said to make a github request etc. if that was the case etc. don’t think one has.
