Softwr

Cybersecurity · head to head

Feedzai vs Signicat

Feedzai logo

Feedzai

Cybersecurity

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

From
On request
Rated
-
Signicat logo

Signicat

Cybersecurity

European digital identity hub connecting national eID schemes

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.; Signicat national eID scheme fees are passed through on top of Signicat's own charge, so a single-country business almost always pays less by integrating with the scheme directly.
  • They diverge on capability: Feedzai covers Real-time scoring, Signicat covers eID scheme brokering.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Signicat actually diverge.

Attributes where Feedzai and Signicat differ
AttributeFeedzaiSignicat
PlatformsWeb, LinuxWeb, iOS, Android

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 Signicat

  • eID scheme brokering
  • Qualified electronic signatures
  • Document verification
  • AML screening
  • Authentication
  • Digital onboarding flows
  • eIDAS compliance

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

Signicat

  • A lender expanding from Norway into Sweden, Denmark and the Netherlands without four separate eID integrationsnot Feedzai
  • An insurer needing eIDAS qualified signatures on policy documents that will hold up in a European courtnot Feedzai
  • A bank that wants customers to onboard with their existing national bank ID rather than photographing a passportnot Feedzai
  • A public sector body needing cross-border recognition of notified eID schemes under eIDASnot 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.

Signicat

  • National eID scheme fees are passed through on top of Signicat's own charge, so a single-country business almost always pays less by integrating with the scheme directly.
  • Value is concentrated in Northern and Western Europe, and coverage in Southern and Eastern Europe is thinner, so a pan-European rollout still hits gaps requiring document fallback.
  • Pricing is per transaction and quoted, and because scheme rates vary by country the cost per onboarded customer differs materially between markets in ways that complicate unit economics.
  • Each eID scheme connection typically carries its own setup fee and approval process, so adding a country is a project with a lead time rather than a configuration change.
  • Availability is tied to the national schemes, meaning an outage at BankID or MitID stops your onboarding entirely and there is no vendor-side mitigation for it.

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

Signicat

On request
  • Signicat Platform$undefined/year
    • Priced per transaction with national scheme fees passed through
    • Signature and verification products licensed separately
    • Setup fee per eID scheme connected

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

  • You need eid scheme brokering.
  • You work on Web, iOS, Android.
  • You also want qualified electronic signatures.

Questions people ask

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

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.

Signicat: Is this an alternative to a document verification vendor?

Only where national eID exists. In markets with a mature bank ID scheme it is better; elsewhere you fall back to document checks, which Signicat also provides.

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.

Signicat: Do we still pay the eID schemes?

Yes. Scheme fees are passed through in addition to Signicat charges. Ask for the split when comparing to a direct integration.

Feedzai: How fast are decisions?

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

Signicat: Are signatures legally qualified?

Signicat supports eIDAS qualified electronic signatures, which carry the highest legal standing in the EU, as well as advanced signatures.

Share

Related pages

Other head to heads