Core capabilities and role-based access model
Overview
Dashboard is a unified interface intended for use by employees of the merchant. It supports a full range of required features, and it implements a role-based access model in order to distribute rights to access different features among various specialists (with consideration of organization structure and other factors).
This section describes core capabilities, supported access roles and their specific characteristics as well as granting access rights to different roles.
Capabilities
- Monitoring and analysing payment processing—users are able to view, filter, search, and visualize data on both completed payments and payments in-progress.
- Executing financial operations—users are able to perform various types of purchases, issue payouts and refunds (both full and partial) as well as manage regular COF purchases (subscriptions).
- Remittances—users are able to make single and bulk B2B payments to corporate accounts (learn more).
- Payment Page design customisation—users are able to view, create, modify, and delete different design styles of the payment form (more).
- Financial accounting and reporting—users are able to prepare and view various reports with access to the balance sheets.
- Risk and chargeback management—users are able to monitor detected fraud cases, which includes managing whitelists and blacklists, as well as to monitor chargebacks and accept specific chargebacks without going through an arbitration process.
- Interface access administration—users (with appropriate permissions) are able to manage user accounts and distribution of access roles as well as to monitor user actions and to view settings of available projects as well as to configure some of these settings.
To access one or more of these capability categories, the following roles are used.
Access roles
| The following roles with the corresponding capabilities are used in Dashboard when access rights are distributed: | ||||||
| Designer | Support | Operations | Finance | Risks | Merchant admin | |
|
– | ± | + | + | + | + |
|
– | ± | + | – | – | + |
|
– | – | – | + | – | + |
|
– | – | – | – | + | + |
|
– | – | – | – | – | + |
|
+ | – | – | – | – | + |
| These roles can be applicable for employees with the following job titles: | ||||||
|
|
|
|
|
|
|
This selection of roles is permanent, which means that the merchant is not able to create other roles. However, for certain user accounts the permission set determined by the role can be modified; in addition, a single user account can take on several roles simultaneously. This widens the range of permissions available to the user by combining permissions initially only available in separate sets of the default selection. For instance, if a user account with the Operations role access requires rights to view the balance sheet, then you can grant this user account the access rights of the Finance role which permits viewing balance information in Finance section.
User accounts with the assigned Merchant Admin role are granted a full set of permissions to access all merchant's projects, and such user accounts can only be created by ecommpay technical support specialists. User accounts with permissions granted by other roles (including accessing projects) can be created and configured by the merchant's employees with the assigned Merchant Admin role. It is important to keep in mind, however, that permissions granted to a user account apply to all projects which this user account is allowed to access. There is no selective applicability of permissions depending on the project that a user account has access to.
Keep in mind that the implemented role-based access model implies the following:
- User accounts with the assigned Merchant Admin role can be created only by ecommpay technical support, while user accounts with permissions granted by other roles can also be created by the merchant's employees with the assigned Merchant Admin role.
- New custom roles cannot be created, but a single user account can take on several roles simultaneously.
- There is no selective applicability of permissions depending on the project a certain user account has access to. However, the permission set determined by the role can be modified.
Access rights
Access rights to work with different sections of Dashboard are distributed among the roles as shown in the following table. In addition to these rights, you can request a number of permissions with the extended scope from the ecommpay technical support—on condition that such permissions are used in the platform and are available for the use by the merchant. For example, to ensure that your employees have access to editing whitelists, you need to request a corresponding permission.
| Designer | Support | Operations | Finance | Risks | Merchant admin | |
|---|---|---|---|---|---|---|
| My team | ||||||
| Viewing the list of user accounts | – | – | – | – | – | + |
| Managing user accounts | – | – | – | – | – | + |
| Finance | ||||||
| Viewing the balance information | – | – | – | + | – | + |
| Reports | ||||||
| Viewing and managing reports | – | + | + | + | + | + |
| Payments | ||||||
| Viewing the payments list | – | + | + | + | + | + |
| Configuring the list's display mode | – | + | + | + | + | + |
| Viewing the payment's detailed information | – | + | + | + | + | + |
| Issuing refunds | – | – | + | – | – | + |
| Performing capture operations | – | – | + | – | – | + |
| Performing cancel operations | – | – | + | – | – | + |
| B2B remittances | ||||||
| Viewing the lists of remittances and remittance recipient accounts | – | + | + | + | – | + |
| Creating and editing remittance recipient accounts | – | – | + | – | – | + |
| Sending remittance recipient accounts for approval and deleting accounts | – | – | + | – | – | + |
| Creating remittance orders | – | – | + | – | – | + |
| Payment links | ||||||
| Viewing the list of payment link purchases | – | – | + | – | – | + |
| Creating payment links | – | – | + | – | – | + |
| Deactivating payment links | – | – | + | – | – | + |
| Manual Payments | ||||||
| Viewing the payouts and mass payouts lists | – | – | + | – | – | + |
| Configuring the display mode of the lists | – | – | + | – | – | + |
| Viewing the payment's detailed information | – | – | + | – | – | + |
| Issuing payouts | – | – | + | – | – | + |
| Issuing refunds | – | – | + | – | – | + |
| Performing capture operations | – | – | + | – | – | + |
| Performing cancel operations | – | – | + | – | – | + |
| Taking MO/TO payments | – | – | + | – | – | + |
| Subscriptions | ||||||
| Viewing the list of subscriptions | – | + | + | – | – | + |
| Viewing the subscription's detailed information | – | + | + | – | – | + |
| Managing subscriptions | – | – | + | – | – | + |
| Risks | ||||||
| Viewing the list of fraudulent operations | – | – | – | – | + | + |
| Viewing whitelists and blacklists | – | – | – | + | + | |
| Editing blacklists | – | – | – | – | + | + |
| Chargebacks | ||||||
| Viewing the list of chargebacks | – | – | – | – | + | + |
| Viewing the chargeback's detailed information | – | – | – | – | + | + |
| Accepting a chargeback | – | – | – | – | + | + |
| My profile | ||||||
| Editing user account's general information | + | + | + | + | + | + |
| Managing Data API tokens | – | + | + | + | + | + |
| Managing technical support bot | – | + | + | – | – | + |
| Analytics | ||||||
| Viewing Analytics section | – | – | + | + | + | + |
| Managing analytic boards | – | – | + | + | + | + |
| Projects | ||||||
| Viewing projects | + | + | + | + | + | + |
| Editing project settings | – | – | – | – | – | + |
| Managing Payment Page Designer | + | – | – | – | – | + |
| Help | ||||||
| Viewing information | + | + | + | + | + | + |