Softwr

APIs · head to head

Episode Six vs Tribe Payments

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
Tribe Payments logo

Tribe Payments

APIs

Combined issuer and acquirer processing platform for fintechs, banks and acquirers

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.; Tribe Payments running both issuing and acquiring through one vendor concentrates operational risk, since a platform fault affects both sides of a client's card business at once rather than just one.
  • They diverge on capability: Episode Six covers Tritium API platform, Tribe Payments covers ISAAC core platform.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Episode Six and Tribe Payments actually diverge.

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

  • ISAAC core platform
  • Issuer processing
  • Acquirer processing
  • Multi-scheme connectivity
  • Open banking module
  • 3D Secure and fraud tooling

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 Tribe Payments
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Tribe Payments
  • A telco or airline launching a branded wallet and card product at national scalenot Tribe Payments
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot Tribe Payments

Tribe Payments

  • A bank or fintech wanting to run both card issuing and merchant acquiring on one processing platformnot Episode Six
  • A payment facilitator consolidating separate issuing and acquiring vendor relationships into one contractnot Episode Six
  • A company needing multi-scheme processing across Visa, Mastercard and regional networks like UnionPaynot Episode Six
  • An Asia-Pacific expansion where Tribe's Singapore office provides regional supportnot 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.

Tribe Payments

  • Running both issuing and acquiring through one vendor concentrates operational risk, since a platform fault affects both sides of a client's card business at once rather than just one.
  • Pricing for either the issuing or acquiring modules is not published, so budgeting requires a sales conversation.
  • With roughly 60-plus customers, it is smaller scale than Visa or Mastercard-owned processing infrastructure, which is a factor for a client prioritising vendor size and track record.
  • Its client base and support depth are concentrated in the UK and continental Europe, and the Asia-Pacific presence via Singapore is comparatively newer and less proven.
  • As with any combined issuing and acquiring platform, a client that only needs one side still evaluates and pays for a vendor built around doing both, which may not be the most specialised option available.

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

Tribe Payments

On request
  • Tribe Payments$undefined/year
    • Pricing not published for issuing or acquiring modules
    • Custom quote required via sales

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 Tribe Payments if

  • You need isaac core platform.
  • You work on Web, API.
  • You also want issuer processing.
Tribe Payments review

Questions people ask

Is Episode Six or Tribe Payments better?
Neither clearly leads. Episode Six starts at On request and Tribe Payments at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Episode Six or Tribe Payments?
Episode Six starts at On request and Tribe Payments at On request.
Does Episode Six or Tribe Payments run on more platforms?
Episode Six runs on Web, API, On-premise. Tribe Payments runs on Web, 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 Tribe Payments is typically brought in for.
What can Episode Six do that Tribe Payments cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Tribe Payments covers ISAAC core platform, Issuer processing, Acquirer processing, Multi-scheme connectivity.

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.

Tribe Payments: Does Tribe do both issuing and acquiring?

Yes, its ISAAC platform supports both, built for issuing in 2019 and acquiring from 2020.

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.

Tribe Payments: How many card schemes does it support?

Visa, Mastercard, Amex, Discover, JCB and UnionPay.

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.

Tribe Payments: Where is its customer base concentrated?

The UK and continental Europe, with a newer Singapore office serving Asia-Pacific.

Share

Related pages

More on Episode Six

More on Tribe Payments

Keep looking

Other head to heads