Important: Network policies have priority over Counterparty and Jurisdictions policies.
The Notabene Policy Engine enables you to define specific criteria to authorize, reject, or flag transactions for manual review. You can configure jurisdictional policies manually for individual countries or use the filter button (top-right) to select entire regions and apply bulk actions, as demonstrated in the video below.
How jurisdiction policies apply
Jurisdiction policies are evaluated across two types of checks:
VASP-level checks — evaluate the jurisdiction of the counterparty institution.
End-customer (PII) checks — evaluate the jurisdiction of the originator or beneficiary included in the transaction data.
How jurisdiction policies interact with other rules
Jurisdiction policies are part of the overall policy engine and are evaluated alongside other policy layers:
Network rules (Trust / Flag / Ban) can override jurisdiction policies for specific counterparties (VASP-level checks only).
End-customer (PII) jurisdiction checks always apply and cannot be overridden.
Transaction-level checks always run and cannot be overridden.
Why this matters
Jurisdiction policies allow you to:
manage geographic risk across transactions
apply consistent rules across regions
combine location-based controls with counterparty and transaction-level checks
Example
If a jurisdiction policy flags a country but a specific VASP from that country is marked as Trusted, the transaction may still be authorized. However, if the transaction involves an end-customer located in a restricted jurisdiction, it may still be flagged or rejected regardless of trust settings.
Contact us at support@notabene.id if you have any questions or need our assistance.