Your policies decide each transaction automatically, so your team only reviews what needs judgement. Each rule looks at one thing, such as a counterparty institution's jurisdiction or a wallet's risk score, and gives a verdict. You set them under Authorization Rules › Policies.
Verdicts
Approve: your side is authorized once every requirement is met, with nothing for your team to do.
Flag: the transaction waits for a person on your team to approve or reject it, as described in Reviewing Flagged Transactions.
Reject: your side rejects the transaction.
When several rules apply, the strictest verdict wins: a rejection beats a flag, and a flag beats an approval. Only your policies can flag a transaction, so your team can't add a flag by hand. The verdict stays private to your organization, and counterparty institutions see only your status.
Changing policies takes the Group Admin or Entity MLRO role, as listed in Member Roles and Permissions.
Evaluation order
Every transaction goes through three layers at once, listed at the bottom of the Policies screen:
Policy rules: the rules you set for a property of an institution, customer, wallet or token, or for the transaction amount.
Not reviewed: the verdict for an institution, customer, wallet or token that no rule matched and that has no policy of its own.
General Default: the verdict when neither of the above gave one.
Policy rules and Not reviewed verdicts combine, and the strictest wins. So when a customer's screening result approves but the counterparty institution falls to a Not reviewed verdict of Flag, the transaction is flagged.
A rule applies only when the transaction has what it looks at. A transfer to a self-hosted wallet has no counterparty institution, so the counterparty institution rules don't apply to it.
General Default
The General Default is Approve, Flag or Reject, and it is never empty. A new organization starts at Flag, so every transaction that nothing else covers waits for review until you change it.
Not reviewed verdicts
A new counterparty institution, or anything else your organization hasn't reviewed yet, falls to the Not reviewed verdict for its kind. You set one for counterparty institutions, counterparty customers, counterparty wallets, your customers and tokens, next to each heading under Policy rules by entity.
Each Not reviewed verdict is Approve, Flag, Reject or No policy. With No policy, that kind gives no verdict of its own and the General Default decides. Changing a Not reviewed verdict updates every institution, customer, wallet or token that currently falls to it.
Policy rules
Click a heading under Policy rules by entity to see its rules. Each heading holds a fixed set of rules, and each rule has a verdict and an on/off switch. You can't add or remove rules, and some accept only one verdict: a rule for a Banned jurisdiction can only reject.
Each rule also applies to all transactions, incoming only or outgoing only. So you can flag incoming transactions from a jurisdiction and reject outgoing ones to it.
Counterparty institutions: the status of the institution's jurisdiction, as set in Jurisdictions, and whether it lacks the Receive or Respond capability.
Counterparty customers: the status of the customer's jurisdiction, and the result from your sanctions screening provider: No match, Potential match or Provider unreachable.
Counterparty wallets: the risk score from your blockchain analytics provider, in that provider's own levels.
Self-hosted wallets: whether the address's proof of ownership is verified.
My customers: no rules of their own, only the Not reviewed verdict and any policy you set on one customer.
Tokens: the token's status, Supported or Not supported, as set in My Organization › Tokens.
Transaction amount: the value of the transaction.
Screening and risk-score rules appear only for the providers you connected in Integrations. When you connect one, its Provider unreachable rule is switched on, and it always flags.
Transaction amount
Amount rules read the transaction's value in the reference currency you choose next to Transaction amount. The options are USD, your local currency and your regulatory currency, and the screen labels each one. A transaction's value is worked out once and stored, so a later change in the exchange rate doesn't move it.
A policy for one institution, customer or wallet
The Policies screen sets rules for every institution, customer or wallet of a kind. To decide about one in particular, set it on its row in its own screen. For a counterparty institution that is Network › Directory, and for customers Network › Counterparty Customers or My Organization › My Customers. Each of those screens shows a summary of your policies at the top, and its Edit policies button opens the matching section here.
A policy you set on one institution, customer or wallet replaces what the rules would give it. The other policies on the transaction still apply, such as the amount or the wallet, and the strictest still wins.
Your policy stays until something new gives a stricter verdict. If its jurisdiction later moves to Watched, for example, and your rules flag Watched jurisdictions, its policy moves to Flag. A lighter result never replaces your policy, so relaxing it is always your team's decision.
When a policy changes
A change to a rule, a Not reviewed verdict, a jurisdiction status or a policy on one institution re-evaluates whatever it affects. Every transaction involved that isn't settled is then re-evaluated, except a rejected one, which stays rejected.
Approve: a pending transaction is authorized once its requirements are met.
Flag: the transaction waits for review. An authorized transaction goes back to Pending.
Reject: the transaction is rejected.
Your policies decide whether a transaction is allowed. What must happen before your side is authorized, such as sending Travel Rule data, is set in Requirements.
For how your backend reads a verdict, see Policies in the developer docs.
