Skip to content
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

Change rule for "reason for payment" field to not use trade ID but leave it empty #5080

Merged

Conversation

chimp1984
Copy link
Contributor

@chimp1984 chimp1984 commented Jan 14, 2021

Implements #2869

  • Adds popup at startup 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.

@chimp1984
Copy link
Contributor Author

chimp1984 commented Jan 14, 2021

Screen Shot 2021-01-13 at 23 31 48

Screen Shot 2021-01-13 at 23 33 09

Screen Shot 2021-01-13 at 23 44 31

@chimp1984
Copy link
Contributor Author

@m52go Could you have a look to the text changes?

@Conza88
Copy link

Conza88 commented Jan 14, 2021

REALLY think if this is going ahead to advise or push folks to continue discussing in chat with trading partner. That's the important part. Communication.

There's no indication anywhere why this change is being made either. It will likely make life harder for extensive traders, no? That's not ideal. They'd want to know WHY this sudden change. I think stating clearly the rationale would help immensely.

Obviously the high volume traders are more at risk getting banned as well, so should support a move that lessens that.

@m52go
Copy link
Contributor

m52go commented Jan 14, 2021

Screen Shot 2021-01-13 at 23 33 09

^ there is a lot of text on this screen...this reduces the chance that the user reads any of it.

I'm not sure the parts on multiple confirmations, bank details, copy/paste, etc. are that important.

Suggestion to simplify:


Your trade has reached at least 1 blockchain confirmation.

Please pay 303 EUR via the specified payment method to the BTC seller. You'll find the seller's account details on the next screen.

Important: when making the payment, leave the "reason for payment" field empty. DO NOT put the trade ID or any other text like 'bitcoin', 'BTC', or 'Bisq'.

If your bank charges you any fees to make the transfer, you are responsible for paying those fees.


@Conza88
Copy link

Conza88 commented Jan 14, 2021

Nice. Is there a potential wiki link if someone is new, or old school and wants to know more? Something that may cover why we're no longer suggesting putting in trade ID? It's a massive step from MUST have trade ID, to DO NOT.

Your trade has reached at least 1 blockchain confirmation.

Please pay 303 EUR via the specified payment method to the BTC seller. You'll find the seller's account details on the next screen.

Important: when making the payment, leave the "reason for payment" field empty. DO NOT put the trade ID or any other text like 'bitcoin', 'BTC', or 'Bisq'. (i) This is to reduce the risk of fiat accounts being deactivated or banned. You are free to discuss via trader chat if an alternate 'trade ID' would be suitable to you both.

If your bank charges you any fees to make the transfer, you are responsible for paying those fees.

Added: "(i) This is to reduce the risk of fiat accounts being deactivated or banned.

You are free to discuss via trader chat if an alternate 'trade ID' would be suitable to you both."

Ideally the (i) only appears when hovered over, not sure if can be done in popup.

@chimp1984
Copy link
Contributor Author

^ there is a lot of text on this screen...this reduces the chance that the user reads any of it.

I'm not sure the parts on multiple confirmations, bank details, copy/paste, etc. are that important.

I agree, but I would prefer to keep that for another PR. There are more popup text to improve but as the text is composed of several blocks depending on payment method its also not that trivial and need then better testing with the diff. payment methods.

Any dev who wants to pick that up?

@m52go Can you check if there are reference on the webpage or other resources regarding that fields?

@chimp1984
Copy link
Contributor Author

Nice. Is there a potential wiki link if someone is new, or old school and wants to know more? Something that may cover why > we're no longer suggesting putting in trade ID? It's a massive step from MUST have trade ID, to DO NOT.

Yes I agree, but I think in the app we should keep things minimal and that context is only relevant for existing users not for new users. Maybe @m52go has a suggestion how to communicate best the reason for the change. To add a sentence to the popup at startup might be ok as well, as its only shown to existing users.

@m52go
Copy link
Contributor

m52go commented Jan 14, 2021

Can you check if there are reference on the webpage or other resources regarding that fields?

Yes I'll check. There are probably some spots on the wiki, not sure about website.

@cbeams
Copy link
Contributor

cbeams commented Jan 15, 2021

utACK. What about i18n versions of these messages? Is the process tight enough there to ensure we get translations (for the most important languages) coordinated with this release?

Copy link
Contributor Author

@chimp1984 chimp1984 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK. What about i18n versions of these messages? Is the process tight enough there to ensure we get translations (for the most important languages) coordinated with this release?

@ripcurlx @m52go Could you push translaters, or at least delete the old entries so english will be the fallback?

@m52go
Copy link
Contributor

m52go commented Jan 16, 2021

When is the next release expected? cc @MwithM

@chimp1984
Copy link
Contributor Author

When is the next release expected? cc @MwithM

I am not sure, but I guess code freeze will be soon. @ripcurlx Any concrete date?

@Conza88
Copy link

Conza88 commented Jan 16, 2021 via email

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK tested locally with Amazon, USPSMO and Transferwise payment methods.

@ripcurlx
Copy link
Contributor

When is the next release expected? cc @MwithM

I am not sure, but I guess code freeze will be soon. @ripcurlx Any concrete date?

Codefreeze will be on Wednesday, but I'll update the translation files the week after. So there should be enough time for translators to come up with proper translations.

Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@ripcurlx ripcurlx merged commit 88c4272 into bisq-network:master Jan 19, 2021
@pazza83
Copy link

pazza83 commented Jan 22, 2021

Sorry, I missed this.

I had a look at the text and it all looks great to me. I am sure there will be some teething issues with traders using trade ID as payment references but these will quickly be sorted out and the odd trader using them until informed otherwise does not seem like much, if any, risk.

I agree the Wiki / website needs to ensure that it is edited to include the new trade protocol. I will contact @m52go on Keybase about what is needed and agree a plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants