RTX5 KYC AML
RTX5 specifies workflow hooks and screening integration. It does not claim to be a particular KYC bureau.
Specified for RTX5 broker deployments. Not evidence that a named production build has passed acceptance tests.
Main capabilities
Hooks, not a bureau
Named vendors are listed only after access rights exist.
Enforcement
A blocked client cannot deposit or trade through another path.
How it works
- 01
Authenticate
A principal acts inside a tenant and account scope.
- 02
Validate
Pre-trade risk and instrument rules run first.
- 03
Record
A durable journal feeds positions, ledger and audit.
- 04
Operate
Managers and APIs use the same permission-enforced path.
Technical details
Server authority
The client is a user interface. Entitlement, order and risk decisions remain on the server.
No inferred venues
Listing a category does not establish venue, data or regulatory access.
Security and controls
Authorization
Tenant, object and function checks are enforced server-side.
Frequently asked questions
Is this live today?
Specified for RTX5 broker deployments. Not evidence that a named production build has passed acceptance tests.
Can I get a quote?
Yes. Use Request a Quote on the contacts page.