Your rules decide,
and say why.
Send the transaction in one call; the engine runs the flow you published and returns the decision with the rule it came from. It works with your own payment stack too.
Decision
Reasons
- velocity.card_24h > 5
- cardCountry ≠ country
Flow: card payment · version 12
From payments
to compliance.
From card payment fraud to transaction monitoring, from case management to decision governance, one engine.
Decisions and flows
An explained decision from one endpoint; build your own flow with 39 node types, run your own code and use it with your own stack.
Learn morePayment fraud
3D Secure step-up decisions, card testing and merchant risk templates, behavioural signals and velocity rules for card payments.
Learn moreMonitoring and money mules
Velocity, fan-out, funnelling and pass-through patterns; ready templates mapped to regulatory texts and account risk screening.
Learn moreCases and governance
Automatic cases from review and block decisions, an analyst assistant, a draft-to-publish flow lifecycle and decision logs.
Learn moreMoney mule detection
Catch mule accounts by the shape of the money flow: fan-out, funnelling, pass-through, dormancy breaks and account risk screening.
Learn moreCompliance AI
Match explanations, case summaries and record-merge suggestions in the analyst console; it suggests, the analyst decides.
Learn moreData retention and legal hold
Fraud records are written under pseudonyms and archived, never deleted, when they expire; erasure cuts the link to the person and a legal hold freezes everything.
Learn more
Four decisions,
each with a reason.
Send the transaction and the engine returns one of four decisions; the response names the flow, node and rule that decided.
- Flow, node, rule and reason code come back with the decision.
- You don't need the Lunixi payment stack; your own gateway, POS or payment institution calls the same endpoint.
- If a flow errors, the decision never passes silently; it rises to at least review.
- allowContinue with the payment.
- force_3dStep up to 3D Secure; don't let it through without 3D.
- reviewSend to human review; don't capture, or hold.
- blockDecline; a case opens and the audit trail records it.
Rules mapped to
regulatory texts.
Adapt ready rule templates to your own thresholds and publish them; no need to write rules from scratch.
37
TCMB 3.1.x
Templates mapped to Turkish central bank monitoring typologies.
5
Account takeover
Templates for signs of account takeover.
5
Remittance and transfers
Templates for money transfer and remittance patterns.
6
UK APP / PSR
Rules for UK authorised push payment fraud.
Make fraud decisions
with your own rules.
Let's set up your flows and thresholds together with our team.
For enterprise inquiries: [email protected]