-
Notifications
You must be signed in to change notification settings - Fork 46
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
Confirmation Withdraw #39
Comments
If i understood it correctly, you need to ask the support of your broker to remove the withdraw confirmation by email |
Oh, right, thanks! |
Same issue here. Through websocket send message U6, then send message u24 with second factor from e-mail AND from OTP (phone token). All I can get with Foxbit (provider 4) is "Not Authorized". |
Guys, thanks for report, i gonna take a look at it more closely and understand what's going on |
Ok, i've a better understanding now. Withdrawals through the API won't work for now, so there's two possible solutions.
So, is absolutely possible to disable withdraw confirmations. Those things is gonna be improved soon, let me know if you guys have any other question. |
Thanks for the help, I talked again with Foxbit support and they told me that it will not be possible to perform the procedure at this time. |
Hello
When I make a withdrawal request through WebSocket it asks me for the secondFactor since I have activated it in my account, and for Rest it sends me an email with a code to confirm.
There is no way you do not need any code to confirm the withdrawals, as an example in other exchanges that if they enable the API service they do not need confirmation?
The text was updated successfully, but these errors were encountered: