Notabene

Edit online

IBM Digital Asset Haven integrates with Notabene to help you comply with the FATF Travel Rule. This solution automates the secure exchange of required originator and beneficiary information with other Virtual Asset Service Providers (VASPs) before executing transactions. By using Notabene’s end-to-end Travel Rule compliance software, you can meet global regulatory requirements while maintaining operational security and efficiency.

Setup

IBM Digital Asset Haven Org Settings
Note:

Before defining Notabene Travel Rule policies, you must:

  • Have a Notabene account

  • Provision a new API key for IBM Digital Asset Haven

  • Register the IBM Digital Asset Haven webhook URL in the Notabene dashboard

  1. In the IBM Digital Asset Haven dashboard, navigate to Settings > Integrations > AML.
  2. Select the Notabene tab. If Notabene is not activated for your organization, contact your IBM Digital Asset Haven Sales Representative.
  3. Check Activate Notabene Integration. A webhook URL will be generated.
  4. Navigate to your Notabene dashboard. From the VASP dashboard, go to Settings > Multi-Message Webhook.
    1. Paste the webhook URL into the Endpoint URL field.
    2. Subscribe only to notification.transactionUpdated events.
    3. After submitting the form, note the signing secret.
  5. In the Notabene dashboard, go to Settings > API Credentials and generate API credentials. Note the Client ID, Client Secret, and VASP DID.
  6. In the IBM Digital Asset Haven Notabene settings window, paste the Client ID, Client Secret, Signing Secret, and VASP DID into the respective fields.

Policy

Outgoing transfers can be screened for Travel Rule compliance by creating a policy with:
  • Activity kind: Wallets:Sign
  • Rule kind: TravelRuleTransactionPrescreening
  • Action kind: Block
When using TravelRuleTransactionPrescreening, the transfer attempt is validated by Notabene and forwarded to the counterparty VASP (if applicable). If validation fails, the counterparty rejects the transfer, or the request times out, the details are published in the policy.triggered webhook event.

Travel Rule Transfer Payload

After Notabene has been configured in IBM Digital Asset Haven settings and a policy is in place, transfers can include an additional travelRule JSON field.
Field Type Required Description
kind string Yes Must be Notabene to identify the Travel Rule integration.
beneficiaryVASPdid string No The Decentralized Identifier (DID) of the beneficiary VASP. Required for custodial transfers.
beneficiaryProof object No A proof object for non-custodial (unhosted) wallet transfers. Used to verify ownership of the beneficiary’s wallet.
originator object Yes Contains PII of the originator. Must be encrypted using the Notabene PII SDK.
beneficiary object Yes Contains PII of the beneficiary. Must be encrypted using the Notabene PII SDK.

PII Structure and Encryption

The originator and beneficiary fields must conform to interVASP Messaging Standard 101 (IVMS101). This standard defines the required information exchange between VASPs.

It is mandatory to encrypt PII data for both fields using the Notabene PII SDK.