Softwr

APIs · head to head

i2c vs TrueLayer

i2c logo

i2c

APIs

Configurable card issuing and banking processing platform for banks and programme managers

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: i2c developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead.; 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: i2c covers Configurable product engine, TrueLayer covers Pay by bank.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which i2c and TrueLayer actually diverge.

Attributes where i2c and TrueLayer differ
Attributei2cTrueLayer
PlatformsWeb, REST 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 i2c

  • Configurable product engine
  • Credit and instalments
  • Multi-currency
  • Fraud and risk tooling
  • Digital banking front ends
  • Global scheme connectivity

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.

i2c

  • A bank wanting credit, debit and prepaid portfolios on one processor rather than threenot TrueLayer
  • An issuer in a market where local scheme and currency support rules out US-centric processorsnot TrueLayer
  • A programme manager launching instalment products without building a lending corenot TrueLayer
  • A credit union replacing an ageing processor without writing custom code for product rulesnot TrueLayer

TrueLayer

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

Where each one falls short

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

i2c

  • Developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead.
  • Implementations lean on i2c or partner professional services, so timelines and costs are set by a services queue rather than by your own engineering speed.
  • Pricing is per active card and per transaction with monthly minimums, none of it published, so comparing bids requires modelling your own portfolio carefully.
  • Configuration flexibility means product behaviour lives in platform settings rather than in your repository, which complicates version control, testing and audit trails.
  • As a private company with a broad global footprint, regional support depth is uneven, and a programme in a smaller market may get thinner service than a flagship account.

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

i2c

On request
  • i2c processing platform$undefined/year
    • Per-active-card and per-transaction processing fees
    • Minimum monthly commitments by programme
    • Implementation and configuration professional services

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

  • You need configurable product engine.
  • You work on Web, REST API.
  • You also want credit and instalments.
i2c 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 i2c or TrueLayer better?
Neither clearly leads. i2c 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, i2c or TrueLayer?
i2c starts at On request and TrueLayer at On request.
Does i2c or TrueLayer run on more platforms?
i2c runs on Web, REST API. TrueLayer runs on Web, iOS, Android.
What is i2c best used for?
i2c is most often used for a bank wanting credit, debit and prepaid portfolios on one processor rather than three, an issuer in a market where local scheme and currency support rules out us-centric processors, a programme manager launching instalment products without building a lending core, a credit union replacing an ageing processor without writing custom code for product rules. Of those, a bank wanting credit, debit and prepaid portfolios on one processor rather than three and an issuer in a market where local scheme and currency support rules out us-centric processors are not what TrueLayer is typically brought in for.
What can i2c do that TrueLayer cannot?
i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information.

Answered from the vendors’ own pages

i2c: Does i2c issue the cards itself?

No. It processes; issuance sits with a bank or licensed issuer, and in most markets you need that relationship separately.

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.

i2c: Can it handle revolving credit?

Yes. Credit, instalments and buy-now-pay-later sit on the same platform as debit and prepaid, which is unusual among modern processors.

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.

i2c: Is it self-serve?

No. Expect a configuration-led implementation with professional services rather than signing up and calling an API.

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.

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 i2c

More on TrueLayer

Keep looking

Other head to heads