-
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
Wrong payment information for Moneybeam (N26) Trades #4809
Comments
Thanks for opening your first issue here! |
Hi @stopfeds thanks for the post. I have just had a look at my Moneybeam account. When sending an N26 to N26 payment it asks me for the email address or the phone number of who I would like to pay. This info is needed to send a payment. Are you referring to N26 to N26 payments? or SEPA payments using N26? |
N26 to N26. |
Ok, so you think the following are needed? Name |
Exactly. IBAN would be very important because if I receive the Moneybeam payment the only things I can check are the Name + payment reference. I can't see the phone number / e-mail. |
Ok great, it would be good to get it added then. Makes it much easier to confirm payment. How are you finding trading with N26 on Bisq? Any other feedback out it? @chimp1984 please can you advise how this could be added to a Bisq update? |
Sorry for my late answer. It works perfectly fine. So far, I did over 15 Moneybeam trades and easily over 20 SEPA (with N26 bank account) and there are no issues with N26. No questions etc. Any suggestions to solve this? |
Thanks glad it is going well. I am going to try out N26. Yes, there are a few payment methods with, what appears to be, no active signed accounts. I will look into this and address the problem with the missing IBAN |
@sqrrm |
@sqrrm please consider Uphold also The signed accounts with the problems are the ones that do not have the field 'account owner name' associated to them so that signing cannot be propagated. Revolut is ok as it is so popular. |
Regarding Moneybeam and Uphold, I don't know anything about these payment methods. @pazza83 do you know if they warrant having signing associated with them? Typically, is it easy to reverse transfers? If we need to seed these with some signers we could either add some self signing feature for some other identifier or have a signing event to get some new accounts signed by arbitrators. Problem is that I don't know how we could figure out who to sign so seed these markets. |
Maybe we should think more about utilizing BSQ bonds for such problems. E.g. Seeders need to set up a bond, or having alternative for signing by setup a bond. But first I think we should figure out the chargeback risk and if acceptable best to remove it, would be the easiest solution. |
Awesome idea with the BSQ bond! I'd definitely buy it to get signed. I don't really know how risky it is in terms of chargebacks but I have never been scammed - had more than 15 trades with multiple peers. I am also not aware of any "chargebacks/money back" functions. |
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. |
This is still to be actioned.
Still to do:
This reduces privacy slightly, but the account name of the BTC buyer is shown to the seller when payment is made. The addition of an account name also helps identify the payee. This is now more important since the use of trade ID as a reference has stopped. |
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. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Requested for this change to be actioned here: #6817 (comment) |
Hey all,
If you receive a Moneybeam transaction you can only see the name and the IBAN of the payer in N26. You can't see the phone number as it is shown on step 3 during the Bisq trade. It would be also helpful if the IBAN is visible for the BTC seller so you can compare if the the Reference code + the IBAN is correct.
I think it's unlikely to exploit this issue but it would be an additional security feature if you can also check if the IBAN is correct.
Version v1.4.2
On Windows 10
The text was updated successfully, but these errors were encountered: