Softwr

Cybersecurity · head to head

Feedzai vs Medius

Feedzai logo

Feedzai

Cybersecurity

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

From
On request
Rated
-
Full reviewWebsite
Medius logo

Medius

Accounting

Accounts payable automation and supplier payments for mid-market finance teams, Marlin Equity owned

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.; Medius the sourcing, contract and procurement modules are considerably less developed than the AP core, so buying Medius as a full source-to-pay suite means accepting weak upstream tooling.
  • They diverge on capability: Feedzai covers Real-time scoring, Medius covers Invoice capture and coding.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Medius actually diverge.

Attributes where Feedzai and Medius differ
AttributeFeedzaiMedius
PlatformsWeb, LinuxWeb, iOS, Android
CategoryCybersecurityAccounting

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

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 Medius

  • Invoice capture and coding
  • Matching and exception handling
  • Fraud and anomaly detection
  • Supplier payments
  • Approval workflow
  • ERP integration

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

Medius

  • A mid-market finance team where most spend arrives as an invoice with no purchase order to match againstnot Feedzai
  • A group with several legal entities on different ERPs that wants one AP process across all of themnot Feedzai
  • Reducing invoice fraud exposure with automated detection of supplier bank detail changesnot Feedzai
  • Replacing a scanning bureau and a shared AP inbox with automated capture and exception-based reviewnot 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.

Medius

  • The sourcing, contract and procurement modules are considerably less developed than the AP core, so buying Medius as a full source-to-pay suite means accepting weak upstream tooling.
  • Pricing is quote-only and driven by invoice volume, so a business with many low-value invoices pays disproportionately relative to the spend being controlled.
  • Payments are billed on transaction volume separately from the AP subscription, which is easy to omit from a cost comparison against a licence-only AP tool.
  • Private equity ownership since 2017 has produced an acquisition-driven product line, so payments and adjacent capability come from bought-in technology rather than the original platform.
  • ERP integration depth varies sharply by system, and organisations on less common or heavily customised ERPs face integration work that lengthens the implementation.

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

Medius

On request
  • Medius AP Automation$undefined/year
    • Two packaged AP automation tiers
    • Priced by invoice volume and entity count
    • Sourcing, contracts and procurement modules sold 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.
Feedzai review

Choose Medius if

  • You need invoice capture and coding.
  • You work on Web, iOS, Android.
  • You also want matching and exception handling.
Medius review

Questions people ask

Is Feedzai or Medius better?
Neither clearly leads. Feedzai starts at On request and Medius at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or Medius?
Feedzai starts at On request and Medius at On request.
Does Feedzai or Medius run on more platforms?
Feedzai runs on Web, Linux. Medius 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 Medius is typically brought in for.
What can Feedzai do that Medius cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. Medius covers Invoice capture and coding, Matching and exception handling, Fraud and anomaly detection, Supplier payments.

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.

Medius: Is Medius a procurement suite or an AP tool?

Primarily an AP automation platform with procurement modules attached. If sourcing is your main requirement, look elsewhere.

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.

Medius: Who owns Medius?

Marlin Equity Partners, which acquired it in 2017 and has funded several bolt-on acquisitions since.

Feedzai: How fast are decisions?

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

Medius: How is it priced?

By quote, driven by invoice volume and entity count, with payments billed separately on transaction volume.

Medius: Does it replace our ERP?

No. It sits alongside the ERP and posts approved invoices into it.

Share

Related pages

More on Feedzai

More on Medius

Keep looking

Other head to heads