MOD-FRD · Fraud & risk

Stop fraud before it costs you, not after.

Every sign-up, login, card payment and transfer is scored in real time against your rules and the signals of leading fraud engines. Suspicious activity is held, challenged or blocked, and lands in a case queue for your team.

  • 8connectors
  • 6platforms run it
  • +1your own, too
  1. 01 · The job

    Decisions in milliseconds, cases for people.

    The module combines device, behaviour and transaction signals into a risk score for each event, then applies your rules: allow, ask for a second factor, hold for review or block. Analysts work the cases in the backoffice, with the full history on one screen.

    • Real-time scoring of sign-ups, logins and payments
    • Velocity limits and spending rules
    • Device fingerprinting and account takeover signals
    • Step-up authentication on risky actions
    • Case management and analyst notes
    • Chargeback and dispute tracking
  2. 02 · The connectors

    Sardine, SEON, Sift, Feedzai.

    External fraud engines add their consortium data and models to your own rules. The module calls them in parallel, merges their signals into one decision, and keeps deciding on your rules if a provider is slow.

    Fraud scoring

    • Sardine
    • SEON
    • Sift
    • Feedzai
    • LexisNexis ThreatMetrix

    Device intelligence

    • Fingerprint

    Card payments

    • EMV 3-D Secure
    • Visa and Mastercard risk scores
  3. 03 · Your own

    Your rules, your models.

    Your risk team writes and tunes rules in the backoffice without waiting for a release. A model you trained yourself plugs in as one more signal, next to the external engines or instead of them.

    In-house, or a provider you already use
    • Rules edited in the backoffice
    • Your own scoring models
    • Thresholds per product and country

In production

Running in these platforms.

Questions

Asked about this module.

Do we need an external fraud provider to launch?

No. The module's own rules and limits cover the common patterns from day one, and an external engine can be added later, when your volumes justify it.

What happens if the fraud provider is down?

The decision falls back to your own rules within a set timeout, so customers are not blocked by an outage on someone else's side.

Same family

The whole library

Start your project

Tell us the idea. We'll show you the platform.

One call is enough to map your product to the modules that already exist.

  • Response in under one business day
  • NDA on request
  • No obligation
What are you building?