Skip to content

Latest commit

 

History

History
16 lines (10 loc) · 1.33 KB

File metadata and controls

16 lines (10 loc) · 1.33 KB

TravelRuleResult

Properties

Name Type Description Notes
direction TravelRuleDirectionEnum [optional] [default to undefined]
isVerified boolean Whether the travel rule information was verified [optional] [default to undefined]
action TravelRuleVerdictEnum [optional] [default to undefined]
providerResponse { [key: string]: any; } 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] [default to undefined]
matchedRule TravelRuleMatchedRule [optional] [default to undefined]

[Back to top] [Back to API list] [Back to Model list] [Back to README]