Softwr

APIs · head to head

Temenos Transact vs Volt

Temenos Transact logo

Temenos Transact

APIs

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

From
On request
Rated
-
Full reviewWebsite
Volt logo

Volt

APIs

Account-to-account pay by bank across Europe, the UK, Brazil and Australia

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.; Volt account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.
  • They diverge on capability: Temenos Transact covers Country model banks, Volt covers Pay by bank.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Temenos Transact and Volt differ
AttributeTemenos TransactVolt
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 Volt

  • Pay by bank
  • Circuit Breaker
  • Virtual IBANs
  • Payouts and refunds
  • Verify
  • Stablecoin checkout

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 Volt
  • An institution running Islamic banking products alongside conventional ones on one corenot Volt
  • A bank that needs a large pool of experienced implementation consultants to de-risk a migrationnot Volt
  • A group standardising subsidiaries in several countries onto one core banking systemnot Volt

Volt

  • A travel seller with high average order values paying percentage card fees it wants to replace with flat transfer feesnot Temenos Transact
  • An iGaming operator needing fast deposits and payouts where card acceptance is restrictednot Temenos Transact
  • A merchant with heavy card fraud that wants strongly authenticated irreversible paymentsnot Temenos Transact
  • A marketplace verifying seller bank accounts before paying outnot 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.

Volt

  • Account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.
  • Refunds are outbound payments rather than reversals, which changes treasury handling and means a refund can fail for reasons a card refund never would.
  • Conversion is lower than a stored card because the shopper must complete a bank authentication journey, and drop-off varies significantly by bank.
  • Core pay by bank pricing is per transaction but refunds, payouts, virtual IBANs, Verify and fraud tooling are billed separately, so the real cost is a stack of line items.
  • Bank API availability and quality vary across markets, and an outage at a major bank removes a slice of your checkout with no fallback unless you keep cards live.

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

Volt

On request
  • Volt pay by bank$undefined/year
    • Per successful transaction fee, quoted by volume and market
    • Separate charges for refunds, payouts, virtual IBANs and Verify
    • Circuit Breaker fraud tooling priced as an add-on

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 Volt if

  • You need pay by bank.
  • You work on Web, REST API.
  • You also want circuit breaker.
Volt review

Questions people ask

Is Temenos Transact or Volt better?
Neither clearly leads. Temenos Transact starts at On request and Volt at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Temenos Transact or Volt?
Temenos Transact starts at On request and Volt at On request.
Does Temenos Transact or Volt run on more platforms?
Temenos Transact runs on Web, Linux, Windows, REST API. Volt 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 Volt is typically brought in for.
What can Temenos Transact do that Volt cannot?
Temenos Transact covers Country model banks, Multi-product core, Payments processing, API layer. Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds.

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.

Volt: Are there chargebacks?

No. Bank transfers are irrevocable, so disputes are handled commercially between merchant and customer, not through a card scheme.

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.

Volt: How do refunds work?

As a separate outbound payment initiated by the merchant, which Volt charges for separately from the inbound transaction.

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.

Volt: Which markets are covered?

Europe and the UK, plus Brazil and Australia, on a single API integration.

Share

Related pages

More on Temenos Transact

More on Volt

Keep looking

Other head to heads