Softwr

APIs · head to head

TrueLayer vs Zeplo

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

Zeplo

APIs

Message queue as a URL prefix, adding retries and delays to any HTTP request

From
Free
Rated
-

The short version

  • Only Zeplo 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.; Zeplo zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
  • They diverge on capability: TrueLayer covers Pay by bank, Zeplo covers URL prefix interface.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which TrueLayer and Zeplo actually diverge.

Attributes where TrueLayer and Zeplo differ
AttributeTrueLayerZeplo
Starting priceOn requestFree
Pricing modelquotePer month by request count
Free tierNoYes
PlatformsWeb, iOS, AndroidWeb, Cloud

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 Zeplo

  • URL prefix interface
  • Retries with backoff
  • Delayed delivery
  • Cron scheduling
  • Concurrency limits
  • Deduplication keys
  • Request logs
  • Team workspaces

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 Zeplo
  • A trading or crypto platform funding accounts instantly by bank transfer where card deposits carry chargeback risknot Zeplo
  • A marketplace paying sellers out to verified bank accounts with name checking to reduce misdirected paymentsnot Zeplo
  • A lender verifying income and affordability from bank transaction data rather than uploaded statementsnot Zeplo

Zeplo

  • A Vercel or Cloudflare Workers application that needs retried background jobs without deploying a separate always-on workernot TrueLayer
  • A team that wants a webhook receiver protected by a concurrency limit so a burst does not overwhelm a downstream APInot TrueLayer
  • A small product needing cron jobs against HTTP endpoints without adding a scheduler to its infrastructurenot TrueLayer
  • A developer adding idempotent retries to an unreliable third-party API call with a one-line URL changenot 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.

Zeplo

  • Zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
  • The free Developer tier includes only 500 requests a month and one team member, so it is a demonstration allowance rather than a usable free plan for anything real.
  • Overage on the Developer tier is 20 US dollars per 100,000 requests, two hundred times the marginal rate on the Company tier, so exceeding the free allowance without upgrading is expensive.
  • Team members cost 15 US dollars each beyond the plan allowance, which is an odd charge on an infrastructure product billed by request volume.
  • Log retention is 30 days on both published tiers, so anything requiring longer audit trails on job execution has to be logged separately.

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

Zeplo

Free
  • DeveloperFree
    • 500 requests a month included
    • $20 per additional 100,000 requests
    • 1 team member
  • Company$39/month
    • 1,000,000 requests a month included
    • $10 per additional million requests
    • Up to 3 team members
  • Enterprise$undefined/month
    • Volume discounts
    • Custom team size
    • Support with SLA

Which should you pick?

Choose TrueLayer if

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

Choose Zeplo if

  • You need url prefix interface.
  • You want to start without paying.
  • You work on Web, Cloud.
  • You also want retries with backoff.

Questions people ask

Is TrueLayer or Zeplo better?
Neither clearly leads. TrueLayer starts at On request and Zeplo at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, TrueLayer or Zeplo?
Zeplo has a free tier; the other does not. Paid plans start at On request for TrueLayer and Free for Zeplo.
Does TrueLayer or Zeplo run on more platforms?
TrueLayer runs on Web, iOS, Android. Zeplo runs on Web, Cloud.
Can I use Zeplo for free?
Yes. Zeplo 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 Zeplo is typically brought in for.
What can TrueLayer do that Zeplo cannot?
TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.

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.

Zeplo: How does Zeplo work?

You prefix your endpoint URL with zeplo.to and add query parameters for retries, delay, cron or concurrency. No SDK or broker is needed.

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.

Zeplo: What does it cost?

Free for 500 requests a month; 39 US dollars a month for a million requests, then 10 dollars per additional million.

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.

Zeplo: Is it suitable for critical jobs?

It is a small vendor in your execution path with no published SLA below Enterprise, so weigh that against the convenience.

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.

Zeplo: Does it work with serverless platforms?

Yes, that is its main use, covering Vercel, Cloudflare Workers, Netlify and similar environments that lack long-running workers.

Share

Related pages

Other head to heads