Fraud and Risk

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.

POST /api/v1/fraud/decisions/evaluate

Decision

allowforce_3dreviewblock

Reasons

  • velocity.card_24h > 5
  • cardCountry ≠ country

Flow: card payment · version 12

One call

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.
Decision API
  • 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.
Ready templates

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.

Transaction monitoring and templates

Make fraud decisions
with your own rules.

Let's set up your flows and thresholds together with our team.

For enterprise inquiries: [email protected]

Fraud and Risk — Explainable fraud decisions | Lunixi