Softwr

Cybersecurity · head to head

Feedzai vs Trulioo

Feedzai logo

Feedzai

Cybersecurity

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

From
On request
Rated
-
Full reviewWebsite
Trulioo logo

Trulioo

Cybersecurity

Identity and business verification against national data sources in nearly 200 countries

From
On request
Rated
-
Full reviewWebsite

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.; Trulioo per-check rates vary widely by country and data source, so a blended average from the sales conversation misleads if your volume concentrates in expensive markets.
  • They diverge on capability: Feedzai covers Real-time scoring, Trulioo covers Person match.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Trulioo actually diverge.

Attributes where Feedzai and Trulioo differ
AttributeFeedzaiTrulioo
PlatformsWeb, LinuxWeb, API

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 Trulioo

  • Person match
  • Business verification
  • Watchlist screening
  • Document and biometric
  • Single API
  • Workflow orchestration

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 Trulioo
  • A card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for daysnot Trulioo
  • An acquirer needing per-merchant risk models rather than one portfolio-wide modelnot Trulioo
  • A bank required by its regulator to explain automated declines to customers, which rules out opaque scoringnot Trulioo

Trulioo

  • A payments firm onboarding across dozens of countries where building a data-source integration per market is impracticalnot Feedzai
  • A marketplace verifying business sellers and needing beneficial ownership rather than just a company numbernot Feedzai
  • A fintech wanting a cheap frictionless first check and reserving document scanning for the minority that fail itnot Feedzai
  • A bank expanding into a market where document upload completion rates are poor and registry matching works betternot 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.

Trulioo

  • Per-check rates vary widely by country and data source, so a blended average from the sales conversation misleads if your volume concentrates in expensive markets.
  • Coverage breadth is real but depth is uneven; a country on the map may be served by one thin source with low match rates, which you only discover in a live test.
  • You are charged per query including no-match results, so a market with poor source coverage burns budget producing nothing usable.
  • Because it aggregates third-party data, data residency and consent handling depend on the underlying provider terms, which complicates GDPR assessments in some jurisdictions.
  • Document and biometric capability is competent but not the strongest in the market, so buyers whose primary need is document fraud detection usually pair it with a specialist.

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

Trulioo

On request
  • Trulioo Platform$undefined/year
    • Priced per check with rates varying by country and data source
    • Person, business and watchlist checks charged separately
    • Volume commitment negotiated annually

Which should you pick?

Choose Feedzai if

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

Choose Trulioo if

  • You need person match.
  • You work on Web, API.
  • You also want business verification.
Trulioo review

Questions people ask

Is Feedzai or Trulioo better?
Neither clearly leads. Feedzai starts at On request and Trulioo at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or Trulioo?
Feedzai starts at On request and Trulioo at On request.
Does Feedzai or Trulioo run on more platforms?
Feedzai runs on Web, Linux. Trulioo runs on Web, API.
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 Trulioo is typically brought in for.
What can Feedzai do that Trulioo cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. Trulioo covers Person match, Business verification, Watchlist screening, Document and biometric.

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.

Trulioo: Does it need a document?

Not for the core product. Data-source matching uses name, address and date of birth, which is why completion rates are higher than document flows.

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.

Trulioo: Are unmatched queries billed?

Yes, in general you pay per query rather than per successful match. Negotiate this explicitly if you are entering markets with thin coverage.

Feedzai: How fast are decisions?

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

Trulioo: Can it verify companies as well as people?

Yes. Business verification including beneficial ownership is a distinct product line and a common reason to choose Trulioo over document-first vendors.

Share

Related pages

More on Feedzai

More on Trulioo

Keep looking

Other head to heads