-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
payment reason BLANK message alert when trading (some banks require to write a reason) #5395
Comments
Thanks for opening your first issue here! |
Hi @Tracachang thanks for the issue. I ran into this issue recently when taking on offer to buy BTC on Bisq using a bank that would not accept a blank reason for payment. It pre-populated instead with my name. I think entering you name (same as bank account) is an acceptable solution to this, as is entering a dash. If the trader enters something not agreed there would be a penalty, see Trade Penalties Table |
Thanks @pazza83, then it is clear, in case of a reason is required must be dash or name. Do I close this issue? Or I keep it open until it is fixed? |
Hi @Tracachang leave it open and I will add it to the wiki before commenting back here and then it can be closed. |
Hi @Tracachang I have included the information here: https://bisq.wiki/Trading_rules#Leave_the_.22reason_for_payment.22_field_empty Thanks for opening this issue it can now be closed. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello,
As a buyer, when a trade is accepted and deposit confirmed you receive an alert to pay precising that transfer reason must be BLANK. This information is "incomplete" and I think it would be good to add from bisq FAQ:
I think in case of a reason is required should be the "-" the standard since it does not give any information, even if "payment" it is trivial too, it would not be something that people would use in most of EU countries where English is not spoken.
The text was updated successfully, but these errors were encountered: