Skip to main content

[V2.1] Travel Rule Settings

See which jurisdiction's Travel Rule applies to you, and choose how much data you send to counterparty institutions.

Written by Emanuel

Notabene keeps the Travel Rule of each jurisdiction that enforces it: which data must travel with a transfer, and the threshold above which it applies. Authorization Rules › Travel Rule shows which of these rules apply to you, and lets you choose how much of your data goes to counterparty institutions.

The Travel Rule screen, the two transmission modes boxed

Applied jurisdiction

Applied jurisdiction names the jurisdiction whose rules your organization follows, by default your own. Your presentation requirements come from it: the data you must send, and the data you expect to receive. When Notabene has no rules for a jurisdiction, the FATF defaults apply.

Transmission mode

The transmission mode decides whether the data you send meets only your own rules, or the counterparty's jurisdiction's rules too.

  • Own obligations: you send exactly what your own presentation requirements ask for, whatever the counterparty may need.

  • Mutual regulatory requirement: you send what your own requirements ask for, plus any field the counterparty's jurisdiction strictly requires beyond them. A counterparty's custom rules are never taken into account.

With Mutual regulatory requirement, a transaction below your own threshold but above the counterparty's still sends your data. To change the mode:

  1. Go to Authorization Rules › Travel Rule.

  2. Under Transmission mode, select Own obligations or Mutual regulatory requirement.

  3. Click Save.

Custom requirements

Under Own obligations, Select custom requirements applies a specific rule set instead of your jurisdiction's requirements. Notabene defines these rule sets, and you choose among them.

To follow other rules than your jurisdiction's, for example to send data on every transaction whatever the threshold, click Contact us under Need help?.

Flexible identifiers

Some jurisdictions accept any one of several identifiers, such as the originator's customer identification number, date and place of birth, or address. Notabene picks one for each transaction:

  1. If an identifier on the customer profile is also required in the counterparty's jurisdiction, Notabene sends that one, whatever your transmission mode. If several match, it sends the first.

  2. Otherwise, Notabene sends the first identifier available on the customer profile.

Data minimization

Only the selected identifier leaves with the transaction, and the others stay on the customer profile. The same goes for every field: Notabene sends only what your requirements call for, even when your systems supplied more.

You remain responsible for your Travel Rule compliance. Check these rules and Notabene's implementation of them against your regulatory obligations. Tell support@notabene.id about any discrepancy, unsupported jurisdiction or regulatory change.

Which requirements use these settings, such as Send Travel Rule data, is set in Requirements. For the data each transfer needs in the API, see Data collection in the developer docs.

Did this answer your question?