Data ownership

The request contract separates transaction facts supplied by the caller from historical and risk information owned by Vantrace.

Caller-supplied facts

Your system is authoritative for:

• Transaction amount, currency, type, channel, and event time.
• True source and beneficiary account identifiers.
• The bank-owned account selected for evaluation.
• Stable customer and transaction references.
• KYC tier and supported customer due-diligence facts.
• Non-null is_shell_company and has_complete_cdd values, including false.
• PEP, sanctions, and adverse-media flags when available in the CBS.
• Privacy-safe account snapshot facts.
• context.current_balance, using the CBS balance for the evaluated account at request time.
• Supported real-time context signals agreed for the integration.

Vantrace-derived values

Vantrace derives or resolves:

• Bank-account ownership against the authenticated tenant.
• Historical transaction windows.
• Daily-spend totals.
• Transaction-count and amount baselines.
• Behavioural-data sufficiency.
• The account and customer used for history enrichment.
• PEP, sanctions, and adverse-media values only when the corresponding CBS field is empty.
• The customer risk score and rating. See Customer risk scoring.
• Rule applicability, results, and failure status.

Vantrace retains CBS-supplied screening values and fills only empty screening fields. Other backend-owned values are resolved by Vantrace for use by the decision engine.

For is_shell_company and has_complete_cdd, an omitted or null CBS value falls back to the stored database value without overwriting it. If neither source has a value, the result remains null (unknown).

Data minimisation

Use opaque identifiers wherever possible. Do not send information that is not required by the documented schema or an agreed context field.

• Do not put API keys, secrets, passwords, or identity documents in any field.
• Avoid personal information in narration and free-text values unless it is required for screening.
• Do not place raw account numbers in fields intended for internal identifiers.
• Keep identifiers stable across requests so history and reconciliation remain accurate.

Why this separation matters

If every caller calculates its own transaction windows and risk baselines, two integrations can produce different decisions for the same facts. Backend-derived values provide consistent tenant-scoped history and prevent an external counterparty’s activity from being treated as the bank customer’s behaviour.