Softwr

APIs · head to head

Increase vs TrueLayer

Increase logo

Increase

APIs

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

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: 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.; 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: Increase covers ACH origination and receipt, TrueLayer covers Pay by bank.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Increase and TrueLayer actually diverge.

Attributes where Increase and TrueLayer differ
AttributeIncreaseTrueLayer
PlatformsAPI, WebWeb, 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 Increase

  • ACH origination and receipt
  • Domestic wires
  • Real-time payments
  • Bank accounts
  • Cards
  • Cheques
  • Sandbox and simulations
  • Audit and reconciliation data

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

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

TrueLayer

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

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

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

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

  • You need ach origination and receipt.
  • You work on API, Web.
  • You also want domestic wires.
Increase 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 Increase or TrueLayer better?
Neither clearly leads. Increase 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, Increase or TrueLayer?
Increase starts at On request and TrueLayer at On request.
Does Increase or TrueLayer run on more platforms?
Increase runs on API, Web. TrueLayer runs on Web, iOS, Android.
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 TrueLayer is typically brought in for.
What can Increase do that TrueLayer cannot?
Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts. TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information.

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.

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.

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.

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.

Increase: Is it international?

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

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.

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.

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 Increase

More on TrueLayer

Keep looking

Other head to heads