How Policies are Evaluated
When a transaction is initiated from a wallet, the Policy Engine evaluates all policies within the enterprise in the following order:
Policies that don’t apply (i.e., not in scope), are disregarded
Conditions from each policy are evaluated
Actions are triggered based on the conditions
If there are redundant actions, the Policy Engine identifies these and deduplicates them
If any actions are Automatically Reject, this will trump all other actions and the transaction will be rejected
If an individual wallet policy differs from a policy that applies across all wallets, the more restrictive policy takes precedence. For example, if the spending limits are lower for a wallet than for all wallets in the enterprise, then that wallet uses the lower limits.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article