Evidence & Claim Basis | Turing Ultra

Product-rights boundary

Do not infer ownership, licence scope, exclusivity, territorial rights, current product availability or delivery authority from this website. Those matters must be confirmed for the relevant transaction in executed rights and customer documents.

How to read the register

“Supplied product material” means a statement appears in historical product material supplied to Turing Ultra. “Historical attributed statement” means the named statement is retained in supplied historical material. Neither status proves current target availability, a current customer relationship or a future result.

Every implementation still requires current scope, rights, architecture, integration, security, regulatory and acceptance validation. Website wording cannot replace that evidence.

Public claim register

Supplied product materialportfolio-integrations

80+ ready-made integrations

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Portfolio-level statement. Exact adapters, versions, certification state and availability vary by target environment.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialsuite-configuration-days

Products and services can be configured in days

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Configuration-time statement, not an implementation or launch timetable.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialsuite-operating-view

One operating view across the suite

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Suite design statement. The implemented view depends on selected modules, roles and integrations.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialcore-unlimited-technical-accounts

Unlimited technical accounts

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Product-design statement. Practical limits depend on the contracted release, infrastructure and operating model.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialcore-multi-model

Multi-entity, chart-of-account and currency support

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Capability statement subject to entity model, accounting design and target configuration.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialcore-low-code

Low-code product and workflow configuration

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Configuration capability statement. Change authority, testing and release controls remain implementation-specific.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialpayments-multi-context

Multi-currency, channel, product and instrument support

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Capability statement. Supported combinations require target integration and scheme validation.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialpayments-central-hub

One central payment operations hub

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Target operating-model statement, not evidence that every provider or rail is currently connected.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialonboarding-training-set

3 million faces in the stated model training set

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Historical model statement. Model identity, version, lawful data basis and current deployment are not established by this website.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialonboarding-lfw

99.38% stated accuracy on the LFW test

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Historical benchmark statement. It is not a target-population error rate or proof of a current production model.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialonboarding-timeframe

Minutes for stated out-of-box onboarding

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Scenario statement. Actual completion time depends on journey, applicant, providers, exceptions and review requirements.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialcompliance-real-time

Real-time transaction rules and intervention paths

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Processing-mode statement. Latency, coverage and intervention authority require target-bound validation.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialcompliance-configurable

Configurable matching, monitoring and scoring logic

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Capability statement. It does not establish regulatory compliance or the fitness of a particular rule set.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialcompliance-refresh

Minutes for stated entity-profile refresh after a change

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Historical refresh-time statement subject to provider, data and target configuration.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialomnichannel-core-compatibility

Any-core deployment compatibility

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Architecture direction, not universal compatibility. Each core, interface and target version requires validation.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialomnichannel-brand-change

Minutes for stated multi-brand presentation change

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Configuration-time statement, excluding approval, content, testing and release processes.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialomnichannel-cross-device

One experience across devices and channels

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Experience-design statement. Exact channel parity depends on selected journeys and target implementation.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialconnect-open-api

Open API integration foundation

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Architecture statement. Available APIs, policies, service levels and security controls are release- and scope-specific.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Supplied product materialconnect-architecture-extension

Extend existing architecture without first replacing it

Source basis: Supplied historical product overview retained by Turing Ultra.
Scope: Implementation approach subject to the incumbent estate, interfaces and transition constraints.
Evidence required to rely: Confirm the target release, integration inventory, configuration and acceptance criteria in signed scope and target-bound validation.

Historical attributed statementcustomer-vivacom

Attributed statement from Atanas Dobrev

Source basis: Attributed statement retained in supplied historical product materials.
Scope: Historical statement about earlier platform delivery. It is not evidence of a current customer relationship or a future result.
Evidence required to rely: Retain the underlying source and obtain any consent required for the intended current use; establish current outcomes separately.

Historical attributed statementcustomer-transact-pro

Attributed statement from Maxim Yaroshewsky

Source basis: Attributed statement retained in supplied historical product materials.
Scope: Historical statement about earlier platform delivery. It is not evidence of a current customer relationship or a future result.
Evidence required to rely: Retain the underlying source and obtain any consent required for the intended current use; establish current outcomes separately.

Historical attributed statementcustomer-mr2

Attributed statement from Heiki Murula

Source basis: Attributed statement retained in supplied historical product materials.
Scope: Historical statement about earlier platform delivery. It is not evidence of a current customer relationship or a future result.
Evidence required to rely: Retain the underlying source and obtain any consent required for the intended current use; establish current outcomes separately.

Historical attributed statementcustomer-amaiz

Attributed statement from Steve Taklasing

Source basis: Attributed statement retained in supplied historical product materials.
Scope: Historical statement about earlier platform delivery. It is not evidence of a current customer relationship or a future result.
Evidence required to rely: Retain the underlying source and obtain any consent required for the intended current use; establish current outcomes separately.

Development directiongoverned-internal-first

Internal-first governed-intelligence operating approach

Source basis: Turing Dynamics design direction described for bounded internal-first workflows.
Scope: Illustrative target posture. It is not evidence of current production availability or operating effectiveness.
Evidence required to rely: Establish a named workflow, approved sources, permissions, human authority, target runtime, test results and operating evidence.

Development directiongoverned-source-linked

Source-linked knowledge and workflow design

Source basis: Turing Dynamics design direction described for bounded internal-first workflows.
Scope: Illustrative target posture. It is not evidence of current production availability or operating effectiveness.
Evidence required to rely: Establish a named workflow, approved sources, permissions, human authority, target runtime, test results and operating evidence.

Development directiongoverned-human-reviewed

Human-reviewed decision control

Source basis: Turing Dynamics design direction described for bounded internal-first workflows.
Scope: Illustrative target posture. It is not evidence of current production availability or operating effectiveness.
Evidence required to rely: Establish a named workflow, approved sources, permissions, human authority, target runtime, test results and operating evidence.

Written confirmation requiredproduct-rights

Product availability and Turing Ultra contracting rights

Source basis: This public website is not evidence of ownership, licence scope, exclusivity, territorial rights or delivery authority.
Scope: Rights, availability, contracting entity and implementation authority are transaction- and territory-specific.
Evidence required to rely: Confirm the applicable rights chain, territory, release, contracting entity and customer terms in executed documents before reliance or purchase.

What this website does not establish

This register does not establish production readiness, regulatory approval, compliance completeness, security certification, universal integration compatibility, implementation timing, customer traction or product rights. Those matters require current, target-bound evidence.

Public statements should show their evidence boundary.