Softwr

APIs · head to head

Temenos Transact vs Weavr

Temenos Transact logo

Temenos Transact

APIs

Established core banking system used by banks in over a hundred countries

From
On request
Rated
-
Full reviewWebsite
Weavr logo

Weavr

APIs

Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Temenos Transact the codebase originates in the 1990s, so banks on older releases face major upgrade programmes to reach current versions, and many defer them for years.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • They diverge on capability: Temenos Transact covers Country model banks, Weavr covers Plug-and-play products.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Temenos Transact and Weavr actually diverge.

Attributes where Temenos Transact and Weavr differ
AttributeTemenos TransactWeavr
PlatformsWeb, Linux, Windows, REST APIWeb, REST 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 Temenos Transact

  • Country model banks
  • Multi-product core
  • Payments processing
  • API layer
  • Cloud deployment
  • Accounting engine

Only in Weavr

  • Plug-and-play products
  • Regulated cover
  • Card issuing
  • Multi-currency accounts
  • Identity and onboarding
  • Data insights

What people use each for

The jobs each tool is most often brought in to do.

Temenos Transact

  • A bank in an emerging market needing local regulatory compliance without building it from scratchnot Weavr
  • An institution running Islamic banking products alongside conventional ones on one corenot Weavr
  • A bank that needs a large pool of experienced implementation consultants to de-risk a migrationnot Weavr
  • A group standardising subsidiaries in several countries onto one core banking systemnot Weavr

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Temenos Transact
  • A marketplace paying out sellers from accounts held inside its own productnot Temenos Transact
  • A procurement platform issuing virtual cards against approved purchase ordersnot Temenos Transact
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot Temenos Transact

Where each one falls short

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

Temenos Transact

  • The codebase originates in the 1990s, so banks on older releases face major upgrade programmes to reach current versions, and many defer them for years.
  • Total cost is dominated by implementation partner fees rather than licence, and those programmes routinely overrun their original estimates.
  • Product changes that cloud-native cores treat as configuration can require development work and a release cycle, which slows time to market for new products.
  • Heavy customisation is common and it makes every subsequent upgrade harder, creating a compounding cost that banks feel a decade after go-live.
  • Temenos has repeatedly restructured its product line and naming, so buyers must check carefully which components a proposal actually includes and which are separately licensed.

Weavr

  • Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
  • It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
  • Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
  • European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.

Pricing, plan by plan

Temenos Transact

On request
  • Temenos Transact$undefined/year
    • Perpetual or subscription licence scaled by assets, accounts or users
    • Annual maintenance typically a percentage of licence value
    • Implementation delivered by partners and charged separately

Weavr

On request
  • Weavr embedded finance$undefined/year
    • Platform subscription plus per-account and per-card fees
    • Interchange share negotiated as part of the commercial terms
    • Monthly minimums apply to card programmes

Which should you pick?

Choose Temenos Transact if

  • You need country model banks.
  • You work on Web, Linux, Windows, REST API.
  • You also want multi-product core.
Temenos Transact review

Choose Weavr if

  • You need plug-and-play products.
  • You work on Web, REST API.
  • You also want regulated cover.
Weavr review

Questions people ask

Is Temenos Transact or Weavr better?
Neither clearly leads. Temenos Transact starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Temenos Transact or Weavr?
Temenos Transact starts at On request and Weavr at On request.
Does Temenos Transact or Weavr run on more platforms?
Temenos Transact runs on Web, Linux, Windows, REST API. Weavr runs on Web, REST API.
What is Temenos Transact best used for?
Temenos Transact is most often used for a bank in an emerging market needing local regulatory compliance without building it from scratch, an institution running islamic banking products alongside conventional ones on one core, a bank that needs a large pool of experienced implementation consultants to de-risk a migration, a group standardising subsidiaries in several countries onto one core banking system. Of those, a bank in an emerging market needing local regulatory compliance without building it from scratch and an institution running islamic banking products alongside conventional ones on one core are not what Weavr is typically brought in for.
What can Temenos Transact do that Weavr cannot?
Temenos Transact covers Country model banks, Multi-product core, Payments processing, API layer. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

Answered from the vendors’ own pages

Temenos Transact: Is Transact the same as T24?

Yes. T24 was renamed Temenos Transact; older installations and much of the consultant population still use the T24 name.

Weavr: Do I need my own financial licence?

No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.

Temenos Transact: Can it run in the cloud?

Yes, it is offered on public cloud, though many existing installations remain on-premises and moving them is a project.

Weavr: How is it different from a banking-as-a-service API?

It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.

Temenos Transact: What drives the cost?

Licence scaled by size, annual maintenance as a percentage of licence, and implementation partner fees that usually exceed the software cost.

Weavr: How does Weavr make money?

Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.

Share

Related pages

More on Temenos Transact

More on Weavr

Keep looking

Other head to heads