Skip to main content

[Transact] - Sample account configuration for Travel Rule messaging

Written by Emanuel
Updated over a week ago

Disclaimer:
The following template is provided for informational purposes only and does not constitute legal advice.
You should configure your policies in consultation with your compliance and/or legal team to ensure alignment with internal policies and applicable regulations.

Several settings will depend on whether you are using the Notabene marketplace integrations. For Travel Rule messaging, make sure you review the TAP policies and the Workspace settings.

I. Policy Configuration Guidelines

Important: When multiple policies apply, the most restrictive outcome takes precedence: Reject → Flag → Authorize
Exceptions: Network policies take priority over Counterparty and Jurisdictions policies.

Requirements (TAP)

  • Enable Travel Rule Information for all transactions above threshold to ensure you receive all required data from counterparties.

  • Enable Settlement Address Confirmation for outgoing transactions to verify that PII data is shared only with the intended counterparty

  • Enable automatic sending of Travel Rule information to beneficiary VASPs to ensure required data is shared promptly and in compliance with regulatory obligations.

Sanctions

  • Authorize transactions with no sanction matches.

  • Flag for manual review transactions where the counterparty is a potential match.

  • Enable the toggle to also flag transactions where the sanction screening tool returned an error.

Risk Score

  • Authorize transactions with a low risk score.

  • Flag for manual review transactions with a medium or high risk score.

  • Reject transactions with a severe risk score.

  • Flag any transactions where the blockchain analytics tool returned an error.

Assets

  • Reject incoming transactions involving unsupported assets.

Amounts

  • Authorize transactions that fall below your jurisdictional threshold.

Exceptions

  • Authorize transactions that do not match any existing policy.

Jurisdictions

  • Reject transactions involving entities incorporated in jurisdictions subject to a FATF call to action (blacklist).

  • Flag for manual review transactions involving jurisdictions under increased monitoring (grey list).

  • Authorize transactions with VASPs incorporated in other jurisdictions.

See FATF "Black and grey" lists here.

II. Settings

Workspace

  • Enable Notabene-Managed PII Encryption to allow Notabene to securely manage the encryption process (Disable this only if you plan to use your own end-to-end encryption solution).

  • Enable Travel Rule Information to Beneficiary Entities to automatically send Travel Rule data to counterparties as required by your jurisdiction.

Webhooks

  • Enable the toggle to allow Notabene to send compliance-related messages to your internal systems (Note: Some technical setup effort is required for webhook integration).

API Credentials

  • Generate API credentials to initiate the technical integration process with Notabene’s platform.

Teams

  • Add team members and assign appropriate roles

For any questions, reach out to our support team.

Did this answer your question?