Methods

  • Sets a signer. The signer must implement ISigner interface

    Provided signer will be used later on to sign messages within checkRisk and downloadReport methods

    There is one exception

    In case of checkRisk and downloadReport overloads that get PureFIPayload as an argument, mentioned methods assume you signed a message by yourself (probably you have a specific scenario around signing), so you don't need to set any signer at all in this particular case

    All for the sake of flexibility

    Parameters

    Returns void

  • Sets issuer url

    Parameters

    • baseUrl: string

    Returns void

  • Performs AML risk score screening

    It assumes that provided address is the address of a wallet

    Parameters

    • param: string

      An address to screen

    • Optionalconfig: AxiosRequestConfig

    Returns Promise<CheckRiskResponse>

  • Performs AML risk score screening

    It assumes that provided addresses are wallet-kind addresses

    Parameters

    • param: string[]

      An array of addresses to screen

    • Optionalconfig: AxiosRequestConfig

    Returns Promise<CheckRiskResponse[]>

  • Performs AML risk score screening

    Allows to specify what type of address you screen

    Parameters

    • param: PureFIAddress

      A PureFIAddress to screen

    • Optionalconfig: AxiosRequestConfig

    Returns Promise<CheckRiskResponse>

  • Performs AML risk score screening

    Allows to specify what type of addresses you screen

    Parameters

    • param: PureFIAddress[]

      An array of PureFIAddress'es to screen

    • Optionalconfig: AxiosRequestConfig

    Returns Promise<CheckRiskResponse[]>

  • Performs AML risk score screening

    Consider using this overload if you want to have more control

    over message signing and handle this process by yourself

    In this particular case you don't need to set any signers

    Parameters

    Returns Promise<CheckRiskResponse[]>