Your risk policy,
written as rules.
Build no-code risk rules across 50+ transaction data points. Auto-approve, queue or block based on your thresholds - with full audit trail.
Risk policy as configuration, not code
Risk requirements change. New verticals, new geographies, new fraud patterns. The Risk Rules Engine lets your risk team change policy without waiting for a release cycle.
50+ data points
Your risk policy expressed as rules rather than as institutional memory. Velocity, amount, method, card, geography and list membership combine into conditions that apply automatically and identically every time.
No-code rules
Allow or block transactions based on the country in which the customer's card was issued (BIN-country) or the country the request is coming from (IP-country) - independently configurable.
Auto-actions
Cap transactions per merchant, per customer or per card over rolling time windows - daily, weekly, monthly. Block, queue or alert on breach.
Decline-pattern rules
React to issuer-decline patterns: when a card declines with a specific reason code, define what happens next - retry, block, alert, queue for review.
Refund and credit limits
Limit a merchant to a predefined amount of refunds or credit transactions per period to mitigate the risk of refund-based fraud.
How rules run
- Define
Build rules in the admin console using the rules editor. Choose triggers, conditions and actions - no code required.
- Apply
Rules run on every transaction. Auto-approve, queue for manual review, or block based on the action you defined.
- Audit
Every rule decision is logged with the data points that triggered it. Your compliance team has the audit trail it needs.
Frequently asked questions
Who can edit risk rules?
Rule editing is a permission, so it sits with the people responsible for risk rather than with anyone who can reach the console. Changes are attributed, which matters when you need to know why a rule looks different from last month.
Can different merchants have different risk rules?
Yes. Rules are configurable per merchant, per vertical, per product. Defaults can be overridden for specific merchants.
How fast does a rule change take effect?
Immediately. A rule applies from the next transaction, with no deployment and no waiting for a window, which is what makes it usable when something is going wrong right now.
Can rules trigger external actions?
Yes. Rules can trigger KYC re-verification, alerts to your team via Slack/email/webhook, or temporary merchant suspension.
How do I test a new rule before going live?
The engine supports a 'shadow' mode - apply the rule but don't enforce the action. You can see what would have happened before flipping enforcement on.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.