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

Transfers API #32

Open
niccokunzmann opened this issue Dec 26, 2024 · 2 comments
Open

Transfers API #32

niccokunzmann opened this issue Dec 26, 2024 · 2 comments

Comments

@niccokunzmann
Copy link

I would like to use the Transfers part of the API.
https://docs.wise.com/api-docs/api-reference/transfer#list
I would like to be able to create transfers and specifically also list certain transfers.

That should be in a pywisetransfer.transfer, I guess. Would you like to receive a PR?

@jayaddison
Copy link
Owner

@niccokunzmann do you expect transfers to be sent from the accounts of multiple users? If yes, then I'd prefer to add user token authentication support before proceeding further.

@jayaddison
Copy link
Owner

Hey @niccokunzmann - thanks for re-using the code here and getting in touch. I have to be honest: I don't think I can keep up the pace of reviewing and being involved in the changesets, but I am glad that the code is getting more use and development.

There are two main reasons for my slowness: firstly, the only use case I've been involved with so far is for emfcamp/Website -- it's not a frequent activity for me, so my maintenance and motivation are sporadic -- and secondly, I'm a bit paranoid about making mistakes in finance-related code. I think it's important to make high quality FOSS finance code -- I just can't do that myself easily without anxiety.

Separately: I'd also recommend being a little careful about the name of the GitHub organization for your fork; I think foss-fund also exists as a fairly-widely-recognized Microsoft initiative, so it might be less friction to choose something that is clearly separate from that.

Hopefully the package/project name itself is OK - I still have some doubts myself about pywisetransfer (previously pytransferwise, changed because I felt it seemed too official-sounding). I contacted Wise about the naming scheme at the time and they seemed OK with my explanation; if at any point you decide to contact them about your fork, I'll do my best to disambiguate and explain anything about the origins here.

I will still try to do some code review and catch up on your updates; it'll take me some time though, and I can't promise when I'll have more feedback.

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

No branches or pull requests

2 participants