Partners and Users

Partners and users allow the hierarchical organization and grouping of PayData Accounts. While child-partners are optional, the creation of users is required because all PayData accounts need to be assigned to a user.

In the simplest case, the main partner has a single user that contains all accounts. But generally, a separate user should be created for each enduser. Additionally, users can be grouped under child-partners if they belong to the same entity (like a tax advisor office).

The following diagram shows the use of child-partners to separate the users for each tax advisor office from each other.

warning

We strongly advice to not create accounts belonging to different endusers under the same PayData user as support tools might display all accounts for a user. This can lead to human error and accidental data leaks.

Design Considerations

• User names must be unique per partner / child-partner. You can re-use user names when they belong to different child-partners.
• By using child-partners, the user management can be delegated to another party or on-premise system without compromising the main partner or other child-partners.
• User tokens can be made available to endusers and allows them direct access to the PayData-API.