$100B+
Processed
annually
annually
Payments · Features
Virtual Terminal User Management
Control access across merchants, teams, and payment workflows. Paygasus’ user and role management protects transactions, reporting, and administrative settings with structured permissions.
Roles · permissions · hierarchy
Who can do what, by design.
Roles · permissions · merchant hierarchy
The access layer — proven across merchant hierarchies
6 of
Fortune 100
organizations
organizations
500+
Municipalities
governed
governed
RBAC
Role-based
by design
by design
Audit
Full activity
trail
trail
30
Countries
operating
operating
What it is
Activate user and role controls
User and role management defines access to payment functions and data based on role and organizational structure, standardizing permissions across multi-merchant environments for internal oversight and compliance.
Role-based access control
Role-based access control (RBAC) reduces risk by limiting sensitive actions to approved roles. Clear role definitions also simplify onboarding by establishing consistent access for common responsibilities.
Operational value
Strengthen security and streamline administration with granular access controls.
- Role-based access control (RBAC) for payment operations.
- Granular permissions for transactions, reporting, settings, and users.
- Configurable access for PayFac and multi-merchant environments.
- Audit trails for user activity and permission changes.
Key features of our user management
Structure access around your organization.
Align permissions to teams, roles, and responsibilities, then maintain a clear record of every access change across the account.
Merchant Hierarchy & Access Controls
Multi-Level PermissionsOrganize users across parent-child merchant structures with permission inheritance and overrides to match operational requirements.
Role-Based Access Control
Granular RBACAssign access by role to unify administration and reduce risk. Create custom roles with permissions for transactions, reports, settings, and user management.
Audit & Compliance
Full Audit TrailLog user actions and permission updates to support accountability, internal reviews, and compliance workflows.
Inside the access layer
Access maps to the merchant hierarchy
Roles map to the merchant hierarchy, with permissions inherited by default and adjustable at any level for tighter control or specific overrides.
Merchant hierarchy
RBAC · inheritanceParent organization
Acme Holdings — all merchants
Full access to every merchant, setting, report, and user.
Sub-merchant · region
North Region
Transactions and reports for assigned merchants only.
Location
Store 14
Process and refund transactions at this location.
Location
Store 22
Process and refund transactions at this location.
Sub-merchant · region
South Region
Transactions and reports for assigned merchants only.
Permissions inherit down the tree; each level can be overridden. Names shown are illustrative.
The difference
RBAC vs. basic access
See why role-based access control is essential for secure payment management.
| Aspect | RBAC | Basic |
|---|---|---|
| Security | Granular, role-specific permissions. | All or nothing access. |
| Scalability | High — scales with team growth. | Low — manual management. |
| Compliance | Full audit trail and logging. | Limited tracking. |
| Hierarchy | Multi-level merchant hierarchy. | Flat structure only. |
| Customization | Custom roles and permissions. | Fixed access levels. |
| Efficiency | Automated role assignment. | Manual user-by-user setup. |
Ready to upgrade your access management?
Talk to a specialist →Why Paygasus
Scale secure access across merchants
Paygasus simplifies administration for large teams with consistent permissions, scalable hierarchies, and operator-friendly controls designed for accountability.
Business impact
Reduce onboarding time and protect sensitive operations with role-based controls and audit-ready tracking from day one.
- Intuitive interface for PayFac and multi-merchant setups.
- Granular permissions across features and workflows.
- Complete audit trail for compliance and security review.
- Permission inheritance and role templates to standardize access.
Getting started
Set up user roles
Follow these four steps to implement secure access control for your payment system.
01
Define Roles
Create custom roles based on your organization’s access requirements and team structure.
- Admin roles
- Manager roles
- Operator roles
02
Assign Permissions
Set granular permissions for each role across transactions, reports, and settings.
- Transaction access
- Report viewing
- Settings control
03
Set Hierarchy
Configure your merchant hierarchy with parent-child relationships and inherited access.
- Parent merchants
- Sub-merchants
- Inherited access
04
Audit
Monitor user activity with full audit logs and review access patterns for compliance.
- Activity logs
- Access reviews
- Compliance reports
Questions
Frequently Asked Questions
User and role management controls access to payment functions and data by assigning permissions to users based on job responsibilities and organizational structure.
Merchant access controls define which merchants, locations, or accounts a user can view and manage, plus what actions are allowed within each scope.
Role-based access control (RBAC) is a security model that assigns permissions to roles, then assigns roles to users to standardize access and reduce risk.
A merchant hierarchy is a parent-child structure used to organize multiple merchants, sub-merchants, or locations so access and reporting can be managed consistently across entities.
RBAC for payments applies role-based permissions to payment workflows such as transaction processing, refunds, reporting, configuration, and user administration to protect sensitive actions and data.
Open the access layer
Secure Your Payment Access Today
Connect with us to standardize roles, speed onboarding, and strengthen oversight across merchant environments.