Important: This article is about the Dext Payments Beta, an upcoming feature currently in development.
Control who can view, create, and process payments in Dext. This guide explains who gets access, how to grant or request it, and what each role can do.
How Payments access is assigned
When your organization completes KYC (Know Your Customer), the Admin who completes KYC becomes the Payment Owner. That user:
Gets immediate access to the Payments area
Can manage access and permissions for other users
Additional notes:
Payment Admins can be designated by the Payment Owner (or via permissions later).
Practice Admins have access to the Payments feature and can control which client accounts get Payments access.
Client Admins have Payments enabled by default, but cannot access protected areas (e.g., Wallets, Payment Runs) until the Payment Owner grants specific permissions.
For client accounts, the first Business Admin who completes KYC becomes the Payment Owner.
Grant access to other users
Currently, Payment Owners and Payment Admins can grant access.
Steps:
Go to Business Settings > Permissions > Add User.
Click Add User to open Give a user access to Payments.
Select an eligible user from the dropdown:
Practice users can see users from their practice and client businesses.
Business users can see users from their own business only.
Choose the user’s role: Payment Admin or Standard User.
Click Submit.
Once added, the user will appear on your organization’s Permissions list.
Request access
If a user sees Payments disabled or is unable to access certain areas (even if their overall account role is Admin), they can request access:
Go to any page in the Payments area.
Click Request Permissions.
Submit the form.
What happens next:
An email requesting access is sent to the Payment Owner and Payment Admins.
The request appears in Permissions > Pending Permission Requests.
Approve or reject access requests
Currently, Payment Owners and Payment Admins can review requests.
Steps:
Go to Business Settings > Permissions > Pending Permission Requests.
Accept or reject each request.
If accepted:
The user’s Payments access becomes active.
The user must add an authentication device (prompted on first visit to any Payments page).
An authentication device is required to view protected pages (wallet details), create payment runs, and perform actions like submitting payments for processing.
Once authentication is complete, the user can access Payments according to their assigned permissions.
Roles and permissions: what users can do
Payment Admins
Can perform all of the following:
View invoices to pay
View payment runs
Be assigned as approvers for payment runs
Manage supplier bank details
Create payment runs
Process payments
Manage permissions (grant, edit, or remove access)
Standard Users
By default, Standard Users can:
View invoices to pay
View payment runs
Be assigned as approvers for payment runs
They can also be optionally granted permission to:
Manage supplier bank details
Create payment runs
Process payments
User list & status indicators
In Payments > Permissions, you’ll see all users with Payments access, plus:
A mobile icon (active/inactive) showing whether the user has added an authentication device
A permissions grid showing which capabilities (e.g., Create Payment Run, Process Payments, and Manage Payees) are enabled for each user
Edit or remove a user’s permissions
Go to Payments > Permissions.
In the user list, click Manage next to the relevant user.
Choose an action:
Edit permissions
Click Edit permissions.
In Edit payments access grant, change the user’s role (e.g., Admin ↔ Standard) or adjust specific capabilities.
Click Save changes.
Remove permissions
Click Remove permissions.
The user is immediately removed from the Permissions table and loses access to Payments.
Any in‑progress tasks are canceled.
The action is recorded in your audit log.
Best practice
Review user access regularly to ensure only the right people can manage payments.
Remove access immediately when a team member changes roles or leaves the organisation.
Always check the audit trail to confirm who has modified permissions and when.