Talk to us

Apply your institution’s rules across your digital asset operations

Keep your existing custody and signing providers while enforcing rules for activity entering your private network. Set approved destinations, require independent approval for higher-value transfers and see why activity was stopped.

Talk to usExplore Commander

Set where funds can go and who must approve

A USD 2.5 million transfer from Treasury. Policy Engine checks the destination and collects two independent approvals. A transfer to the supplier account passes and goes on to signing; a transfer to an unapproved account stops at the destination check. Each decision is recorded.
Transfer request

USD 2.5m from Treasury

Policy Engine
  1. Approved destination
  2. First independent approval
  3. Second independent approval
Signing
Decision recorded

Example: transfers above USD 1m require two independent approvals. The requester cannot approve their own transfer.

Approved: released to signing. The decision is recorded.

Prevent transfers to unapproved recipients

An authorized employee can still request a transfer to the wrong recipient. Set approved destinations so Policy Engine can block transfers outside that list before submission.

Rules can also account for the amount, asset and person or service making the request.

Give higher-value transfers an independent check

Require another person’s approval before a higher-value transfer proceeds. Choose the roles responsible for reviewing it and the number of approvals needed. You can prevent the requester from approving their own transfer.

Routine transfers that meet your rules can proceed without that additional approval.

Give operations teams a clear reason for stopped transfers

Operations teams can see why a transaction was blocked and which rule determined the outcome.

Operations teams can explain the decision to whoever requested the transfer. Authorized staff can also see which rules were checked when a transaction was allowed or held for approval.

Transfer decisions as operations staff see them: a blocked, a held and an allowed transfer, each with the rule that determined the outcome.
Transfer decision
Request
USD 8m · Treasury → supplier
Result
Blocked before submission
Rule
The supplier’s destination is not approved

Prevent unreviewed changes to your financial controls

The person proposing a policy change needs an independent reviewer’s approval before it takes effect. The approval applies to the exact version reviewed. Further edits require a new approval.

This gives your institution a separate check on changes to its rules, as well as the transfers governed by them.

A policy change proposed by a treasury lead takes effect only after a risk officer approves it. The approval covers the exact version reviewed; an edit afterwards needs a new approval, and the approved version stays in effect until then.
Policy change
  1. Version 4 proposedTreasury lead
  2. Independent reviewRisk officer
  3. Version 4 in effectApproved version only
Version 4 approved by an independent reviewer and in effect.

Keep your existing custody and signing provider

Your provider continues to hold keys and sign transactions. Policy Engine adds your institution’s rules to supported activity on the private network.

With those rules enforced as transactions enter the network, using a different application does not remove the policy check. Your institution can apply its controls alongside the provider it already uses.

Transactions from a treasury application and a payments application both pass Policy Engine's destination and approval checks before the institution's own custody provider signs them.
Treasury application
Payments application
Policy Engine
  1. Approved destination
  2. Approval threshold
Your custody provider
  1. Holds the keys
  2. Signs the transaction

Frequently asked questions

What happens if the rules change while a transfer is awaiting approval?

After the final approval, Policy Engine applies the current rules. It blocks the transfer if those rules do not permit it.

Discuss your policy requirements

Talk to the Prividium team about the operations you need to govern and the rules you want to enforce.

Talk to us