Give access
without giving everything.
Sub-user accounts with role-based access for merchants, partners and operators. Give each user only what they need to see and do.
Access control as a feature, not an afterthought
Real teams have specialist roles - finance, support, risk, sales. Each role needs a different view and different permissions. Limited Sub-Accounts give every user exactly what they need.
Role-based access
Access that stops where you want it to. A sub-account gets its own credentials and its own permissions, so somebody can do the one job they were given without inheriting the whole account.
Granular permissions
Restrict a user's access to specific merchants or merchant groups. Useful for support agents, account managers and partner staff.
Audit-logged
Grant access for a defined period - useful for contractors, auditors or temporary support coverage. Access auto-expires.
Approval workflows
Sensitive actions - refunds above a threshold, fee changes, merchant suspensions - can require approval from a second user with the right role.
Full audit log
Every action logged with user, timestamp, before/after state. Audit log searchable, filterable and exportable for compliance reviews.
How sub-accounts work
- Define roles
Create roles with the permissions each function needs. Apply scoping rules - by merchant, by region, by action type.
- Invite users
Invite users via email; they set their own password and 2FA. Apply the right role at invite time.
- Audit
Review the audit log per user, per merchant or per action type. Export for compliance reviews.
Frequently asked questions
How granular are the permissions?
Permissions are set per feature rather than as a single level, so read, write and edit can be granted separately and a sub-user can be given visibility of something without the ability to change it.
Can I scope access to specific merchants?
Yes. A user's role can be scoped to a single merchant, a group of merchants or all merchants. Useful for partner staff or account managers.
Is 2FA enforced?
Login can be protected with a one-time passcode, and high risk actions such as payouts and transfers can be made to require a passcode confirmation of their own even for an already authenticated user.
Can I delegate role management to a merchant?
Yes. Merchants can manage their own sub-users in the merchant control panel - within the role limits you define for that merchant.
How is access revocation handled?
Immediate. Revoking a role or deactivating a user takes effect on the next request. The audit log shows when and by whom the change was made.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.