Softwr

APIs · head to head

Episode Six vs Volt

Episode Six logo

Episode Six

APIs

Payment processing and ledger platform deployable on premise or in your own cloud

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: Episode Six deployment on premise or in a private tenancy means the institution carries infrastructure, upgrade and PCI scope work that a hosted processor would absorb.; 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: Episode Six covers Tritium API platform, Volt covers Pay by bank.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Episode Six and Volt actually diverge.

Attributes where Episode Six and Volt differ
AttributeEpisode SixVolt
PlatformsWeb, API, On-premiseWeb, 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 Episode Six

  • Tritium API platform
  • Flexible deployment
  • Multi product issuing
  • Digital wallets
  • Multi currency ledger
  • Network connectivity
  • Configurable product engine
  • Institutional controls

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.

Episode Six

  • A bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloudnot Volt
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Volt
  • A telco or airline launching a branded wallet and card product at national scalenot Volt
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot Volt

Volt

  • A travel seller with high average order values paying percentage card fees it wants to replace with flat transfer feesnot Episode Six
  • An iGaming operator needing fast deposits and payouts where card acceptance is restrictednot Episode Six
  • A merchant with heavy card fraud that wants strongly authenticated irreversible paymentsnot Episode Six
  • A marketplace verifying seller bank accounts before paying outnot Episode Six

Where each one falls short

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

Episode Six

  • Deployment on premise or in a private tenancy means the institution carries infrastructure, upgrade and PCI scope work that a hosted processor would absorb.
  • Implementation runs to quarters and involves core banking, network certification and fraud system integration, so time to first card is far longer than with a self serve issuer processor.
  • Pricing is entirely bespoke and weighted to large programmes, which prices out fintechs and small issuers who would be better served by a hosted platform.
  • Being smaller than the incumbent processors, its network certifications and operational presence vary by region, so a global rollout can find gaps in specific markets.
  • The flexibility of six hundred APIs and a configurable product engine shifts design responsibility onto the buyer, and institutions without strong internal payments architects end up dependent on professional services.

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

Episode Six

On request
  • Tritium platform$undefined/year
    • Licence and implementation quoted per institution
    • Deployment model affects cost materially: on premise, private cloud or hosted
    • Processing fees typically per transaction or per active card

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 Episode Six if

  • You need tritium api platform.
  • You work on Web, API, On-premise.
  • You also want flexible deployment.
Episode Six 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 Episode Six or Volt better?
Neither clearly leads. Episode Six 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, Episode Six or Volt?
Episode Six starts at On request and Volt at On request.
Does Episode Six or Volt run on more platforms?
Episode Six runs on Web, API, On-premise. Volt runs on Web, REST API.
What is Episode Six best used for?
Episode Six is most often used for a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud, a large institution replacing a legacy card processor without moving off its own infrastructure, a telco or airline launching a branded wallet and card product at national scale, a bank running prepaid, debit and credit products that wants them on one ledger rather than three processors. Of those, a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud and a large institution replacing a legacy card processor without moving off its own infrastructure are not what Volt is typically brought in for.
What can Episode Six do that Volt cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds.

Answered from the vendors’ own pages

Episode Six: Can Episode Six run inside our own data centre?

Yes. On premise and private cloud deployment is the main reason banks choose it over hosted only processors.

Volt: Are there chargebacks?

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

Episode Six: Is it suitable for a startup issuing its first cards?

Not really. The licence, implementation timeline and cost are aimed at banks and large institutions.

Volt: How do refunds work?

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

Episode Six: Do we still need a card licence or sponsor?

Yes. Episode Six is a processor. Network membership, licensing or a sponsor arrangement remains your responsibility.

Volt: Which markets are covered?

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

Share

Related pages

More on Episode Six

More on Volt

Keep looking

Other head to heads