TranexioAI-native trade platform
简EN繁
Sign inBook a demo
Platform

Integration hub

The integration hub is Tranexio’s only channel to external systems. The Single Window, the electronic tax bureau, banks and treasury, futures brokers’ trading systems, finance, ERP and OA all connect through standard connectors; business modules call one gateway and never deal with external protocols, so changing vendor or interface needs no business code changes.

Key points

  • One connector per system

    Each external system has its own adapter registered in the connector pool and is routed through a single call gateway; changing vendor means replacing the connector while business workflows stay the same.

  • Event-driven, one-way dependency

    Business modules publish events and the integration hub subscribes and forwards them, so an external system failure never drags down saving or approving business documents.

  • Idempotent and replayable

    Messages are de-duplicated by business key, receipt status only ever moves forward, out-of-order receipts are queued and replayed automatically, and failed messages can be compensated from the console.

  • Secure inbound calls

    External callbacks are verified with HMAC signatures, time windows and replay protection; connector credentials are stored encrypted and never shown in plain text.

  • Observable and governable

    Integration audit logs, health checks, retry and fallback policies and the reconciliation centre sit in one console, where administrators can see where every message went and what happened to it.

The problem

Point-to-point interfaces are a familiar burden for trading companies’ IT. Each business module calls banks, customs and finance systems on its own, a protocol change means editing code in several places, and when something breaks nobody can tell where a message went. Tranexio requires every external connection to go through the integration hub, with a one-way dependency: business module → integration hub → external system.

What the platform does

Component Role
Connector pool One adapter per external system, declaring its capabilities, health checks and fallback when unavailable
Single call gateway Business modules call only the gateway, which selects the connector by tenant, legal entity and routing rules
Event routing Business events are distributed by subscription rules, with retries, fallback and compensation
Field mapping Configurable mapping rules between external and platform fields
Inbound interface HMAC signatures, time windows and replay protection for external callbacks
Monitoring and audit Integration overview, message audit log, reconciliation centre and alerts

External systems available for connection

Standard connectors are available for all the categories below; actual activation depends on project integration testing.

  • Customs: the China International Trade Single Window (国际贸易单一窗口) and Golden Customs Phase II (via a front-end server on the company’s side).
  • Tax: invoicing and export tax refund filing through the electronic tax bureau.
  • Banking and treasury: bank–enterprise connectivity platforms, group treasury and direct bank links.
  • Futures: futures brokers’ trading systems and market data feeds.
  • Finance and ERP: mainstream general ledgers and ERPs such as Yonyou, Kingdee, SAP and Oracle.
  • OA and collaboration: to-dos and password-free sign-in for OA systems such as Weaver and Seeyon; notifications via WeCom, DingTalk, Feishu, email and SMS.
  • Risk and credit: company registry data, sanctions list sources and EDI with export credit insurers.
  • Logistics: shipping schedule and container tracking data sources.
  • Identity: OIDC and CAS enterprise identity.

Key controls

  • Credentials are stored encrypted, isolated by tenant, with changes logged.
  • Messages are append-only and status only moves forward, traceable to the business document that triggered them.
  • Connectors support a simulation mode, so business acceptance can be completed before external channels are opened.

Frequently asked questions

Can Tranexio connect to our existing finance system and ERP?

Connectivity is available. The integration hub provides connectors for mainstream finance systems and ERPs; journal entry posting supports dual ledgers, routing to manual handling when mappings are missing, and reversals. The actual connection depends on your system version and the interfaces it exposes, and is tested and accepted in the project.

Can it connect directly to China’s Single Window?

Connectivity is available. The Single Window and Golden Customs Phase II are accessed through a front-end server or client on the company’s side, and the connector handles message receipts, status updates and back-filling of customs numbers. Declaration certificates can stay on the company’s internal network, and the filing channel is opened in the customer’s environment during the project.

Will an external system outage stop us entering orders?

No. Business modules and external systems are decoupled by events. When an external service is unavailable, messages go into a retry queue and degrade according to policy, while business documents are saved and approved as normal. Once the service recovers, messages are resent under idempotency rules, with no duplicate postings or declarations.

Do we need system changes to switch bank or OA vendor?

No business functions need to change. You add or replace the relevant connector on the integration hub and configure field mappings and routing, while contract, order and payment workflows stay the same.

Related

See how Tranexio fits your trade operations

Tell us how you trade and what systems you run today — a product specialist will walk you through your own scenarios.

Book a demo →

Updated 2026-10-06