Skip to main content
Simulación lets your team send sample transactions through the same decision pipeline used in production — without charging a card or calling your payment processor.

​
Why use it

  • Validate blocklists and protection rules after changes
  • Train analysts on approve, review, challenge, and decline outcomes
  • Populate the Panel and Monitor with data while integrating the API
  • Demonstrate value to stakeholders using controlled scenarios
Simulations are labeled in monitoring views. They do not move real money and should not be used as regulatory evidence by themselves.

​
How to run a simulation

1

Open Simulación

Sidebar → Simulación (/dashboard/simulation).
2

Pick a scenario

Choose a preset (low risk, high amount, suspicious device, etc.) or adjust amount, email, card BIN, and IP.
3

Run

Click Ejecutar. Clausum returns a risk score, decision, and session identifier.
4

Review results

Check Panel, Protección, and Monitor de transacciones — counts and charts update for your timezone.

​
What you receive

Each run returns:
FieldMeaning
decisionRecommended action: approve, review, challenge, or decline
risk_score0–100 score for prioritization
signal_detailsHuman-readable reasons (without exposing internal engine configuration)
session_idReference to find the row in monitoring tools
If persistence fails, the UI shows an actionable error (usually organization setup). Contact support if provisioning was never completed.

​
Best practices

  • Run at least one approve and one decline scenario after changing rules
  • Use distinct customer emails when testing velocity rules
  • Avoid double-clicking Ejecutar — each click creates a new assessment row (by design)
  • Pair simulation with a real sandbox API test before production cutover

​
Next steps

Protection workspace

Tune rules and blocklists.

Real-time assessment

Wire the same flow in your backend.