Softwr

APIs · head to head

i2c vs Tuum

i2c logo

i2c

APIs

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

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

Where they differ

Only the attributes on which i2c and Tuum actually diverge.

Attributes where i2c and Tuum differ
Attributei2cTuum
PlatformsWeb, REST APIWeb, API

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 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.

i2c

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

Tuum

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

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

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

Tuum

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

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 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 i2c or Tuum better?
Neither clearly leads. i2c 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, i2c or Tuum?
i2c starts at On request and Tuum at On request.
Does i2c or Tuum run on more platforms?
i2c runs on Web, REST API. Tuum runs on Web, API.
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 Tuum is typically brought in for.
What can i2c do that Tuum cannot?
i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.

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.

Tuum: Is Tuum the same company as Modularbank?

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

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.

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.

i2c: Is it self-serve?

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

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Share

Related pages

More on i2c

More on Tuum

Keep looking

Other head to heads