Softwr

Cybersecurity · head to head

Feedzai vs Yoti

Feedzai logo

Feedzai

Cybersecurity

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

From
On request
Rated
-
Yoti logo

Yoti

Cybersecurity

Reusable digital identity, facial age estimation and identity verification

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.; Yoti age estimation returns a probabilistic range rather than a verified date of birth, so it only works with a safety buffer above the legal threshold and cannot prove an exact age.
  • They diverge on capability: Feedzai covers Real-time scoring, Yoti covers Facial age estimation.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Yoti actually diverge.

Attributes where Feedzai and Yoti differ
AttributeFeedzaiYoti
PlatformsWeb, LinuxWeb, iOS, Android, 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 Yoti

  • Facial age estimation
  • Reusable digital ID
  • Identity verification
  • UK right to work and rent
  • Digital ID for retail
  • Selective disclosure

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

Yoti

  • A social platform meeting UK Online Safety Act age assurance duties without collecting identity documents from teenagersnot Feedzai
  • A supermarket removing staff interventions at self-checkout for age-restricted purchasesnot Feedzai
  • A UK employer running digital right-to-work checks under the certified trust framework rather than inspecting passportsnot Feedzai
  • A gambling operator needing an age gate with high completion rates before the account funding stepnot 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.

Yoti

  • Age estimation returns a probabilistic range rather than a verified date of birth, so it only works with a safety buffer above the legal threshold and cannot prove an exact age.
  • Estimation accuracy varies by demographic and reported error margins widen at the age bands that matter most for eighteen-year thresholds, which pushes borderline users into a document fallback you still have to pay for.
  • Pricing is not published, so buyers cannot compare the cost of an estimation check against a document check without going through sales.
  • Regulatory acceptance of facial estimation differs by jurisdiction, so a method that satisfies Ofcom may not satisfy a regulator elsewhere and multi-market platforms need more than one approach.
  • The reusable digital identity app depends on consumer adoption, which is meaningful in the UK and thin elsewhere, limiting the reusability benefit outside its home market.

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

Yoti

On request
  • Yoti Age and Identity Services$undefined/year
    • Per-check pricing quoted by volume and method
    • Age estimation, document verification and digital ID priced differently
    • Right to work and right to rent checks quoted separately

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 Yoti if

  • You need facial age estimation.
  • You work on Web, iOS, Android, API.
  • You also want reusable digital id.

Questions people ask

Is Feedzai or Yoti better?
Neither clearly leads. Feedzai starts at On request and Yoti at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or Yoti?
Feedzai starts at On request and Yoti at On request.
Does Feedzai or Yoti run on more platforms?
Feedzai runs on Web, Linux. Yoti runs on Web, iOS, Android, 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 Yoti is typically brought in for.
What can Feedzai do that Yoti cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. Yoti covers Facial age estimation, Reusable digital ID, Identity verification, UK right to work and rent.

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.

Yoti: Does age estimation store my face?

The image is used to produce an estimate and then deleted rather than retained, which is the specific property that makes it usable for age assurance on minors.

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.

Yoti: Is it accepted for UK Online Safety Act compliance?

Facial age estimation is one of the methods regulators have accepted as highly effective age assurance. Confirm the current position with your own counsel for your content category.

Feedzai: How fast are decisions?

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

Yoti: Can it prove someone is exactly 21?

No. It gives a range. If you need a precise age you need a document or database check, which Yoti also sells.

Share

Related pages

Other head to heads