Softwr

Accounting · head to head

Medius vs Volt

Medius logo

Medius

Accounting

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

From
On request
Rated
-
Volt logo

Volt

APIs

Account-to-account pay by bank across Europe, the UK, Brazil and Australia

From
On request
Rated
-

The short version

  • Each has a real cost: 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.; Volt account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.
  • They diverge on capability: Medius covers Invoice capture and coding, Volt covers Pay by bank.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Medius and Volt actually diverge.

Attributes where Medius and Volt differ
AttributeMediusVolt
PlatformsWeb, iOS, AndroidWeb, REST API
CategoryAccountingAPIs

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 Medius

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

Only in Volt

  • Pay by bank
  • Circuit Breaker
  • Virtual IBANs
  • Payouts and refunds
  • Verify
  • Stablecoin checkout

What people use each for

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

Medius

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

Volt

  • A travel seller with high average order values paying percentage card fees it wants to replace with flat transfer feesnot Medius
  • An iGaming operator needing fast deposits and payouts where card acceptance is restrictednot Medius
  • A merchant with heavy card fraud that wants strongly authenticated irreversible paymentsnot Medius
  • A marketplace verifying seller bank accounts before paying outnot Medius

Where each one falls short

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

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.

Volt

  • Account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.
  • Refunds are outbound payments rather than reversals, which changes treasury handling and means a refund can fail for reasons a card refund never would.
  • Conversion is lower than a stored card because the shopper must complete a bank authentication journey, and drop-off varies significantly by bank.
  • Core pay by bank pricing is per transaction but refunds, payouts, virtual IBANs, Verify and fraud tooling are billed separately, so the real cost is a stack of line items.
  • Bank API availability and quality vary across markets, and an outage at a major bank removes a slice of your checkout with no fallback unless you keep cards live.

Pricing, plan by plan

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

Volt

On request
  • Volt pay by bank$undefined/year
    • Per successful transaction fee, quoted by volume and market
    • Separate charges for refunds, payouts, virtual IBANs and Verify
    • Circuit Breaker fraud tooling priced as an add-on

Which should you pick?

Choose Medius if

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

Choose Volt if

  • You need pay by bank.
  • You work on Web, REST API.
  • You also want circuit breaker.

Questions people ask

Is Medius or Volt better?
Neither clearly leads. Medius starts at On request and Volt at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Medius or Volt?
Medius starts at On request and Volt at On request.
Does Medius or Volt run on more platforms?
Medius runs on Web, iOS, Android. Volt runs on Web, REST API.
What is Medius best used for?
Medius is most often used for a mid-market finance team where most spend arrives as an invoice with no purchase order to match against, a group with several legal entities on different erps that wants one ap process across all of them, reducing invoice fraud exposure with automated detection of supplier bank detail changes, replacing a scanning bureau and a shared ap inbox with automated capture and exception-based review. Of those, a mid-market finance team where most spend arrives as an invoice with no purchase order to match against and a group with several legal entities on different erps that wants one ap process across all of them are not what Volt is typically brought in for.
What can Medius do that Volt cannot?
Medius covers Invoice capture and coding, Matching and exception handling, Fraud and anomaly detection, Supplier payments. Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds.

Answered from the vendors’ own pages

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.

Volt: Are there chargebacks?

No. Bank transfers are irrevocable, so disputes are handled commercially between merchant and customer, not through a card scheme.

Medius: Who owns Medius?

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

Volt: How do refunds work?

As a separate outbound payment initiated by the merchant, which Volt charges for separately from the inbound transaction.

Medius: How is it priced?

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

Volt: Which markets are covered?

Europe and the UK, plus Brazil and Australia, on a single API integration.

Medius: Does it replace our ERP?

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

Share

Related pages

Other head to heads