Softwr

APIs · head to head

Tribe Payments vs TrueLayer

Tribe Payments logo

Tribe Payments

APIs

Combined issuer and acquirer processing platform for fintechs, banks and acquirers

From
On request
Rated
-
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
-

The short version

  • Each has a real cost: Tribe Payments running both issuing and acquiring through one vendor concentrates operational risk, since a platform fault affects both sides of a client's card business at once rather than just one.; 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: Tribe Payments covers ISAAC core platform, TrueLayer covers Pay by bank.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Tribe Payments and TrueLayer actually diverge.

Attributes where Tribe Payments and TrueLayer differ
AttributeTribe PaymentsTrueLayer
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 Tribe Payments

  • ISAAC core platform
  • Issuer processing
  • Acquirer processing
  • Multi-scheme connectivity
  • Open banking module
  • 3D Secure and fraud tooling

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.

Tribe Payments

  • A bank or fintech wanting to run both card issuing and merchant acquiring on one processing platformnot TrueLayer
  • A payment facilitator consolidating separate issuing and acquiring vendor relationships into one contractnot TrueLayer
  • A company needing multi-scheme processing across Visa, Mastercard and regional networks like UnionPaynot TrueLayer
  • An Asia-Pacific expansion where Tribe's Singapore office provides regional supportnot TrueLayer

TrueLayer

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

Where each one falls short

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

Tribe Payments

  • Running both issuing and acquiring through one vendor concentrates operational risk, since a platform fault affects both sides of a client's card business at once rather than just one.
  • Pricing for either the issuing or acquiring modules is not published, so budgeting requires a sales conversation.
  • With roughly 60-plus customers, it is smaller scale than Visa or Mastercard-owned processing infrastructure, which is a factor for a client prioritising vendor size and track record.
  • Its client base and support depth are concentrated in the UK and continental Europe, and the Asia-Pacific presence via Singapore is comparatively newer and less proven.
  • As with any combined issuing and acquiring platform, a client that only needs one side still evaluates and pays for a vendor built around doing both, which may not be the most specialised option available.

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

Tribe Payments

On request
  • Tribe Payments$undefined/year
    • Pricing not published for issuing or acquiring modules
    • Custom quote required via sales

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 Tribe Payments if

  • You need isaac core platform.
  • You work on Web, API.
  • You also want issuer processing.

Choose TrueLayer if

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

Questions people ask

Is Tribe Payments or TrueLayer better?
Neither clearly leads. Tribe Payments 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, Tribe Payments or TrueLayer?
Tribe Payments starts at On request and TrueLayer at On request.
Does Tribe Payments or TrueLayer run on more platforms?
Tribe Payments runs on Web, API. TrueLayer runs on Web, iOS, Android.
What is Tribe Payments best used for?
Tribe Payments is most often used for a bank or fintech wanting to run both card issuing and merchant acquiring on one processing platform, a payment facilitator consolidating separate issuing and acquiring vendor relationships into one contract, a company needing multi-scheme processing across visa, mastercard and regional networks like unionpay, an asia-pacific expansion where tribe's singapore office provides regional support. Of those, a bank or fintech wanting to run both card issuing and merchant acquiring on one processing platform and a payment facilitator consolidating separate issuing and acquiring vendor relationships into one contract are not what TrueLayer is typically brought in for.
What can Tribe Payments do that TrueLayer cannot?
Tribe Payments covers ISAAC core platform, Issuer processing, Acquirer processing, Multi-scheme connectivity. TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information.

Answered from the vendors’ own pages

Tribe Payments: Does Tribe do both issuing and acquiring?

Yes, its ISAAC platform supports both, built for issuing in 2019 and acquiring from 2020.

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.

Tribe Payments: How many card schemes does it support?

Visa, Mastercard, Amex, Discover, JCB and UnionPay.

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.

Tribe Payments: Where is its customer base concentrated?

The UK and continental Europe, with a newer Singapore office serving Asia-Pacific.

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

Other head to heads