Skip to main content

Fireblocks

Overview​

We have partnered with Fireblocks to introduce automated AML and KYT screening. Fireblocks leverages the VAAS rules engine to ensure that your organization stays secure and compliant.

Before you begin​

  1. You need to request your Callback URL from VAAS support and the Co-Signer Public Key. It will be used during the setup process of the Fireblocks Co-Signer Callback Handler.

Configuring the API Co-Signer with Callback Handler​

  1. Follow Fireblocks' step-by-step instructions for configuring the Co-Signer.

  2. During the Co-Signer setup process, the script will prompt for the callback URL. At this point, simply input the URL provided by the VAAS support team.

    Please enter callback URL (if using callback URL, else empty)

  3. Next, the script will prompt you to select the authentication method.

    Please select one of the callback authentication options: (1)-PUBLIC KEY (2)-certificate
  • Select option (1)-PUBLIC KEY.
  • The script will prompt you to paste the Co-Signer's callback public key.

  1. Paste the Co-Signer's callback public key

  2. Now, just continue and complete the Co-Signer setup process.

When your API Co-Signer is configured with VAAS API as the callback handler, it sends a POST request containing a JSON Web Token (JWT) encoded message signed with the API Co-Signer's private key. VAAS API uses the API Co-Signer's public key to verify that every incoming JWT is signed correctly by the API Co-Signer.

Therefore, it's necessary to send the Co-Signer's public key to the VAAS support team so that authentication can be configured.