APIs · head to head
TrueLayer vs Weavr

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

Weavr
APIs
Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence
- From
- On request
- Rated
- -
The short version
- 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.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
- They diverge on capability: TrueLayer covers Pay by bank, Weavr covers Plug-and-play products.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which TrueLayer and Weavr actually diverge.
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 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 Weavr
- Plug-and-play products
- Regulated cover
- Card issuing
- Multi-currency accounts
- Identity and onboarding
- Data insights
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 Weavr
- A trading or crypto platform funding accounts instantly by bank transfer where card deposits carry chargeback risknot Weavr
- A marketplace paying sellers out to verified bank accounts with name checking to reduce misdirected paymentsnot Weavr
- A lender verifying income and affordability from bank transaction data rather than uploaded statementsnot Weavr
Weavr
- A project management SaaS adding expense cards without hiring a compliance officernot TrueLayer
- A marketplace paying out sellers from accounts held inside its own productnot TrueLayer
- A procurement platform issuing virtual cards against approved purchase ordersnot TrueLayer
- A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot 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.
Weavr
- Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
- Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
- It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
- Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
- European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.
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
Weavr
On request- Weavr embedded finance$undefined/year
- Platform subscription plus per-account and per-card fees
- Interchange share negotiated as part of the commercial terms
- Monthly minimums apply to card programmes
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 Weavr if
- You need plug-and-play products.
- You work on Web, REST API.
- You also want regulated cover.
Questions people ask
- Is TrueLayer or Weavr better?
- Neither clearly leads. TrueLayer starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, TrueLayer or Weavr?
- TrueLayer starts at On request and Weavr at On request.
- Does TrueLayer or Weavr run on more platforms?
- TrueLayer runs on Web, iOS, Android. Weavr runs on Web, REST API.
- 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 Weavr is typically brought in for.
- What can TrueLayer do that Weavr cannot?
- TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.
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.
Weavr: Do I need my own financial licence?
No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.
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.
Weavr: How is it different from a banking-as-a-service API?
It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.
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.
Weavr: How does Weavr make money?
Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.
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.
Related pages
Other head to heads
- TrueLayer vs Volt
- TrueLayer vs Tink
- TrueLayer vs Salt Edge
- TrueLayer vs Token.io
- TrueLayer vs Enable Banking
- TrueLayer vs Ozone API
- TrueLayer vs Brite Payments
- TrueLayer vs Neonomics
- TrueLayer vs Zimpler
- TrueLayer vs Bud Financial
- TrueLayer vs Trustly
- TrueLayer vs Yapily
- TrueLayer vs Tuum
- TrueLayer vs Unit
- TrueLayer vs Vodeno
- TrueLayer vs Apollo GraphQL
- TrueLayer vs Backendless
- TrueLayer vs Griffin
- TrueLayer vs Enfuce
- TrueLayer vs Synctera
- TrueLayer vs Swan
- TrueLayer vs Solaris
- TrueLayer vs Thredd
- TrueLayer vs Treasury Prime
- TrueLayer vs Fintech Farm
- TrueLayer vs Highnote
- TrueLayer vs Lithic
- TrueLayer vs Fintecture
- TrueLayer vs Formance
- TrueLayer vs GraphQL Apollo
- TrueLayer vs GraphQL Playground
- TrueLayer vs Gravitee
- TrueLayer vs Hoppscotch
- Weavr vs Volt
- Weavr vs Tink
- Weavr vs Salt Edge
- Weavr vs Token.io
- Weavr vs Enable Banking
- Weavr vs Ozone API
- Weavr vs Brite Payments
- Weavr vs Neonomics
- Weavr vs Zimpler
- Weavr vs Bud Financial
- Weavr vs Trustly
- Weavr vs Yapily
- Weavr vs Tuum
- Weavr vs Unit
- Weavr vs Vodeno
- Weavr vs Apollo GraphQL
- Weavr vs Backendless
- Weavr vs Griffin
- Weavr vs Enfuce
- Weavr vs Synctera
- Weavr vs Swan
- Weavr vs Solaris
- Weavr vs Thredd
- Weavr vs Treasury Prime
- Weavr vs Fintech Farm
- Weavr vs Highnote
- Weavr vs Lithic
- Weavr vs Fintecture
- Weavr vs Formance
- Weavr vs GraphQL Apollo
- Weavr vs GraphQL Playground
- Weavr vs Gravitee
- Weavr vs Hoppscotch
