Softwr

APIs · head to head

Tribe Payments vs Tuum

Tribe Payments logo

Tribe Payments

APIs

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

From
On request
Rated
-
Full reviewWebsite
Tuum logo

Tuum

APIs

Modular core banking platform from Estonia, formerly branded Modularbank

From
On request
Rated
-
Full reviewWebsite

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.; Tuum it is a smaller, younger company than Mambu, so it has fewer live reference deployments and a shorter track record to evaluate risk against.
  • They diverge on capability: Tribe Payments covers ISAAC core platform, Tuum covers Modular product structure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Tribe Payments and Tuum differ
AttributeTribe PaymentsTuum

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 Tuum

  • Modular product structure
  • Low-code integration middleware
  • Cloud-agnostic deployment
  • Multi-currency real-time accounts
  • Cards and lending modules
  • Faster migration timeline

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

Tuum

  • A bank wanting to migrate specific banking products to the cloud within months rather than replacing its entire core at oncenot Tribe Payments
  • A fintech in the DACH region or Middle East wanting a European core banking vendor with regional expansion focusnot Tribe Payments
  • An institution wanting low-code middleware to connect new modules to an existing legacy core rather than a full rebuildnot Tribe Payments
  • A company researching "Modularbank" that needs to confirm it is the same company now branded Tuumnot 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.

Tuum

  • It is a smaller, younger company than Mambu, so it has fewer live reference deployments and a shorter track record to evaluate risk against.
  • The 2022-era rebrand from Modularbank to Tuum means older funding records, case studies and press coverage appear under a different name, complicating due diligence for anyone unaware of the change.
  • Pricing is entirely unpublished, requiring a sales conversation to budget against competing composable core vendors.
  • Its geographic expansion into DACH and the Middle East is comparatively recent, so support depth and local regulatory expertise in those markets are less proven than in its home Baltic and Nordic base.
  • As with any core banking platform, choosing Tuum is a multi-year infrastructure commitment; switching cores after implementation is a major undertaking regardless of how modular the initial adoption was.

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

Tuum

On request
  • Tuum$undefined/year
    • Subscription and module-based pricing, not published
    • Custom quote required via sales

Which should you pick?

Choose Tribe Payments if

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

Choose Tuum if

  • You need modular product structure.
  • You work on Web, API.
  • You also want low-code integration middleware.
Tuum review

Questions people ask

Is Tribe Payments or Tuum better?
Neither clearly leads. Tribe Payments starts at On request and Tuum at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Tribe Payments or Tuum?
Tribe Payments starts at On request and Tuum at On request.
Does Tribe Payments or Tuum 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 Tuum is typically brought in for.
What can Tribe Payments do that Tuum cannot?
Tribe Payments covers ISAAC core platform, Issuer processing, Acquirer processing, Multi-scheme connectivity. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.

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.

Tuum: Is Tuum the same company as Modularbank?

Yes, Modularbank rebranded to Tuum; it is the same company and platform.

Tribe Payments: How many card schemes does it support?

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

Tuum: Where is it strongest geographically?

Its base is Estonia and the Nordic and Baltic region, with newer expansion into DACH and the Middle East.

Tribe Payments: Where is its customer base concentrated?

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

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Share

Related pages

More on Tribe Payments

More on Tuum

Keep looking

Other head to heads