Skip to content

Latest commit

 

History

History
18 lines (10 loc) · 1.18 KB

File metadata and controls

18 lines (10 loc) · 1.18 KB

ScreeningTravelRuleResult

Detailed Travel Rule screening result containing provider-specific data. Contains Travel Rule specific information like verified status, rule type, and actions.

Properties

Name Type Description Notes
direction TravelRuleDirectionEnum [optional]
isVerified Boolean Whether the travel rule information was verified [optional]
action TravelRuleVerdictEnum [optional]
providerResponse Map<String, Object> Complete response from the travel rule provider. This is a dynamic object that varies significantly between different travel rule providers (NOTABENE etc.). Each provider has their own proprietary response format and schema. Examples of provider-specific structures: - NOTABENE: Contains VASP information, PII data, protocol-specific fields The structure is provider-dependent and cannot be standardized as each vendor implements their own proprietary data models and response formats. [optional]
matchedRule ScreeningTravelRuleMatchedRule [optional]