Softwr

Cybersecurity · head to head

Feedzai vs NICE Actimize

Feedzai logo

Feedzai

Cybersecurity

Real-time transaction fraud and financial crime detection for banks and payment processors

From
On request
Rated
-
NICE Actimize logo

NICE Actimize

Cybersecurity

Financial crime, risk and compliance suite for regulated institutions

From
On request
Rated
-

The short version

  • Each has a real cost: Feedzai pricing is per transaction with an annual minimum, so a bank with seasonal or growing volume commits to a floor it may not use and pays overage above the band.; NICE Actimize modules are licensed separately, so a bank that starts with AML and later needs fraud and surveillance faces three negotiations and a bill that compounds rather than a suite price.
  • They diverge on capability: Feedzai covers Real-time scoring, NICE Actimize covers Suspicious activity monitoring.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and NICE Actimize actually diverge.

Attributes where Feedzai and NICE Actimize differ
AttributeFeedzaiNICE Actimize
PlatformsWeb, LinuxWeb, Linux, Windows

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Cybersecurity).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Feedzai

  • Real-time scoring
  • Rule and model hybrid
  • Case manager
  • Behavioural biometrics
  • Model explainability
  • Deployment options

Only in NICE Actimize

  • Suspicious activity monitoring
  • Watchlist filtering
  • Customer due diligence
  • Payment fraud detection
  • Markets surveillance
  • Case management
  • X-Sight marketplace

What people use each for

The jobs each tool is most often brought in to do.

Feedzai

  • A bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossiblenot NICE Actimize
  • A card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for daysnot NICE Actimize
  • An acquirer needing per-merchant risk models rather than one portfolio-wide modelnot NICE Actimize
  • A bank required by its regulator to explain automated declines to customers, which rules out opaque scoringnot NICE Actimize

NICE Actimize

  • A bank under a regulatory consent order that needs a monitoring system with an audit trail examiners already recognisenot Feedzai
  • A broker dealer required to implement trade surveillance covering both orders and trader communicationsnot Feedzai
  • A regional bank outgrowing spreadsheet-based sanctions screening and needing documented model governancenot Feedzai
  • A payments firm needing real time fraud scoring on faster payments alongside batch AML monitoringnot Feedzai

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Feedzai

  • Pricing is per transaction with an annual minimum, so a bank with seasonal or growing volume commits to a floor it may not use and pays overage above the band.
  • It sits in the authorisation path, which makes every upgrade a change-controlled event with rollback plans, and the operational burden falls on the bank rather than the vendor.
  • Out of the box models need months of the customer own labelled fraud history before they beat the rules they replace, so the value case starts late.
  • AML and fraud are licensed as separate modules, so institutions expecting one platform fee find the transaction monitoring capability is a second line item.
  • The buyer profile is large institutions, so smaller banks and fintechs face minimums that make per-transaction economics unattractive below significant scale.

NICE Actimize

  • Modules are licensed separately, so a bank that starts with AML and later needs fraud and surveillance faces three negotiations and a bill that compounds rather than a suite price.
  • Tuning and model validation are consultant-heavy, and the services spend over a deployment often exceeds the first year licence cost.
  • The older on premises deployments carry batch-oriented architecture that makes true real time decisioning harder than in newer cloud native rivals.
  • Rule and model changes go through a controlled release process, so a bank reacting to a new fraud typology may wait weeks for a change that a modern platform would ship in days.
  • Because it is the incumbent at so many institutions, criminals have a good working understanding of what the standard rule sets detect, and undifferentiated out of the box configurations catch predictable behaviour.

Pricing, plan by plan

Feedzai

On request
  • Feedzai Financial Crime Platform$undefined/year
    • Priced by transaction volume with annual minimum commitment
    • Modules for fraud, AML and account opening licensed separately
    • Cloud, private cloud and on-premises deployment

NICE Actimize

On request
  • NICE Actimize$undefined/year
    • Licensed per module, not as one suite
    • Scaled by institution asset size or transaction volume
    • On premises or Actimize cloud deployment

Which should you pick?

Choose Feedzai if

  • You need real-time scoring.
  • You work on Web, Linux.
  • You also want rule and model hybrid.

Choose NICE Actimize if

  • You need suspicious activity monitoring.
  • You work on Web, Linux, Windows.
  • You also want watchlist filtering.

Questions people ask

Is Feedzai or NICE Actimize better?
Neither clearly leads. Feedzai starts at On request and NICE Actimize at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or NICE Actimize?
Feedzai starts at On request and NICE Actimize at On request.
Does Feedzai or NICE Actimize run on more platforms?
Feedzai runs on Web, Linux. NICE Actimize runs on Web, Linux, Windows.
What is Feedzai best used for?
Feedzai is most often used for a bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossible, a card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for days, an acquirer needing per-merchant risk models rather than one portfolio-wide model, a bank required by its regulator to explain automated declines to customers, which rules out opaque scoring. Of those, a bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossible and a card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for days are not what NICE Actimize is typically brought in for.
What can Feedzai do that NICE Actimize cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. NICE Actimize covers Suspicious activity monitoring, Watchlist filtering, Customer due diligence, Payment fraud detection.

Answered from the vendors’ own pages

Feedzai: Can Feedzai run on-premises?

Yes. On-premises and private cloud deployments are supported, which is why it appears in markets where transaction data cannot legally leave the country.

NICE Actimize: Is Actimize one product?

No. It is a family of separately licensed modules covering AML, fraud, due diligence and surveillance. You buy what you need and each has its own price.

Feedzai: Does it cover AML as well as fraud?

It does, but transaction monitoring is a separately licensed module. Assume two line items if you want both.

NICE Actimize: Can it run in the cloud?

Yes, Actimize offers cloud deployment, though a large share of the installed base still runs on premises for data residency reasons.

Feedzai: How fast are decisions?

Designed for the authorisation window, typically tens of milliseconds. This is the constraint that rules out batch scoring architectures.

NICE Actimize: Who owns it?

NICE Ltd, an Israeli company listed on Nasdaq. Actimize is its financial crime division.

Share

Related pages

Other head to heads