Cameron, Not 100% certain what is happening here. We will need to get this over to our HQ team to research. In the meantime, I went ahead and set the profile as updated for this user so you should be able to log in as this user. Please attempt to do so and let us know how it goes.
I will update this if we figure out the root cause.
Ethan, we have a DB helper to "get" Users that you can pass the "primary_cif" into in order to get a User Record Response. Please note, there can be multiple users for the same "primary_cif". Although I would expect that not be common, it is a use case you need to have support for.
https://docs.q2developer.com/api_references/q2_sdk/db/db_objects/user.html
The SDK does allow for development inside of Q2 Central.
The documentaion and a tutorial located here: https://docs.q2developer.com/tutorials/central/index.html
Part of the User object you will have access to in the request is the "DefaultAddressID". This is what you should use to get that address.
gv
This would typically be a configuration of the extension that would be set at time of deployment. Since this information would be singular per institution, and not change frequently, it can be easily set at deployment time.
What is the response you are getting when they are dropped? If you are getting a 429 - To Many Requests, then that is due to the throttling we must enable on the API Endpoints.
Our API-Tokens are limited to 100 requests per second, with a burst of 200 requests. What this means, if you haven't made any prior requests in the previous 2 seconds, you can make 200 requests. Then you will be able to continuously make 100 requests per second until you reach the limit of your key, which is...
You will want to look at: FundsTransferFromUnassociatedAccountByUiWithPandIandAdditionalData
It will allow you to move from the holding account with the receiving users loginname.
Lisa, while your workflow is ceratinly doable, it seems like it would be helpful if we spent some time showing you around your DB in your test environment and working with you to identify some data.
If you would like to shoot me an email (greg.varnell@q2ebanking.com) we can get some time setup this afternoon or early next week.