Softwr

APIs · head to head

Increase vs Medius

Increase logo

Increase

APIs

Direct banking API for ACH, wires, real-time payments, accounts and cards

From
On request
Rated
-
Medius logo

Medius

Accounting

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

From
On request
Rated
-

The short version

  • Each has a real cost: Increase the published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.; 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: Increase covers ACH origination and receipt, Medius covers Invoice capture and coding.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Increase and Medius actually diverge.

Attributes where Increase and Medius differ
AttributeIncreaseMedius
PlatformsAPI, WebWeb, iOS, Android
CategoryAPIsAccounting

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 Increase

  • ACH origination and receipt
  • Domestic wires
  • Real-time payments
  • Bank accounts
  • Cards
  • Cheques
  • Sandbox and simulations
  • Audit and reconciliation data

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.

Increase

  • A payroll or treasury product that needs to originate same-day ACH and wires under its own control rather than through a payment processornot Medius
  • A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Medius
  • A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Medius
  • An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Medius

Medius

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

Where each one falls short

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

Increase

  • The published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.
  • Free allowances are deliberately small at ten account numbers and five physical cards, so any programme issuing accounts or cards at volume moves to quoted pricing almost immediately.
  • Banking is provided through partner banks, so programme approval, compliance obligations and the ability to launch at all depend on a bank relationship you do not control, and post-Synapse bank risk appetite has tightened considerably.
  • The API deliberately exposes payment rail mechanics rather than smoothing them, which is correct engineering but means a team without payments expertise will build reconciliation and return handling wrongly and only discover it when funds go astray.
  • Coverage is United States only, so a company with international payout needs runs a second provider and reconciles two ledgers, and the single API argument disappears at the first cross border customer.

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

Increase

On request
  • Increase Platform$undefined/month
    • Monthly fee quoted by use case and not published
    • Next-day ACH origination listed at 0.50 US dollars per transaction
    • Same-day ACH origination listed at 2.00 per transaction

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

  • You need ach origination and receipt.
  • You work on API, Web.
  • You also want domestic wires.

Choose Medius if

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

Questions people ask

Is Increase or Medius better?
Neither clearly leads. Increase 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, Increase or Medius?
Increase starts at On request and Medius at On request.
Does Increase or Medius run on more platforms?
Increase runs on API, Web. Medius runs on Web, iOS, Android.
What is Increase best used for?
Increase is most often used for a payroll or treasury product that needs to originate same-day ach and wires under its own control rather than through a payment processor, a marketplace that must hold seller balances in ledgered accounts with real account and routing numbers, a fintech that wants fednow and rtp payouts so recipients are paid outside banking hours, an engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logic. Of those, a payroll or treasury product that needs to originate same-day ach and wires under its own control rather than through a payment processor and a marketplace that must hold seller balances in ledgered accounts with real account and routing numbers are not what Medius is typically brought in for.
What can Increase do that Medius cannot?
Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts. Medius covers Invoice capture and coding, Matching and exception handling, Fraud and anomaly detection, Supplier payments.

Answered from the vendors’ own pages

Increase: Does Increase publish its pricing?

Partly. Per transaction fees for ACH, wires, RTP, FedNow and cards are listed publicly. The monthly platform fee is not, and it is described only as varying by use case.

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.

Increase: Who holds the deposits?

Partner banks, not Increase itself. That relationship determines your programme approval, your compliance obligations and your risk if the bank changes appetite.

Medius: Who owns Medius?

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

Increase: Is it international?

No. Increase covers United States rails only, so cross border payouts require a second provider.

Medius: How is it priced?

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

Increase: How is it different from a middleware BaaS platform?

It exposes the rails rather than abstracting them, showing real return codes and settlement timing. That suits teams who understand payments and punishes teams who do not.

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