The following five default user roles are available for your payment gateway account. Except for Account Owner, these user roles can be customized by modifying the user's permissions.
Account Owner
An Account Owner is the top level user, has irrevocable access to all features of the Merchant Interface, and manages all other user accounts. Only an Account Owner may create another Account Owner.
Account Administrator
By default, an Account Administrator has all Merchant Interface permissions except for the ability to enable or disable payment gateway services or manage Account Owner user accounts.
Transaction Manager
By default, a Transaction Manager can perform all transaction processing functions in the Merchant Interface.
Account Analyst
By default, an Account Analyst may only view and download Merchant Interface statements and reports.
Account Contact
An Account Contact does not have access to the Merchant Interface and is created solely to receive account notification e-mails.
All user roles (except for Account Contact) have the following basic, non-editable rights in the payment gateway:
Basic interface access: User can log on to the Merchant Interface, view the home page, announcements, help files, and contact Customer Support.
Edit own user profile: User can edit their own contact information, password, secret question and answer, and subscribe to notification and administrative emails.
View account information: User can view payment gateway account information, services, payment methods, and reseller contact information.
View transaction information: User can view unsettled transactions, transaction details, Automated Recurring Billing (ARB) subscriptions, and file upload statuses for regular and ARB transactions.
View reports: User can view and download transaction summaries, transaction settlement reports, statistics reports and returned items reports.
Close account: User can close the payment gateway account by contacting Customer Support. To initiate the request, the user must be able to verify specific account information.
The following table further describes the account permissions associated with each user role.
IMPORTANT: An Account Owner or Account Administrator can customize these permissions on a per-user basis.
PERMISSIONS KEY |
|
Default permission; not editable |
|
Default permission; editable |
|
Permission not applicable to the user role |
ROLES AND PERMISSIONS |
|||||
|
Account Owner |
Account Administrator |
Transaction Manager |
Account Analyst |
Account Contact |
Transaction Processing Permissions |
|||||
Create charge transactions: Ability to charge a credit card. |
|||||
Create refund/void transactions: Ability to refund a credit card. |
|||||
Manage existing transactions: Ability to void transactions, submit PRIOR_AUTH_CAPTURE. |
|||||
Settings Permissions |
|||||
Edit transaction format settings: Ability to edit the settings for Transaction Cut-Off Time, and Time Zone. |
|||||
Update transaction security settings: Ability to create the API Login ID and update the Transaction Key and MD5 Hash. Also ability to run the Merchant Interface in Test Mode. |
|||||
Manage mobile devices: Ability to approve, update or delete mobile devices used for transaction processing |
|||||
Account Level Permissions |
|||||
Update business information: Ability to edit credit card and bank account billing information and business information. |
|||||
Manage account services: Ability to enable or disable products and services. |
|||||
View account finances: Ability to view account Statements, Fee Definitions, and Risk Profile. |
|||||
User Management Permission |
|||||
Edit account users: Ability to add, edit, and delete user accounts, user permissions, and notification emails; reset passwords and secret questions and answers, and unlock users. |
Note: If you are a Card Present merchant, only Account Owners, Account Administrators, and Transaction Managers will be allowed to log on to Virtual Point of Sale (VPoS). To log on successfully, these users must have the appropriate permissions to create charge and refund transactions.