One finX user per application user
If the use case requires interacting with the finX API for one user over an extended period of time, it is recommended to create one finX user per application user. This way, the data of each of your users is securely separated.
In this scenario, it is recommended to create the finX users with a username directly mappable from your application user IDs, e.g. using <your user ID>@finX.<yourapplication domain>.
That way you do not have to save any additional information and still do not block email address of your user for explicit finX API usage. A similar, but more secure, mapping is recommended for the user's password.
One finX user per application transaction
It is possible to only integrate the finX API as part of processing a transaction, e.g. to verify account owner information. In this scenario, it is recommended to create one finX user per transaction and delete it after the finX API integration part of the transaction processing is completed.
For the same reasons as in the other case, a simple mapping between your transaction and the finX username/password is recommended for this case as well, e.g. <your-transaction-id>@finx.<your-application-domain> as username.
In order to keep transaction processing time as short as possible, we recommend deferring any clean-up activities.