-
Notifications
You must be signed in to change notification settings - Fork 21
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
Authorizing transfers? #7
Comments
Hey @vvug thank you! This is something I plan to add, yes. I'm actually doing some research about it to figure it out if it's possible to authorise the transfer without a smartphone. Worst case scenario is that you create the transfer in the CLI and will have to open the app on your phone to authorise it. If my hands are not tied by N26 here, I would like to have everything done via CLI as well :) |
@guitmz any progress? |
@stevenklar currently is not possible without a smartphone (honestly I don't know if it will ever be, it is a good security practice to keep it this way). So my plan is to try to implement the transaction creation via command line and only having to authorise via smartphone. Hopefully I find some time to implement this soon |
I agree with you. It feels more safe to approve auto created transactions, just to be sure everything is correct. Its money, so... Well that would be fine also to create transactions and review them later. Does N26 notify you for created transactions which needs approvel like other complete transactions? |
It should. For example here in Germany when I use N26 with SOFORT gateway, I get a notification in the smartphone asking me to confirm the transaction. After its confirmed, the gateway continues the process normally. I will do some testing when I can and report back here for you guys |
for future reference, here you can find an example on how to build a POST request to make transfers |
This n26 client is great! Do you plan to add a function to authorize payments? This would be very convenient as it would allow to fully use the N26 account without a smartphone.
The text was updated successfully, but these errors were encountered: