Softwr

APIs · head to head

Rutter vs TrueLayer

Rutter logo

Rutter

APIs

One API across accounting, commerce, payments and advertising platforms

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: Rutter a unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.; 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: Rutter covers Accounting and ERP, TrueLayer covers Pay by bank.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Rutter and TrueLayer actually diverge.

Attributes where Rutter and TrueLayer differ
AttributeRutterTrueLayer
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 Rutter

  • Accounting and ERP
  • Commerce data
  • Payments data
  • Advertising data
  • Write operations
  • Passthrough requests
  • Observability tooling
  • Sandbox

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.

Rutter

  • A revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facilitynot TrueLayer
  • A spend management product that needs to push bills and journal entries back into whichever accounting system its customer runsnot TrueLayer
  • A B2B payments platform reconciling invoices across customers using four different ERPsnot TrueLayer
  • An insurance or benefits provider that needs verified business financials without asking the customer to upload PDFsnot TrueLayer

TrueLayer

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

Where each one falls short

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

Rutter

  • A unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.
  • Write operations into accounting systems are where these products break, because each system validates differently, and a rejected journal entry surfaces as a support ticket against you rather than against the ERP.
  • No pricing is published beyond a sandbox trial, so cost cannot be compared against alternatives without a sales process, and pricing tends to scale with connected accounts.
  • QuickBooks Desktop and other on-premises systems require a local connector or hosted agent, which introduces installation steps your customers must complete and support burden you inherit.
  • Sync freshness varies by platform and by customer authorisation state, so a product promising near real-time figures will find some connections update far less often than the marketing implies.

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

Rutter

On request
  • Starter$undefined/month
    • Thirty day sandbox trial
    • Test integrations with QuickBooks, Xero, FreshBooks and Zoho Books
    • Documentation and workflow guides
  • Full Access$undefined/year
    • Production access across all platforms
    • Includes NetSuite, QuickBooks Desktop and Sage Intacct
    • Write operations and passthrough

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

  • You need accounting and erp.
  • You work on Web, API.
  • You also want commerce data.
Rutter 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 Rutter or TrueLayer better?
Neither clearly leads. Rutter 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, Rutter or TrueLayer?
Rutter starts at On request and TrueLayer at On request.
Does Rutter or TrueLayer run on more platforms?
Rutter runs on Web, API. TrueLayer runs on Web, iOS, Android.
What is Rutter best used for?
Rutter is most often used for a revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facility, a spend management product that needs to push bills and journal entries back into whichever accounting system its customer runs, a b2b payments platform reconciling invoices across customers using four different erps, an insurance or benefits provider that needs verified business financials without asking the customer to upload pdfs. Of those, a revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facility and a spend management product that needs to push bills and journal entries back into whichever accounting system its customer runs are not what TrueLayer is typically brought in for.
What can Rutter do that TrueLayer cannot?
Rutter covers Accounting and ERP, Commerce data, Payments data, Advertising data. TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information.

Answered from the vendors’ own pages

Rutter: Does Rutter support QuickBooks Desktop?

Yes, which distinguishes it from unified APIs that only cover cloud accounting, and matters because many small businesses still run it.

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.

Rutter: Can Rutter write data back?

Yes. Invoices, bills and journal entries can be pushed into supported accounting systems, not only read.

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.

Rutter: Is there a free tier?

There is a thirty day sandbox trial with test data. Production access requires a paid plan with quoted pricing.

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.

Rutter: What if the unified model lacks a field I need?

Rutter supports passthrough requests to the underlying platform API, though using them reintroduces platform-specific code.

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 Rutter

More on TrueLayer

Keep looking

Other head to heads