Integrating Notabene Into Your Fireblocks Policies

Let's take a look at where Notabene sits within your larger Fireblocks transaction flow.

After you create a transaction in Fireblocks the following happens:

1. Your travel rule screening policy determines whether or not the transaction will be screened.
2. If the transaction is screened then a travel rule message will be created and sent to your counter-party VASP.
3. The travel rule screening status will remain pending in Fireblocks until your travel rule message reaches a certain state in Notabene, after which the travel rule screening status will be update to completed, rejected, or cancelled.
4. Your travel rule post-screening policy will use the status of your travel rule screening to determine how to proceed with the transaction.

Screening Policy

The travel rule transaction screening policy determines what transactions are forwarded to Notabene. You can read more about travel rule screening policies in Fireblocks here.

The default screening policy is to screen all transactions except the following:

• Transactions along Unsupported Routes.
• Transactions involving unsupported assets (either unsupported by Fireblocks or unsupported by Notabene)
  • See Notabene's supported asset list and information on requesting new assets here.
• Transactions without the required additional travel rule data.
• Transactions in a workspace where AML screening is bypassed or not activated.

If a transaction falls into one of the above four categories then the travel rule screening will have a status of "Bypassed".

Deciding When a Notabene Screening is "Complete"

When you screen a Fireblocks transaction through Notabene, the Fireblocks travel rule screening status will be "Pending" until the screening is completed in which case the status will be "Completed", "Cancelled" or "Rejected".

Meanwhile, every travel rule message created on Notabene will have its own Notabene status. You can configure which Notabene status your travel rule message must reach in order to complete the Fireblocks screening.

There are four options for this configuration:

1. NEW - You wait to transfer the funds until after the travel rule message is created.
2. SENT - You wait to transfer the funds until after the travel rule message is sent to the counter-party VASP.
3. ACK - You wait to transfer the funds until after the counter-party VASP has confirmed ownership of the destination blockchain address.
4. ACCEPTED - You wait to transfer funds until after the counter-party VASP has accepted the transfer.

You can see the full travel rule message flow below.

Once you have decided which status you require for a "Complete" screening, you must update the setting in the Notabene UI.

Menu -> Settings -> Blockchain Transaction Authorization

The below tables show the relationship between each Notabene status and Fireblocks screening status depending on the blockchain transaction authorization setting you have chosen.

Fireblocks screening is considered complete when the travel rule message has a status: NEW

Fireblocks screening is considered complete when the travel rule message has a status: SENT

Fireblocks screening is considered complete when the travel rule message has a status: ACK

Fireblocks screening is considered complete when the travel rule message has a status: ACCEPTED, DECLINED, REJECTED, or NOT_READY

Post-Screening Policy

Once the Notabene travel rule screening is complete, your Fireblocks post-screening policy will use the screening status to determine what actions are necessary, ie whether or not to proceed with the transaction.

You can read more about how to configure your travel rule post screening policy and see an example here.