After your onboarding application is approved, you can create accounts for team members in the Merchant Portal and use the role mechanism to precisely assign page access and operation permissions. This approach meets team collaboration needs while ensuring the security of sensitive information and critical operations.

Before adding users, it is recommended to create the required roles first to assign appropriate permissions to different positions.

Permission Configuration Description:
| Permission Module | Included Features |
|---|---|
| Home | Home data overview |
| Balance Account | Comprehensive account balance, payment account balance, global accounts |
| Payment | Transaction management, payment settlement |
| Card Issuing | Card issuing related features |
| Payout | Payout related features |
| Settings | Business, personal profile, payment settings, team and security, notifications, Webhooks, transfer security |
Tip: Permissions are set at the button level. If a button permission is not selected, the user will not be able to click that button to perform the operation. After adding permissions, users will have page and button display as well as operation permissions.
After creating roles, you can add accounts for team members.
| Field | Description | Required |
|---|---|---|
| Name | User's real name | ✅ |
| Login Email | Email address for logging into the Merchant Portal | ✅ |
| Contact Email | Email for receiving system notifications (can be different from login email) | — |
| Receive Chargeback Email Notifications | When checked, this user will receive chargeback-related email notifications | — |
| Password | Set the user's login password | ✅ |
| Confirm Password | Confirm password | ✅ |
| Role | Select a created role for the user | ✅ |
| Status | Enable/Disable this user account | ✅ |
Based on different business needs, here are some common role configuration recommendations:
| Role Name | Recommended Permission Configuration | Applicable Personnel |
|---|---|---|
| Admin | All permissions | Business owner, supervisor |
| Finance | Balance account, payment settlement, payout | Finance personnel |
| Operations | Home, payment (transaction management) | Operations personnel |
| Customer Service | Home, payment (transaction management - view only) | Customer service personnel |
| Technical | Settings (Webhooks, payment settings) | Technical developers |
Note: After disabling a user, that user will not be able to log in to the Merchant Portal.
If a user forgets their password, the administrator can:
Q: Can a user have multiple roles?
A: Currently, each user can only be assigned one role. If you need combined permissions, it is recommended to create a new role and configure all required permissions.
Q: What happens to users using a role after it is deleted?
A: Before deleting a role, ensure no users are currently using that role. It is recommended to adjust related users to other roles before deleting.
Q: Can the login email be modified?
A: The login email cannot be modified after creation. If you need to change the email, please create a new user and disable the old user.
Q: How many users can be created at most?
A: There is no limit on the number of users. You can freely create the user accounts needed based on your team size.