APIs · head to head
Tink vs Tuum

Tink
APIs
European open banking platform for account data and payment initiation
- From
- On request
- Rated
- -

Tuum
APIs
Modular core banking platform from Estonia, formerly branded Modularbank
- From
- On request
- Rated
- -
The short version
- Each has a real cost: Tink visa owns Tink, and pay-by-bank exists to move payments off card rails, so the roadmap and pricing of the product you are using to reduce interchange are set by the company that earns the interchange.; 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: Tink covers Account data access, Tuum covers Modular product structure.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Tink and Tuum actually diverge.
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 Tink
- Account data access
- Payment initiation
- EEA passporting
- Categorisation
- Account verification
- Risk and affordability signals
- Variable recurring payments support
- Consent management
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.
Tink
- A European lender that needs verified income and expense data from a borrower bank account across several EEA markets under one licencenot Tuum
- A merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value basketsnot Tuum
- A fintech that does not hold its own PSD2 licence and needs to operate under an authorised provider passported across the EEAnot Tuum
- A bank building an account aggregation view of a customer external accounts without negotiating with each institution individuallynot Tuum
Tuum
- A bank wanting to migrate specific banking products to the cloud within months rather than replacing its entire core at oncenot Tink
- A fintech in the DACH region or Middle East wanting a European core banking vendor with regional expansion focusnot Tink
- An institution wanting low-code middleware to connect new modules to an existing legacy core rather than a full rebuildnot Tink
- A company researching "Modularbank" that needs to confirm it is the same company now branded Tuumnot Tink
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Tink
- Visa owns Tink, and pay-by-bank exists to move payments off card rails, so the roadmap and pricing of the product you are using to reduce interchange are set by the company that earns the interchange.
- Coverage is Europe only, so a product serving both European and United States users runs a second aggregator with a different data model and a separate contract.
- PSD2 connection quality varies sharply by bank, and headline connection counts hide wide differences in success rate, consent lifetime and re-authentication frequency that determine what users actually experience.
- Consent under PSD2 expires and requires periodic re-authentication, so any product depending on continuous data access has a recurring user friction it cannot design away, and drop-off at re-consent is a real product problem.
- Pricing is quoted with data access and payment initiation priced separately, and there is no published rate card, so small merchants cannot compare pay-by-bank economics against card acceptance without a sales process.
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
Tink
On request- Tink Platform$undefined/year
- Priced by product, market and volume
- Data access and payment initiation priced separately
- Annual commitments typical for enterprise agreements
Tuum
On request- Tuum$undefined/year
- Subscription and module-based pricing, not published
- Custom quote required via sales
Which should you pick?
Choose Tink if
- You need account data access.
- You work on API, Web.
- You also want payment initiation.
Choose Tuum if
- You need modular product structure.
- You work on Web, API.
- You also want low-code integration middleware.
Questions people ask
- Is Tink or Tuum better?
- Neither clearly leads. Tink 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, Tink or Tuum?
- Tink starts at On request and Tuum at On request.
- Does Tink or Tuum run on more platforms?
- Tink runs on API, Web. Tuum runs on Web, API.
- What is Tink best used for?
- Tink is most often used for a european lender that needs verified income and expense data from a borrower bank account across several eea markets under one licence, a merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value baskets, a fintech that does not hold its own psd2 licence and needs to operate under an authorised provider passported across the eea, a bank building an account aggregation view of a customer external accounts without negotiating with each institution individually. Of those, a european lender that needs verified income and expense data from a borrower bank account across several eea markets under one licence and a merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value baskets are not what Tuum is typically brought in for.
- What can Tink do that Tuum cannot?
- Tink covers Account data access, Payment initiation, EEA passporting, Categorisation. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.
Answered from the vendors’ own pages
Tink: Who owns Tink?
Visa, since 2022. That is directly relevant if you are adopting pay-by-bank specifically to reduce card costs.
Tuum: Is Tuum the same company as Modularbank?
Yes, Modularbank rebranded to Tuum; it is the same company and platform.
Tink: Do I need my own PSD2 licence?
No. Tink holds AIS and PIS licences from the Swedish FSA passported across the EEA, and customers can operate as its agent rather than obtaining their own authorisation.
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.
Tink: Does Tink cover the United States?
No. It is a European platform. US coverage requires a separate provider.
Tuum: Is pricing published?
No, subscription and module pricing require a sales conversation.
Tink: How reliable are the bank connections?
It varies by institution far more than the headline count of roughly 6,000 connections suggests. Ask for per market and per bank success rates and consent lifetimes for the banks your users actually hold accounts with.
Related pages
Other head to heads
- Tink vs TrueLayer
- Tink vs Token.io
- Tink vs Enable Banking
- Tink vs Yodlee
- Tink vs Bud Financial
- Tink vs MX Technologies
- Tink vs Neonomics
- Tink vs Yapily
- Tink vs Enfuce
- Tink vs Trustly
- Tink vs Volt
- Tink vs Salt Edge
- Tink vs Skaleet
- Tink vs Svix
- Tink vs Synctera
- Tink vs Treblle
- Tink vs Tribe Payments
- Tink vs Mambu
- Tink vs Vodeno
- Tink vs Fintech Farm
- Tink vs Weavr
- Tink vs Temenos Transact
- Tink vs 10x Banking
- Tink vs Unit
- Tink vs Griffin
- Tink vs Swan
- Tink vs i2c
- Tink vs Solaris
- Tink vs Tyk
- Tink vs WSO2 API Manager
- Tink vs Zimpler
- Tink vs 3scale
- Tink vs Aiia
- Tuum vs TrueLayer
- Tuum vs Token.io
- Tuum vs Enable Banking
- Tuum vs Yodlee
- Tuum vs Bud Financial
- Tuum vs MX Technologies
- Tuum vs Neonomics
- Tuum vs Yapily
- Tuum vs Enfuce
- Tuum vs Trustly
- Tuum vs Volt
- Tuum vs Salt Edge
- Tuum vs Skaleet
- Tuum vs Svix
- Tuum vs Synctera
- Tuum vs Treblle
- Tuum vs Tribe Payments
- Tuum vs Mambu
- Tuum vs Vodeno
- Tuum vs Fintech Farm
- Tuum vs Weavr
- Tuum vs Temenos Transact
- Tuum vs 10x Banking
- Tuum vs Unit
- Tuum vs Griffin
- Tuum vs Swan
- Tuum vs i2c
- Tuum vs Solaris
- Tuum vs Tyk
- Tuum vs WSO2 API Manager
- Tuum vs Zimpler
- Tuum vs 3scale
- Tuum vs Aiia
