Set up Travel Rule

To set up Travel Rule, connect your Notabene account to Wallet-as-a-Service, prepare your address book, and then create Travel Rule policy rules on your wallets.

1. In the Wallet-as-a-Service console, go to Settings > Integrations.

2. On the Notabene card, select Connect.

   

3. Enter your Client ID, Client secret, and Notabene VASP DID. The DID looks like did:ethr:0x….

4. Select Connect.

Wallet-as-a-Service checks the credentials and DID with Notabene, and then registers a webhook with Notabene so it receives message updates. The Travel Rule page shows your VASP name, VASP DID, webhook URL, and one of these statuses:

If Notabene rejects the credential and DID pair, the console shows an error and doesn't save the connection.

The Notabene card on the Integrations page shows Connected as soon as you save the connection, even while the Travel Rule page shows Webhook pending. To check the connection status, select View on the card.

On the Notabene connection page, select Disconnect. Disconnecting removes your Notabene credentials and stops Travel Rule checks for your organization.

Your Travel Rule policy rules stay in place. While you're disconnected, Wallet-as-a-Service rejects every outbound transfer that matches a Travel Rule rule, with reason TRAVEL_RULE_NOT_CONFIGURED. If you no longer need the rules, delete them.

Wallet-as-a-Service takes beneficiary information from your address book. For every external destination that a Travel Rule rule covers:

1. Save the destination as an address on a counterparty of type organization, with its legal name.

2. On the address, select Add custodian details. Under Select custodian, enter the beneficiary VASP's name, select Search, and then select the VASP from the Notabene directory.

3. Confirm that the custodial information is correct, and then select Add address. The address takes effect after your Addresses approvers approve it.

   

Wallet-as-a-Service rejects a covered transfer to a destination that isn't in the address book, has no custodian details, or belongs to an individual counterparty.

You need a connected Notabene account before you can create Travel Rule rules. Without one, the console shows Integrate a travel rule provider to add this policy type, and the API returns PAL006.046.

1. Open the wallet and go to the Policy tab.

2. Select Add a new rule.

3. On the Direction step, select Outbound for transfers from this wallet, or Inbound for deposits into this wallet, and then select Next.

4. On the Conditions step, select the asset, and then select Travel rule under Rule.

5. For an outbound rule, select a level under Release the withdrawal when. See Release levels.

   

6. On the Scope step, select the destinations the rule covers. For an inbound rule, the selection applies to the sender, even though the step labels it To.

7. On the Advanced step, leave All selected, or restrict the rule to one user or API credential.

8. On the Confirm step, review the rule, and then select Add policy rule.

The console creates a Travel Rule rule for one asset, with no amount threshold. To cover all assets, or only transfers of more than an amount, use the API.

POST /v2/vaults/{vaultId}/wallets/{walletId}/policy-rules

Outbound: This rule requires an accepted Travel Rule exchange for counterparty transfers of more than 1,000 of the asset:

{
  "trigger": "OUTBOUND_INITIATED",
  "assetId": "3::XRP",
  "matchers": [
    { "type": "ALL_COUNTERPARTIES", "values": [] }
  ],
  "definition": {
    "kind": "TRAVEL_RULE",
    "travelRule": {
      "travelRuleReleaseLevel": "TRAVEL_RULE_RELEASE_LEVEL_ACCEPTED",
      "amount": {
        "threshold": "1000",
        "operator": "GT",
        "aggregation": "SINGLE_TX"
      }
    }
  }
}

Inbound: This rule checks every deposit into the wallet, for any asset:

{
  "trigger": "INBOUND_DETECTED",
  "definition": {
    "kind": "TRAVEL_RULE",
    "travelRule": {}
  }
}

The release level sets how far the outbound Travel Rule message must progress before Wallet-as-a-Service lets the transfer continue to signing.

A stricter level is safer but slower. If the counterparty doesn't respond, the transfer waits until it times out.

If several Travel Rule rules apply to the same transfer, the most specific rule wins. For example, a rule for one counterparty overrides a rule for the whole wallet. When rules are equally specific, a rule with an amount threshold overrides a rule without one.

• Sweeps, Web3 signing, plaintext signing, passkey signing, and passkey transfers.
• Transfers to your own wallets, unless a rule covers them. A rule with no matchers, or with a WALLET_ID matcher, covers transfers to your own wallets. Wallet-as-a-Service sends these as same-VASP transfers, which Notabene settles without a counterparty response. Rules with ALL_COUNTERPARTIES, COUNTERPARTY_ID, or ADDRESS_ID matchers don't cover your own wallets.

• Travel Rule transactions
• Policy rules (Policy Engine v2)
• Manage counterparties