/* tslint:disable */ /* eslint-disable */ /** * Fireblocks API * Fireblocks provides a suite of applications to manage digital asset operations and a complete development platform to build your business on the blockchain. - Visit our website for more information: [Fireblocks Website](https://fireblocks.com) - Visit our developer docs: [Fireblocks DevPortal](https://developers.fireblocks.com) * * The version of the OpenAPI document: 1.6.2 * Contact: developers@fireblocks.com * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). * https://openapi-generator.tech * Do not edit the class manually. */ // May contain unused imports in some cases // @ts-ignore import { ScreeningTravelRuleMatchedRule } from './screening-travel-rule-matched-rule'; // May contain unused imports in some cases // @ts-ignore import { TravelRuleDirectionEnum } from './travel-rule-direction-enum'; // May contain unused imports in some cases // @ts-ignore import { TravelRuleVerdictEnum } from './travel-rule-verdict-enum'; /** * Deprecated: This field is not currently returned in the API response. Detailed Travel Rule screening result containing provider-specific data. Contains Travel Rule specific information like verified status, rule type, and actions. * @export * @interface ScreeningTravelRuleResult */ export interface ScreeningTravelRuleResult { /** * * @type {TravelRuleDirectionEnum} * @memberof ScreeningTravelRuleResult */ 'direction'?: TravelRuleDirectionEnum; /** * Whether the travel rule information was verified * @type {boolean} * @memberof ScreeningTravelRuleResult */ 'isVerified'?: boolean; /** * * @type {TravelRuleVerdictEnum} * @memberof ScreeningTravelRuleResult */ 'action'?: TravelRuleVerdictEnum; /** * 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. * @type {{ [key: string]: any; }} * @memberof ScreeningTravelRuleResult */ 'providerResponse'?: { [key: string]: any; }; /** * * @type {ScreeningTravelRuleMatchedRule} * @memberof ScreeningTravelRuleResult */ 'matchedRule'?: ScreeningTravelRuleMatchedRule; }