What is a User?
When a referrer Referrer or merchant Merchant entityis added to the platform and API, creating a User Login (User)is necessary in order for that entityto access the Portal. An example
Creating a User Login requires a unique email address, a username, and a password. By default, a user’saccess to the Portal is dependent on the type of account it is associated with.
...
Example:
...
A Merchant’s User Loginwill only give them access to the parts of the Portal that are relevant to
...
Merchants, while a User Loginconnected to a
...
Referrer entitywill have access to additional sections relevant to them.
...
Referrer partners have the flexibility to give or restrict their clients access to the Portal. Depending on your portfolio’s specific needs, we offer a number of integration options that allow your clients to perform essential Payrix functions directly on your platform or for you to manage these aspects on their behalf.
...
Create a User
...
Step 1: From the Portal Dashboard menu, click Users (under the Management tab.)
...
Step 2: In the Users menu, click the Add User Button to reveal the Create a New User lightbox.
...
...
When Merchants or Referrers want to add a new user to their business on the platform (add a new user associated with their entity). The user will need to provide some information, name, phone number, and email as examples, to get started. From here the user will be provided with a Role, username, and password associated with that information and tied to the entity that created the User. The steps below will demonstrate how to set up a new User with a login.
Expand | ||
---|---|---|
| ||
Step 1: From the Portal Dashboard menu, click Users (under the Management tab.) Step 2: In the Users menu, click the Add User Button to reveal the Create a New User lightbox. Step 3: Set the new user’s Role, Username, Password, Full Name, and Email Address. Then click the ADD USER button. |
Info |
---|
Note on Role Access Levels: |
...
Info |
---|
Note on Access Templates: An Access Template can be used while creating a new user by clicking the ADD A TEMPLATE link in the Create a New User lightbox. Access Templates can set predetermined roles for new users to streamline the process. Read more about Access Templates here. |
...
Step 4: After being returned to the Users menu, click on the user you created to be redirected to that user’s User Profile menu.
...
Step 5: In the User Profile Menu, you can edit individual settings for the specific user.
...
Step 4: After being returned to the Users menu, click on the user you created to be redirected to that user’s User Profile menu. Step 5: In the User Profile Menu, you can edit individual settings for the specific user.
|
Parent User vs Child User
A Parent User is a user that was the first to be set up to access an entity. (Such as a Merchant. In some cases, a Referrer).
The Parent User owns the merchant resource and has access to the login to be able to impersonate their view.
Each entity can only have one Parent User login setup and by default, that login will have access to the entity account they are associated with.
A single user can be associated with multiple entities; however, by default, the login associated with an entity will be the user who first has access to that account.
A Child User is any user created by a Parent User. Either using the Portal or via API.
Each Child User will and must be tied to an entity (likely a merchant account).
Note |
---|
Parent User Visibility of Child UsersThe Parent User of any Child user has the ability to access and view the Child user’s associated entity (merchant) because it’s hierarchy is the source of the Child user’s access to the portal. As a result, the Parent User will have full view of the Child User’s merchant account. The Child user however is unable to view the Parent User’s view. |
How to Login to view a Child User’s Portal:
Step 1: From the Portal Dashboard menu, click Merchants (under the Management tab.)
...
Step 2: Click on the Login icon (located in the right hand column of the merchant list) to log in as the desired user (see below).
...
Step 3: You will now be redirected to the Dashboard that your Child User sees, with Full Admin Access typically being available to the Parent User to Add, Edit, View, or Change certain information.
...
Warning – DO NOT Deactivate Referrer-Level Parent Users.
...
Note: An Access Template can be used while creating a new user by clicking the ADD A TEMPLATE link in the Create a New User lightbox.
Access Templates can set predetermined roles for new users to streamline the process. Read more about Access Templates here.
Note |
---|
Warning: Role access levels can only be assigned to new users based on the level of access the parent user has. For example, a Merchant can not give “Referrer Full Access” to another user, but a Referrer can grant this level of access to a Merchant. |
...
Parent & Child Users
A Parent User is a user that was the first to be set up to access an entity. (Such as a Merchant. In some cases, a Referrer). The Parent User owns the Merchant resource and has access to the login to be able to impersonate their view. Each entity can only have one Parent User login setup and by default, that login will have access to the entity account they are associated with. A single user can be associated with multiple entities; however, by default, the login associated with an entity will be the user who first has access to that account.
A Child User is any user created by a Parent User. Either using the Portal or via API. Each Child User must be tied to an entity (likely a Merchant account).
Note: The Parent User of any Child user has the ability to access and view the Child user’s associated entity (Merchant) because it’s hierarchy is the source of the Child user’s access to the portal.
As a result, the Parent User will have full view of the Child User’s Merchant account. The Child user however is unable to view the Parent User’s view.
Note |
---|
Warning: Do Not Deactivate Referrer-Level Parent Users. Deactivating Referrer-level Parent Users that are associated with the entity’s API key or are the primary parent user login will remove access from all associated Child Users to their respective entity. |
Tip |
---|
Instead of Deactivating A Parent Login..
Tip: In the event that a person acting as the Parent User needs to be changed, use the steps below to repurpose the Parent User with new information and login credentials.
|
...
Roles are used to determine how much access a user has to see, edit, create, or delete information on the portal. Roles can be assigned to users to further provide or extract the access capabilities they're intended to have.
Each user has a set of default Roles, as well as customizable parameters allowing you to restrict or allow access to specific pages and functions of the Portal.
Info |
---|
Referrer Access Roles vs Merchant Access Roles Within the Default Access Roles, there are Referrer and Merchant-level access roles (as shown above). The Referrer has the unique ability to create and manage ALL merchants under a Referrer as well as manage Sub-Referrers. The Referrer also has the ability to login to view the merchant portal. Whereas the Merchant Access Roles only allow for the management of that respective Merchant and its Sub-Merchants. |
Setting Default User Roles
To set the default (primary access) roles for a new user:
Step 1: From the Portal Dashboard menu, click Users (under the Management tab.)
...
Step 2: In the Users menu, click the Add User Button to reveal the Create a User lightbox.
...
How to Log In to View a Child User’s Portal
In scenarios where a Parent User (Referrer) would like to view a Child User’s (Merchant) Portal view for troubleshooting, support, or reasons related to fraud and risk, the steps below will demonstrate how to access this portal view.
Expand | ||
---|---|---|
| ||
Step 1: From the Portal Dashboard menu, click Merchants (under the Management tab.) Step 2: Click on the Login icon (located in the right-hand column of the Merchant list) to log in as the desired user (see below). Step 3: You will now be redirected to the Dashboard that your Child User sees, with Full Admin Access typically being available to the Parent User to Add, Edit, View, or Change certain information. |
...
What are Roles?
Roles are used to determine how much access a user has to see, edit, create, or delete information on the portal. Roles can be assigned to users to further provide or extract the access capabilities they're intended to have.
Each user has a set of default Roles, as well as customizable parameters allowing you to restrict or allow access to specific pages and functions of the Portal.
Set Default User (Primary Access) Roles
Expand | ||
---|---|---|
| ||
Step 1: From the Portal Dashboard menu, click Users (under the Management tab.) Step 2: In the Users menu, click the Add User Button to reveal the Create a User lightbox. Step 3: Select the desired Default Role from the Role drop-down. Then, set the Username, Password, Full Name, and Email Address and click the ADD USER button. |
...
Set Custom User Roles
Expand | ||
---|---|---|
| ||
Step 1: After being returned to the Users menu, click on the user you created to be redirected to that user’s User Profile menu. Step 2: Select the Role tab from the User Profile Menu bar Step 3: Click the “Select resources to allow” drop-down next to each desired Role Category Step 4: Toggle the desired Role Resources check boxes. Step 5: To enable sub-resources of Role Resources, click the Advanced toggle switch in the upper right-hand corner of the window. Step 6: Click the arrow located next to the desired Role Category to reveal each category’s role resources. Step 7: Clicking the arrow next to each Role Resource will reveal each resource’s sub-resource access options. Step 8: Toggle each Role |
...
Step 9: After selecting all desired Role Resources and Sub-Resources, click Save in the upper right-hand corner to enable and save changes in the user’s access.
...
More on Role Resources
Default Roles
Default Roles determine the level of Portal access for a user.
Expand | ||
---|---|---|
| ||
Referrer Sub-Resource you would like to enable for the User. Step 9: After selecting all desired Role Resources and Sub-Resources, click Save in the upper right-hand corner to enable and save changes in the user’s access. |
...
Role Resources
Role resources determine the specific abilities that a user will have when navigating the Portal. In many cases, the Default Roles available for Referrers and Merchant-level Users provide the necessary access capabilities that most Users need to perform daily actions such as creating Transactions or Withdrawals. For unique cases where Default Roles don’t satisfy the specific criteria required by the Parent Entity or Users, Custom Roles allow individual assignment of specific resources (see below) with sub-resources for a completely modular
Default Roles
Default Roles determine the level of Portal access for a user. Referrer-Level Access Roles are roles available to users of a Referrer-level entity, while Merchant-Level Access Roles are available to users of a Merchant-level entity.
Note: The Referrer has the unique ability to create and manage ALL Merchants under a Referrer as well as manage Sub-Referrers. The Referrer also has the ability to login to view the Merchant portal. The Merchant Access Roles only allow for the management of that respective Merchant and its sub-Merchants.
Default Referrer-Level Access Roles
Referrer Admin Full Access
...
- This level of access allows a user to view and edit/manage all
...
Merchants underneath a Referrer hierarchy in addition to managing sub-Referrer accounts underneath a client Division.
Referrer Admin View Only
...
- This level of access allows a user to view only all
...
Merchants underneath a Referrer hierarchy in addition to viewing any sub-Referrer accounts underneath a client Division.
Referrer Full Access
...
- This level of access allows a user to view and edit/manage all
...
Merchants underneath the Referrer account.
Referrer View Only
...
- This level of access allows a user to view only all
...
Merchants underneath the Referrer account.
Default Merchant-Level Access Roles
Merchant Admin Full Access
...
- This level of access allows a user to view and edit/manage the
...
Merchant account(s) they are associated with, in addition to managing sub-
...
Merchant accounts.
Merchant Admin View Only
...
- This level of access allows a user to view the
...
Merchant account they are associated with in addition to viewing sub-
...
Merchant accounts.
Merchant Full Access
...
- This level of access allows a user to view and edit/manage the
...
Merchant account(s) they are associated with.
Merchant View Only
...
- This level of access allows a user to view only the
...
Merchant account they are associated with.
Custom Roles
Custom Roles provide fiveRole categories which contain fifteen Role resources:
...
Create - Gives User access to create content from the allowed role resources.
Full View - Gives User access to view content from the allowed role resources.
Summary View - Gives User access to view monetary totals from the allowed role resources.
Update - Gives User access to update content from the allowed role resources
Delete - Gives User access to delete content from the allowed role resources.
Custom Role Resources
The Custom Role Resources allow the user’s access to be refined by specific resources or actions on the platform. See the available Custom Role Resources below:
Bank Accounts
The Bank Accounts role resource allows the user to add bank accounts for payouts or debits to an entity, such as a Referrer or Merchant.
...
The Recurring Payments role resource allows the user to set up recurring payments/subscriptions for a merchantMerchant.
This role resource is available in all role categories (Create, Full View, Summary View, Update, & Delete).
...
Expand | ||
---|---|---|
| ||
entities
Merchants
members
contacts
terminals
funds
fundOriginsAccess to view the source of where funds were processed for an entity.
entriesAccess to view the movement of funds from an entity.
pendingEntriesAccess to view an entry that will be created in the future (such as a refund that has been submitted reducing the available balance but has not been captured).
entryOriginsAccess to view the origin of an entry (such as a transaction and where it was funded).
|
...
The Groups role resource allows the user to group merchants Merchants together to set up specific rules for risk management and fees, as well as enable specific parameters.
...
Expand | ||
---|---|---|
| ||
txns
txnResults
batches
entityReturns
items
txnDatas
|
...
The Risk Management role resource allows the user to manage merchantMerchant/transaction risk factors that are open, reviewed, approved, or blocked.
...
Expand | ||
---|---|---|
| ||
holds
notes
decisions
decisionRules
|
...
Expand | ||
---|---|---|
| ||
logins
apikeys
iplists
messages
messageThreads
teams
teamLogins
aggregations
mappings
|
...
Expand | ||
---|---|---|
| ||
chargebacks
chargebackMessages
chargebackStatuses
chargebackMessageResults
chargebackDocuments
|
...
Expand | ||
---|---|---|
| ||
quickCharge
cc
eCheck
|
...