Softwr

APIs · head to head

Salt Edge vs TrueLayer

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
TrueLayer logo

TrueLayer

APIs

Open banking payments and data across the UK and Europe, with the largest share of UK variable recurring payments

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; TrueLayer variable recurring payments, the strongest reason to choose TrueLayer, is a UK construct, and European businesses expecting the same capability in their market will not get it on the same timetable.
  • They diverge on capability: Salt Edge covers Payment initiation, TrueLayer covers Pay by bank.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Salt Edge and TrueLayer differ
AttributeSalt EdgeTrueLayer
PlatformsWeb, APIWeb, iOS, Android

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

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

Only in TrueLayer

  • Pay by bank
  • Variable recurring payments
  • Payouts and refunds
  • Account name verification
  • Signup and KYC support
  • Multi-country coverage
  • Hosted payment page

Both cover

  • Account information

What people use each for

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

Salt Edge

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

TrueLayer

  • A UK subscription or top-up business that wants card-like recurring collection over bank rails using variable recurring paymentsnot Salt Edge
  • A trading or crypto platform funding accounts instantly by bank transfer where card deposits carry chargeback risknot Salt Edge
  • A marketplace paying sellers out to verified bank accounts with name checking to reduce misdirected paymentsnot Salt Edge
  • A lender verifying income and affordability from bank transaction data rather than uploaded statementsnot Salt Edge

Where each one falls short

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

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.

TrueLayer

  • Variable recurring payments, the strongest reason to choose TrueLayer, is a UK construct, and European businesses expecting the same capability in their market will not get it on the same timetable.
  • Payment conversion varies substantially by bank, and a bank with a slow or broken authentication journey drags results down regardless of vendor, so aggregate coverage numbers say little about your actual mix.
  • Pay by bank has no chargeback mechanism, which merchants like until a customer disputes a purchase and finds no scheme protection, making it a poor fit for categories where buyers expect card style recourse.
  • Pricing is unpublished and varies by market and product, so multi-country merchants cannot model cost without a full sales engagement and often find rates differ significantly between countries.
  • Open banking authentication requires the customer to leave the checkout and authorise in their banking app, and that redirect remains the largest source of drop-off compared with a stored card.

Pricing, plan by plan

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

TrueLayer

On request
  • TrueLayer Payments and Data$undefined/year
    • Per-payment fees quoted by volume, market and product
    • Separate commercial terms for payment initiation, VRP and account information
    • Platform and minimum commitment terms negotiated per contract

Which should you pick?

Choose Salt Edge if

  • You need payment initiation.
  • You work on Web, API.
  • You also want wide country coverage.
Salt Edge review

Choose TrueLayer if

  • You need pay by bank.
  • You work on Web, iOS, Android.
  • You also want variable recurring payments.
TrueLayer review

Questions people ask

Is Salt Edge or TrueLayer better?
Neither clearly leads. Salt Edge starts at On request and TrueLayer at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Salt Edge or TrueLayer?
Salt Edge starts at On request and TrueLayer at On request.
Does Salt Edge or TrueLayer run on more platforms?
Salt Edge runs on Web, API. TrueLayer runs on Web, iOS, Android.
What is Salt Edge best used for?
Salt Edge is most often used for a lender operating across several european and non-eu markets that needs one aggregation contract rather than a different provider per country, a fintech that wants an aggregator not owned by a card network because its use case competes with card products, an accounting or treasury product that needs bank feeds in markets the large aggregators do not serve, a bank that must publish psd2-compliant apis and would rather buy the compliance layer than build it. Of those, a lender operating across several european and non-eu markets that needs one aggregation contract rather than a different provider per country and a fintech that wants an aggregator not owned by a card network because its use case competes with card products are not what TrueLayer is typically brought in for.
What can Salt Edge do that TrueLayer cannot?
Salt Edge covers Payment initiation, Wide country coverage, Open Banking Gateway, Categorisation and enrichment. TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account name verification. Both handle Account information.

Answered from the vendors’ own pages

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.

TrueLayer: Is VRP available outside the UK?

No. Variable recurring payments are a UK capability. EU adoption is on a slower path, with UK commercial VRP expanding into ecommerce during 2026.

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.

TrueLayer: What does TrueLayer cost?

Not published. Per-payment fees are quoted by volume, market and product, usually with a platform component and a minimum commitment.

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

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

TrueLayer: Are there chargebacks on pay by bank?

No. Bank transfers have no card scheme chargeback mechanism, which removes that cost but also removes buyer recourse, so it suits some categories and not others.

Salt Edge: What does it cost?

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

TrueLayer: Which countries are covered?

The UK plus a substantial set of European markets under PSD2, though bank-level coverage and conversion vary by country and should be checked for your specific mix.

Share

Related pages

More on Salt Edge

More on TrueLayer

Keep looking

Other head to heads