XTRM is a global multi-tenant payment system. This means we have one organization account (Prime Entity) for a company worldwide with separate entities for regional subsidiaries or any legal entity owned by the organization. The regional user administrators can create and separately manage their own entity profile, users, wallets, and role-based access as needed for their local requirements.
To Summarize:
- Only one org acct (Prime Entity) is needed for your company globally.
- You can set up as many regional entities within the organization as you like.
- You can add as many single-entity and multi-entity regional users as you like.
- Wallet and service access are strictly controlled via security roles and settings.
- Existing master admin, controller, or manager users can add new regional users. More Info
Master Admin Consideration:
One designated person, typically with signatory authority, is designated the "Master Admin" and should register the Org Acct. (Prime Entity) with the company headquarters details, i.e., register ACME Inc HQ. and associated address (Not ACME Region 1 or ACME Region 2). If you are a company regional office, you must register your Org Acct (Prime Entity) first. This can be done at www.xtrm.com - choose company registration. If an Org account (Prime entity) already exists, you will be notified and asked to contact the existing manager-type users to add you as a user for your region.
Since XTRM is a financial service account regulated in the same way as a bank, when considering who will be the master admin for your company account, we recommend you choose someone with financial signatory approval for your company. This is often someone in the exec team, treasury, or finance group. This person is not solely responsible for managing the account but can delegate responsibility to regional entity managers (controller, manager, and standard users).
Entities, user roles, and access levels handle the separation of access to wallets and funds. Regional entities can have specific access to regional entity wallets and functions. It is identical to separate accounts from a compliance and security perspective but provides global account compliance and consolidated reconciliation reporting. It also simplifies onboarding times and ensures more accurate and faster payments whilst ensuring only the right people access the right wallets, funds, and services.
Some key terms:
Term | Description | Identifier | # |
| Organization (Prime Entity) | This is your prime entity, typically your HQ. It has a unique Organization ID (OID) - the format is SPNXXXXXXXX. There is one ORG account (Prime Entity) globally with multiple regional entities below the org account. | SPN Prefix + 7 Numbers SPN1234567 | 1 |
| Entities | These are the local country or regional entities. An example of a regional entity is ACME France or ACME EMEA. (An example of an ORG would be ACME HQ). Entities can also be legally separate companies or member firms rolling up into one organization. | Name Acme France | Any |
| Wallets | Within an entity account, you can have as many currency wallets as you like. Wallets are assigned to entities and can only be seen by users with access to the wallet entity. | Unique Number 12345678910 | Any |
| Users | Any person that has access to your company account. Users can have different roles, such as master admin, controller, manager, or standard users. Users have unique account IDs (AID) starting with SPAXXXXXXX. | PAT Prefix + 7 Numbers PAT1234567 | Any |
| Master Admin | This is the key global contact. There is one master admin per global Org account. This person should typically be in finance or treasury with company signatory authority. This person has full access to all services. | SPA Prefix + 7 Numbers SPA1234567 | 1 |
| Controller User (NEW) | These are multi-regional or entity administrators responsible for one or more regions or entities. There can be any number of controllers. These users can manage other "Controller", "Manager," or "Standard" users for only the regions they control, plus manage wallets and service access for all the users within their regions. | SPA Prefix + 7 Numbers SPA1234567 | Any |
| Manager User | These are regional administrators responsible for one region or entity. For example, they are responsible for one country or one entity. There can be any number of manager users. These also have full access to all wallets and services within their entity and can create and manage standard users within their entity. | SPA Prefix + 7 Numbers SPA1234567 | Any |
| Standard User | These are your regional program and wallet administrators. There can be any number of standard users. Very granular access can be set to these user types. | SPA Prefix + 7 Numbers SPA1234567 | Any |
✓ = Yes X = No O=Optional (Access Level Setting)
| 4 User Levels: | Master Admin | Controller | Manager | Standard | Suspended |
| Typical Role | Senior Finance/Treasury | Multi Region, Multi-Entity Finance/Treasury Head | Single Regional Finance, Department Head | Department Manager (Most common) | N/A |
| Number Allowable | 1 | Any number | Any number | Any number | Any Number |
| Entity Control | Multi | Multi | Single | Single | X |
| Log in to Company Account | ✓ | ✓ | ✓ | ✓ | X |
| Delete Users | ✓ | ✓ | X | X | X |
| Manage Multi Regions | ✓ | ✓ | X | X | X |
| Create Users | ✓ | ✓ | ✓ | X | X |
| Suspend Users | ✓ | ✓ | ✓ | X | X |
| Set User Access Levels | ✓ | ✓ | ✓. | X | X |
| Send Password Reset Emails | ✓ | ✓ | ✓ | X | X |
| Fund Wallets | ✓ | ✓ | ✓ | O | X |
| Send Funds | ✓ | ✓ | ✓ | O | X |
| Transfer Funds (withdraw) | ✓ | ✓ | ✓ | O | X |
| Currency Exchange | ✓ | ✓ | ✓ | O | X |
| Create Programs | ✓ | ✓ | ✓ | O | X |
| Link Banks | ✓ | ✓ | ✓ | O | X |
| Create Edit Claims | ✓ | ✓ | ✓ | O | X |
| Create Edit Beneficiaries | ✓ | ✓ | ✓ | O | X |
| Create Edit Connected | ✓ | ✓ | ✓ | O | X |
| Create Edit Wallets | ✓ | ✓ | ✓ | O | X |
| View Claims | ✓ | ✓ | ✓ | O | X |
| View Reports | ✓ | ✓ | ✓ | O | X |
| View Beneficiaries | ✓ | ✓ | ✓ | O | X |
| View Connected | ✓ | ✓ | ✓ | O | X |
| View Wallets | ✓ | ✓ | ✓ | O | X |
There are 4 template levels of access.
| Level | Access |
| Full | Full access to all features |
Custom | Custom access to features |
| View | View-only access to wallets and features |
| Limited | Limited access to basic features |
A master, controller, or manager user can edit any users that are in the entities they manage and are of a lower level. Click on the Set Custom Access button to be directed to the set custom access level screen:
