<p></p>
> Even if it did work (seller releases payment to incorrect account name<br>
and number) then having a trade ID as a reference would likely not make a<br>
difference to the seller that is not concerned if other payment details<br>
match.<br>
<br>
That's a good point. I'd add that it's not uncommon for the account number<br>
to be incorrect. People sometimes assume that it doesn't matter which<br>
account they use to fulfil their side of the trade, not realising that<br>
technically they're breaking the trade agreement, which is grounds for<br>
losing their security deposit. I'd say that this happens because people<br>
don't realise that these seemingly little things are part of the security<br>
mechanism protecting the other party (and the other party might not realise<br>
it either). This is tangential to the discussion at hand, but I wanted to<br>
mention it because people following this are those likely to take this<br>
seriously too.<br>
<br>
On Sun, Feb 7, 2021 at 11:16 PM pazza <notifications@github.com> wrote:<br>
<br>
> Previously to release BTC when trading using a bank payment details needed<br>
> to match where; Account name, fiat amount, account number, reference<br>
><br>
> Now to release BTC when trading using a bank payment details needed to<br>
> match where; Account name, fiat amount, account number<br>
><br>
> So all in all I do not think removing the trade ID being included<br>
> compromises security.<br>
><br>
> In the example above of the ebay seller my thoughts are:<br>
><br>
>    - It would not work as account name and account number would not match<br>
>    - Even if it did work (seller releases payment to incorrect account<br>
>    name and number) then having a trade ID as a reference would likely not<br>
>    make a difference to the seller that is not concerned if other payment<br>
>    details match.<br>
><br>
> —<br>
> You are receiving this because you commented.<br>
> Reply to this email directly, view it on GitHub<br>
> <https://github.com/bisq-network/bisq/issues/2869#issuecomment-774769292>,<br>
> or unsubscribe<br>
> <https://github.com/notifications/unsubscribe-auth/AAUW6VGZSQ44QCJGQYYHPOTS537JLANCNFSM4HS7RAMQ><br>
> .<br>
><br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/2869#issuecomment-774771781">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNSROSITO5KJXNDDJFTS54BFDANCNFSM4HS7RAMQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNTSFFU6QBOFJ4P4JLLS54BFDA5CNFSM4HS7RAM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFYXBIRI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2869#issuecomment-774771781",
"url": "https://github.com/bisq-network/bisq/issues/2869#issuecomment-774771781",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>