Softwr

APIs · head to head

Token.io vs Tuum

Token.io logo

Token.io

APIs

Account to account pay by bank infrastructure across the UK and Europe

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: Token.io account to account payments carry no chargeback scheme, so merchants gain cost savings but consumers lose the dispute protection cards provide, which limits adoption in general retail.; 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: Token.io covers Payment initiation, Tuum covers Modular product structure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Token.io and Tuum actually diverge.

Attributes where Token.io and Tuum differ
AttributeToken.ioTuum

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

  • Payment initiation
  • Variable recurring payments
  • Bank network coverage
  • giroAPI membership
  • Payouts and refunds
  • Data and account information
  • Hosted payment pages
  • Reconciliation reporting

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.

Token.io

  • A utility or telecom collecting high value bills where card interchange makes acceptance expensivenot Tuum
  • An investment or trading platform funding customer accounts without card chargeback exposurenot Tuum
  • A payment service provider adding pay by bank to its merchant proposition without building bank connectivitynot Tuum
  • A German merchant using giroAPI scheme access for recurring and future dated bank paymentsnot Tuum

Tuum

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

Where each one falls short

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

Token.io

  • Account to account payments carry no chargeback scheme, so merchants gain cost savings but consumers lose the dispute protection cards provide, which limits adoption in general retail.
  • Conversion depends on each bank's own authentication journey, and slow or broken bank redirects cost sales in ways the merchant cannot fix or even always diagnose.
  • Variable recurring payments beyond sweeping are still being rolled out unevenly across banks and markets, so a subscription use case may be supported at one bank and not another.
  • Token.io initiates payments rather than acting as acquirer of record, so merchants still need settlement, safeguarding and reconciliation arrangements elsewhere.
  • Coverage and feature parity vary by country, so a pan European rollout means different capabilities and different bank behaviour in each market rather than one uniform product.

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

Token.io

On request
  • Token.io platform$undefined/year
    • Quoted per customer, typically per initiated payment
    • Volume tiers and monthly minimums are common
    • No interchange, so unit cost is usually well below card acceptance

Tuum

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

Which should you pick?

Choose Token.io if

  • You need payment initiation.
  • You work on Web, API.
  • You also want variable recurring payments.
Token.io 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 Token.io or Tuum better?
Neither clearly leads. Token.io 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, Token.io or Tuum?
Token.io starts at On request and Tuum at On request.
Does Token.io or Tuum run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Token.io best used for?
Token.io is most often used for a utility or telecom collecting high value bills where card interchange makes acceptance expensive, an investment or trading platform funding customer accounts without card chargeback exposure, a payment service provider adding pay by bank to its merchant proposition without building bank connectivity, a german merchant using giroapi scheme access for recurring and future dated bank payments. Of those, a utility or telecom collecting high value bills where card interchange makes acceptance expensive and an investment or trading platform funding customer accounts without card chargeback exposure are not what Tuum is typically brought in for.
What can Token.io do that Tuum cannot?
Token.io covers Payment initiation, Variable recurring payments, Bank network coverage, giroAPI membership. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.

Answered from the vendors’ own pages

Token.io: Does pay by bank remove card fees?

It removes interchange and scheme fees, so unit cost is normally far below card acceptance, particularly on high value payments.

Tuum: Is Tuum the same company as Modularbank?

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

Token.io: What about chargebacks?

There are none. That is the cost saving and the consumer protection gap, which is why it suits bills, top ups and account funding more than retail.

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.

Token.io: Is Token.io regulated?

Yes, it is an authorised third party provider under UK and European open banking rules, but it initiates payments rather than holding merchant funds as an acquirer.

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Share

Related pages

More on Token.io

More on Tuum

Keep looking

Other head to heads