Transaction risk,
in focus.

Prism gives merchants and payment operations teams the same view of transaction risk. See what drove a decision, investigate declines, and test rule changes before they affect payments.

Explore the simulator
Decision traceSample transaction
$1.00Online payment
Declined
  1. Hard blocksCard testing rule matched
  2. Model scoreSkipped after hard block
  3. Behavior overridesSkipped after hard block
  4. Audit and countersDecision recorded

How Prism decides

Each payment follows the merchant’s risk policy. A hard block can end evaluation early. When a payment continues, Prism can assess its model score and behavioral signals before logging the decision.

Transaction signalsPayment data and activity
Sample decision traceDeclined · Rule matched
  1. L1 · AVS mismatch

    Hard blocks

    Apply explicit policy checks first. A match, such as an address verification mismatch under the active policy, can decline a payment before scoring.

  2. L2 · Score 82/100

    Model score

    See a live transaction risk score for eligible merchant payments. The score adds context to the decision alongside policy and behavior checks.

  3. L3 · Card velocity

    Behavior overrides

    Check activity across transactions. Card velocity and unusual changes in spend can add context that a single payment cannot provide.

  4. L4 · Decision logged

    Audit and counters

    Log the outcome and the path that led to it. Velocity counters update after Prism returns its decision.

A shared view of payment risk.

Merchant console

Start with the review queue. Open a declined payment, see which check drove the decision, and record whether the activity was fraudulent or legitimate. The rules view shows which policies and shadow tests apply to your business.

Prism Merchant console showing shadow tests and enforced rules
Rules and shadow tests

Prism admin

Manage merchant-level policy and settings. Create a rule, review which transactions it would flag in shadow mode, and choose when to promote it to enforcement.

Prism admin showing the controls for custom rules and shadow mode
Custom rule controls

Test before you enforce.

Start with a merchant profile. Adjust traffic volume and the mix of simulated fraud, then introduce a preset scenario and inspect the decisions as they arrive.

Simulation uses generated transactions so you can see approvals, declines, false alarms, and shadow flags in a controlled scenario. Shadow testing evaluates a candidate rule against incoming transactions while the current policy continues to make live decisions.

Prism Live simulator showing traffic controls, scenario presets, and decision metrics
Live simulator with generated traffic
Prism transaction detail showing the reason for a decline, skipped layers, audit status and review actions
Transaction detail in the merchant console

Find what drove a decline.

A decline has a decision path. Open the transaction to see the rule that matched, the layers that ran or were skipped, and the elapsed decision time. Then record the review outcome so it can inform future policy decisions.

Try the sample trace

Prism in practice

Does a shadow rule change what happens to a live payment?

A shadow rule records a flag when it would match. The enforced policy still determines the payment outcome. Operations can review those flags before promoting the rule.

Why might a transaction have no model score?

An enforced hard block can stop evaluation before model scoring. The decision trace shows the rule that matched and the layers Prism skipped.

What happens when a merchant marks a decline as legitimate?

Prism records the merchant’s review label alongside the transaction. The label becomes feedback for risk teams evaluating policy and model inputs.

Follow a payment through Prism.

Compare a rule match, a velocity flag, and a routine payment to see how the decision path changes.

Try the decision trace