Policies

    Set your policy thresholds

    Choosing the numbers behind your rules, and how to pick them for the way your company actually pays.

    Version 1.0 · Last updated

    When you would do this

    At setup, when your payment volumes change, after an incident, or when your team complains that everything is flagged.

    Only an Admin can change policies.

    Steps

    1. Go to Governance › Policies.
    2. Choose a starting template, Standard or Strict, or start from your current settings.
    3. Work through the controls on the External Payments and Internal tabs, setting each threshold.
    4. If you use native coins, enable Native Token Self-Approval Limits and set a limit per coin. You can prefill these from your currency limits and then adjust.
    5. Read the Policy Summary panel. It restates everything in plain language.
    6. Select Publish Changes.
    7. Sign the queued policy update in Operation › Signing.

    How to choose your numbers

    Document threshold. Set it at the point where you would expect a paper trail anyway. Too low and your team uploads the same document repeatedly for routine payments, which trains everyone to treat evidence as a formality. Too high and your largest payments have nothing behind them.

    New recipient threshold. Set it low. Paying someone for the first time is where nearly all payment fraud happens, and the cost of a flag is a few minutes.

    External self-approval limit. Set it at the amount you would be comfortable with a single trusted person sending without anyone else looking, on their worst day, on a phone, in a hurry. That number is usually lower than the first one people suggest.

    Swap and internal limits. These can reasonably be higher than external payments, because funds stay under your control. They are not zero risk, but a mistake is recoverable in a way an external payment is not.

    Native coin limits. Entered in units of the coin, not in currency. A limit that looks small in coin terms may be large in value, and the value moves.

    What to expect

    Publishing does not take effect immediately. It queues a policy update that requires signatures, then applies.

    Changes apply to payments created after they take effect. Payments already in the queue keep the rules they were created under.

    If your team says everything is flagged, that is information. Either your thresholds are wrong for your volumes, or your payment patterns are genuinely irregular. Find out which before loosening anything.

    Common problems and what they mean

    You cannot edit anything. You are not an Admin.

    Your change has not applied. It is waiting in the signing queue.

    Native coin payments still need quorum. Native limits are not enabled, or not set for that coin.

    "Live exchange rates unavailable." The prefill from currency limits cannot be calculated. Enter the coin amounts manually.