Softwr

APIs · head to head

Increase vs Salt Edge

Increase logo

Increase

APIs

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

From
On request
Rated
-
Full reviewWebsite
Salt Edge logo

Salt Edge

APIs

Independent open banking aggregator covering Europe by PSD2 API and other markets by direct connection

From
On request
Rated
-
Full reviewWebsite

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.; Salt Edge coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
  • They diverge on capability: Increase covers ACH origination and receipt, Salt Edge covers Account information.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Increase and Salt Edge actually diverge.

Attributes where Increase and Salt Edge differ
AttributeIncreaseSalt Edge
PlatformsAPI, WebWeb, API

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

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 Salt Edge

  • Account information
  • Payment initiation
  • Wide country coverage
  • Open Banking Gateway
  • Categorisation and enrichment
  • Consent management
  • Partner and white label
  • Sandbox

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 Salt Edge
  • A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Salt Edge
  • A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Salt Edge
  • An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Salt Edge

Salt Edge

  • A lender operating across several European and non-EU markets that needs one aggregation contract rather than a different provider per countrynot Increase
  • A fintech that wants an aggregator not owned by a card network because its use case competes with card productsnot Increase
  • An accounting or treasury product that needs bank feeds in markets the large aggregators do not servenot Increase
  • A bank that must publish PSD2-compliant APIs and would rather buy the compliance layer than build itnot 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.

Salt Edge

  • Coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
  • Pricing is not published and is usage-based, so two providers cannot be compared without running both sales processes, and cost grows with the connected user base rather than with revenue.
  • Support and engineering are distributed across Eastern Europe and Canada, and buyers in other time zones report slower turnaround on connection-specific breakages than they get from a domestic provider.
  • PSD2 consent rules require customers to reauthenticate periodically, and Salt Edge cannot change that, so any product depending on continuous data must design for consent expiry and the drop-off it causes.
  • United States coverage is weaker than Plaid or Mastercard Open Banking, so a company with meaningful US volume ends up running two aggregators and normalising between them.

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

Salt Edge

On request
  • Salt Edge Open Banking API$undefined/year
    • Account information and payment initiation
    • Coverage across 50 plus countries
    • Consent management and enrichment

Which should you pick?

Choose Increase if

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

Choose Salt Edge if

  • You need account information.
  • You work on Web, API.
  • You also want payment initiation.
Salt Edge review

Questions people ask

Is Increase or Salt Edge better?
Neither clearly leads. Increase starts at On request and Salt Edge at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Increase or Salt Edge?
Increase starts at On request and Salt Edge at On request.
Does Increase or Salt Edge run on more platforms?
Increase runs on API, Web. Salt Edge runs on Web, API.
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 Salt Edge is typically brought in for.
What can Increase do that Salt Edge cannot?
Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts. Salt Edge covers Account information, Payment initiation, Wide country coverage, Open Banking Gateway.

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.

Salt Edge: Who owns Salt Edge?

It is independently owned, unlike Tink (Visa), Finicity (Mastercard) or Yodlee (Envestnet), which matters if your use case competes with the owner.

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.

Salt Edge: Is all coverage direct bank API?

No. Inside PSD2 markets connections use regulated APIs; elsewhere coverage relies on direct connections whose reliability depends on the bank not changing its systems. Ask for a per-institution answer.

Increase: Is it international?

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

Salt Edge: Does it do payments as well as data?

Yes, payment initiation is supported in European markets where PSD2 applies.

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.

Salt Edge: What does it cost?

Not published. Pricing is usage-based and quoted, though the sandbox is free.

Share

Related pages

More on Increase

More on Salt Edge

Keep looking

Other head to heads