The Notabene Policy Engine allows you to define automated rules for handling transactions by authorizing, rejecting, or flagging for manual review based on specific criteria.
Requirements: Define your TAP policies for sending and receiving transactions before granting authorization.
Example: Require travel rule information from the originating entity for transactions that exceed your jurisdictional threshold.
Sanctions: Automatically authorize, reject, or flag transactions based on whether the counterparty is a potential match against a sanctions list.
Example: Authorize transactions when the counterparty is not sanctioned.
Risk Score: Automatically take action based on the counterparty’s risk rating.
Example: Reject transactions if the counterparty’s risk score is high.
Assets: Define actions based on asset type.
Example: Reject all incoming transactions of Monero (XMR).
Amounts: Define actions based on transaction amount.
Example: Authorize all incoming transactions below $10 USD.
Exceptions: Decide how to handle transactions that do not trigger any policies.
Example: Flag unmatched transactions for manual review.
Contact us at support@notabene.id if you have any questions or need our assistance.