Glossary
Role-based access control
Role-based access control, RBAC, gives each user a role, and each role a set of permissions: view payments, refund, create a payout, approve a payout, change routing, onboard a merchant, manage users. In a payment platform the roles are also scoped: to a network, to a merchant, to a set of merchants, so that a partner's administrator sees only its brand and a merchant's accountant only its reports. Separation of duties, creating a payout and approving it as two roles, is what keeps one compromised account from moving money alone.
Typical roles
Platform administrator; network administrator for a brand; operations and support, who see traces and can resend webhooks but not move money; finance, who settle and approve payouts; compliance, who onboard and review merchants; merchant owner, merchant developer with keys and webhooks, merchant accountant with reports. Each role should be the smallest set of permissions its work needs.
What goes with it
Two-factor authentication for every user who can see card data or move money; session limits; approval flows for payouts and routing changes above thresholds; an audit log of who did what; and a review of roles when people change jobs or leave.
On the platform
Tranzify’s back office and merchant cabinet assign users roles scoped to networks and merchants, require two-factor authentication and record every action in the audit log; the licensed client administers its own users and those of its partners’ networks.
Updated: 2026-11-08