Softwr

APIs · head to head

Brite Payments vs Tuum

Brite Payments logo

Brite Payments

APIs

Instant account to account payments and payouts across Europe

From
On request
Rated
-
Tuum logo

Tuum

APIs

Modular core banking platform from Estonia, formerly branded Modularbank

From
On request
Rated
-

The short version

  • Each has a real cost: Brite Payments because Brite fronts settlement it underwrites the merchant, so higher risk sectors face volume caps, reserves or delayed settlement that undo the instant advantage they bought it for.; 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: Brite Payments covers Instant pay ins, Tuum covers Modular product structure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Brite Payments and Tuum differ
AttributeBrite 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 Brite Payments

  • Instant pay ins
  • Instant payouts
  • Proprietary settlement network
  • European bank coverage
  • Recurring and one click
  • Risk and verification
  • Merchant reporting
  • Hosted checkout

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.

Brite Payments

  • A gambling operator that needs deposits confirmed instantly and withdrawals paid out in seconds to retain playersnot Tuum
  • A trading platform funding customer accounts without card chargeback exposurenot Tuum
  • A marketplace paying sellers on demand rather than in weekly batchesnot Tuum
  • A Nordic retailer replacing card acceptance on high value baskets to cut interchange costnot Tuum

Tuum

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

Where each one falls short

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

Brite Payments

  • Because Brite fronts settlement it underwrites the merchant, so higher risk sectors face volume caps, reserves or delayed settlement that undo the instant advantage they bought it for.
  • There is no chargeback scheme, so refunds, disputes and fraud recovery are processes the merchant has to build and staff itself.
  • Coverage and instant capability differ markedly by country, with the Nordics far stronger than southern and eastern Europe, so a pan European rollout gives inconsistent customer experience.
  • Conversion depends on each bank's authentication journey, and the merchant cannot fix a slow or unreliable bank redirect that is costing it sales.
  • A large share of Brite's volume comes from gambling and trading, which concentrates regulatory exposure: a change in gambling payment rules in a key market would affect the provider as well as the merchant.

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

Brite Payments

On request
  • Brite instant payments$undefined/year
    • Quoted per merchant, typically per transaction
    • Pay ins and payouts priced separately
    • Merchant underwriting may impose volume limits, reserves or delayed settlement

Tuum

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

Which should you pick?

Choose Brite Payments if

  • You need instant pay ins.
  • You work on Web, API.
  • You also want instant payouts.

Choose Tuum if

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

Questions people ask

Is Brite Payments or Tuum better?
Neither clearly leads. Brite 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, Brite Payments or Tuum?
Brite Payments starts at On request and Tuum at On request.
Does Brite Payments or Tuum run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Brite Payments best used for?
Brite Payments is most often used for a gambling operator that needs deposits confirmed instantly and withdrawals paid out in seconds to retain players, a trading platform funding customer accounts without card chargeback exposure, a marketplace paying sellers on demand rather than in weekly batches, a nordic retailer replacing card acceptance on high value baskets to cut interchange cost. Of those, a gambling operator that needs deposits confirmed instantly and withdrawals paid out in seconds to retain players and a trading platform funding customer accounts without card chargeback exposure are not what Tuum is typically brought in for.
What can Brite Payments do that Tuum cannot?
Brite Payments covers Instant pay ins, Instant payouts, Proprietary settlement network, European bank coverage. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.

Answered from the vendors’ own pages

Brite Payments: How is Brite different from a standard open banking initiator?

It settles on its own network, so the merchant sees funds as final in seconds rather than waiting for the bank transfer to clear.

Tuum: Is Tuum the same company as Modularbank?

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

Brite Payments: Are payouts really instant?

In markets with mature instant payment schemes, yes. Elsewhere the speed depends on local rails, so check country by country.

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.

Brite Payments: What about disputes?

There is no chargeback framework on account to account payments. Refunds and disputes are entirely your own process.

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Share

Related pages

Other head to heads