The problem
A trade system holds contract prices, customer credit, hedge positions and customs credentials, so overly broad access is a business risk in itself. Group customers also require private deployment, domestic IT stacks and traceable audit. Tranexio treats all of this as core capability rather than project-by-project patches.
What the platform does: permissions and isolation
| Dimension | What it controls |
|---|---|
| Menus | Which functions a user can open |
| Buttons | Which actions a user can take, such as create, approve, void or export |
| Data | Which organisations’, legal entities’, departments’ or own documents a user can see |
| Fields | Which fields a user can see or edit, such as cost, margin and price |
| APIs | Which open APIs a user can call |
- Role segregation (a conflict-of-duties matrix), automatic revocation of temporary grants on expiry and one-click handover when staff leave.
- Multi-tenant plus multi-entity isolation: business documents carry their operating entity by design, so consolidation needs no mapping tables.
Security controls
- Image or behavioural CAPTCHA, SMS sign-in and lockout after failed attempts; connection to enterprise identity (OIDC / CAS) is available.
- SM2 password transmission and SM4 field encryption; API message encryption; XSS protection; rate limiting and API keys.
- External system credentials are stored encrypted and called only through the integration hub.
- Operation, API and error logs are kept in full and can be searched and exported.
Deployment options
| Option | Details |
|---|---|
| Multi-tenant SaaS | Field-level isolation in a shared database, with an optional dedicated data source per tenant |
| Single-tenant private | Offline installation and upgrade packages, licence certificate activation, can run on an internal network |
| Hybrid cloud | Core data deployed privately, with collaboration and external portals in the cloud as needed |
- Database: supports MySQL and is adapted to Chinese domestic databases such as Dameng.
- Xinchuang: private deployments can be supplied as ARM64 (aarch64) offline packages with domestic JDKs, adapted per project to domestic CPUs, operating systems and middleware.