Softwr

APIs · head to head

TrueLayer vs Yapily

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

Yapily

APIs

Open banking API infrastructure for account data and pay-by-bank payments across Europe

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Yapily has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; Yapily production pricing itself is not published; only the resulting typical merchant transaction cost is publicly known, so the underlying platform fee still requires a sales conversation.
  • They diverge on capability: TrueLayer covers Pay by bank, Yapily covers Unified open banking API.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which TrueLayer and Yapily actually diverge.

Attributes where TrueLayer and Yapily differ
AttributeTrueLayerYapily
Starting priceOn requestFree
Pricing modelquoteFree sandbox, pay-as-you-go production
Free tierNoYes
PlatformsWeb, iOS, AndroidWeb, API

Identical on both: 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 TrueLayer

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

Only in Yapily

  • Unified open banking API
  • Account information access
  • Payment initiation
  • Free sandbox
  • Multi-country bank coverage
  • Webhooks and reconciliation tooling

What people use each for

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

TrueLayer

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

Yapily

  • A merchant wanting a lower-cost payment method alongside card acceptancenot TrueLayer
  • A lending or budgeting product needing bank account data for affordability checksnot TrueLayer
  • A business wanting one API instead of separate integrations to each bank's own open banking standardnot TrueLayer
  • A company prototyping open banking features for free in sandbox before committing budgetnot TrueLayer

Where each one falls short

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

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.

Yapily

  • Production pricing itself is not published; only the resulting typical merchant transaction cost is publicly known, so the underlying platform fee still requires a sales conversation.
  • Consumer adoption of pay-by-bank still lags card payments, so merchants offering it as a checkout option typically see it used as a secondary rather than primary payment method.
  • Coverage depends on the banks in each country maintaining reliable open banking APIs, and inconsistent bank-side reliability across markets is a known category-wide weakness, not unique to Yapily but not solved by it either.
  • As infrastructure for both account data and payments, a company only needing one of those two capabilities is still evaluating a broader platform than it may need.
  • Regulatory dependence on PSD2 and UK open banking rules means the underlying legal framework, not just Yapily's product, could shift and affect what is possible on the platform.

Pricing, plan by plan

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

Yapily

Free
  • SandboxFree
    • Free testing environment
    • UK and European bank connections for development
  • Production$undefined/month
    • Pay-as-you-go pricing, exact rates not published
    • Typical pay-by-bank cost of 0.1 to 0.5% or a flat 5 to 30 pence per transaction

Which should you pick?

Choose TrueLayer if

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

Choose Yapily if

  • You need unified open banking api.
  • You want to start without paying.
  • You work on Web, API.
  • You also want account information access.
Yapily review

Questions people ask

Is TrueLayer or Yapily better?
Neither clearly leads. TrueLayer starts at On request and Yapily at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, TrueLayer or Yapily?
Yapily has a free tier; the other does not. Paid plans start at On request for TrueLayer and Free for Yapily.
Does TrueLayer or Yapily run on more platforms?
TrueLayer runs on Web, iOS, Android. Yapily runs on Web, API.
Can I use Yapily for free?
Yes. Yapily has a free tier, so you can try it without paying. TrueLayer starts at On request.
What is TrueLayer best used for?
TrueLayer is most often used for a uk subscription or top-up business that wants card-like recurring collection over bank rails using variable recurring payments, a trading or crypto platform funding accounts instantly by bank transfer where card deposits carry chargeback risk, a marketplace paying sellers out to verified bank accounts with name checking to reduce misdirected payments, a lender verifying income and affordability from bank transaction data rather than uploaded statements. Of those, a uk subscription or top-up business that wants card-like recurring collection over bank rails using variable recurring payments and a trading or crypto platform funding accounts instantly by bank transfer where card deposits carry chargeback risk are not what Yapily is typically brought in for.
What can TrueLayer do that Yapily cannot?
TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information. Yapily covers Unified open banking API, Account information access, Payment initiation, Free sandbox.

Answered from the vendors’ own pages

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.

Yapily: Is there a free way to try it?

Yes, sandbox access is free for development and testing.

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.

Yapily: How much cheaper is pay-by-bank than card payments?

Typically 0.1 to 0.5% of transaction value, or a flat 5 to 30 pence, against 1.5 to 3.5% for card scheme fees.

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.

Yapily: Is production pricing published?

No, production access is pay-as-you-go but exact rates require a sales conversation.

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 TrueLayer

More on Yapily

Keep looking

Other head to heads