Softwr

APIs · head to head

Tribe Payments vs Trustly

Tribe Payments logo

Tribe Payments

APIs

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

From
On request
Rated
-
Trustly logo

Trustly

APIs

Pay-by-bank payments network, majority-owned by private equity firm Nordic Capital

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.; Trustly it is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
  • They diverge on capability: Tribe Payments covers ISAAC core platform, Trustly covers Pay by bank checkout.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Tribe Payments and Trustly differ
AttributeTribe PaymentsTrustly

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web, API), 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 Trustly

  • Pay by bank checkout
  • Instant refunds
  • Verified payouts
  • Multi-market bank connectivity
  • Merchant dashboard and reconciliation
  • Fraud and risk tooling

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 Trustly
  • A payment facilitator consolidating separate issuing and acquiring vendor relationships into one contractnot Trustly
  • A company needing multi-scheme processing across Visa, Mastercard and regional networks like UnionPaynot Trustly
  • An Asia-Pacific expansion where Tribe's Singapore office provides regional supportnot Trustly

Trustly

  • An e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptancenot Tribe Payments
  • A gaming or gambling operator needing verified, instant payouts to players' bank accountsnot Tribe Payments
  • A merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delaysnot Tribe Payments
  • A business in a market with strong open banking adoption wanting pay-by-bank as a checkout optionnot 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.

Trustly

  • It is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
  • Consumer familiarity with paying by bank transfer still lags card payments in most markets, so merchants typically see it used as a secondary option rather than a full card replacement.
  • The 1.15 to 3.15% merchant fee range is not a single published rate, so a merchant cannot know its actual cost without a sales negotiation.
  • As with all open banking-dependent payment methods, reliability depends on the consistency of the underlying banks' own APIs, which Trustly does not control.
  • Its verified payout functionality is heavily used in gaming and gambling, a sector with additional regulatory scrutiny, which is worth factoring in when evaluating vendor risk exposure by association.

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

Trustly

On request
  • Trustly$undefined/month
    • Typical merchant cost of 1.15% to 3.15% depending on volume and market
    • Exact rate negotiated per merchant, not published as a flat card

Which should you pick?

Choose Tribe Payments if

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

Choose Trustly if

  • You need pay by bank checkout.
  • You work on Web, API.
  • You also want instant refunds.

Questions people ask

Is Tribe Payments or Trustly better?
Neither clearly leads. Tribe Payments starts at On request and Trustly at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Tribe Payments or Trustly?
Tribe Payments starts at On request and Trustly at On request.
Does Tribe Payments or Trustly run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
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 Trustly is typically brought in for.
What can Tribe Payments do that Trustly cannot?
Tribe Payments covers ISAAC core platform, Issuer processing, Acquirer processing, Multi-scheme connectivity. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity.

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.

Trustly: Who owns Trustly?

Nordic Capital, a private equity firm, holds a 51.1% majority stake; Alfven & Didrikson and BlackRock hold smaller stakes.

Tribe Payments: How many card schemes does it support?

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

Trustly: Is Trustly going public?

It has discussed an IPO but as of its most recent comments said one remained at least a year away.

Tribe Payments: Where is its customer base concentrated?

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

Trustly: What does it typically cost a merchant?

Roughly 1.15% to 3.15% of transaction value depending on volume and market, negotiated per merchant.

Share

Related pages

Other head to heads