Softwr

APIs · head to head

Episode Six vs Swan

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
Swan logo

Swan

APIs

European banking-as-a-service platform for embedding accounts, cards and payments into other products

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.; Swan its regulatory base and strongest local account coverage are French and European, so companies needing US, UK-post-Brexit-specific, or broader global banking-as-a-service need an additional provider.
  • They diverge on capability: Episode Six covers Tritium API platform, Swan covers Embedded business accounts.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Episode Six and Swan differ
AttributeEpisode SixSwan
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 Swan

  • Embedded business accounts
  • Card issuing
  • SEPA payments
  • Local account localisation
  • ACPR regulation
  • Usage-based pricing

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

Swan

  • A vertical SaaS platform wanting to embed business bank accounts under its own brandnot Episode Six
  • A marketplace wanting to issue cards to sellers or partners without becoming a licensed banknot Episode Six
  • A company wanting SEPA payment initiation embedded directly into its own productnot Episode Six
  • A European fintech wanting to avoid a six-figure setup fee and long lock-in typical of legacy banking-as-a-service dealsnot 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.

Swan

  • Its regulatory base and strongest local account coverage are French and European, so companies needing US, UK-post-Brexit-specific, or broader global banking-as-a-service need an additional provider.
  • Pricing is described only philosophically (usage-based, no big setup fee) rather than published as an actual rate card, so a company still needs a sales conversation to get real numbers.
  • Embedding banking features into a product is a substantial compliance and design undertaking regardless of the vendor, and Swan handling the licence does not remove a platform's own KYC, AML and customer support obligations for the accounts it offers.
  • As a comparatively young, single-country-licensed e-money institution, its balance sheet and regulatory standing carry more concentration risk than a banking-as-a-service offering backed by an established, multi-jurisdiction bank.
  • Local account depth is explicitly limited to France, Germany and Spain, so a platform needing native local accounts in other European countries may find coverage thinner than expected.

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

Swan

On request
  • Swan$undefined/month
    • Usage-based pricing, no published rate card
    • No long-term contract or large setup fee required
    • Custom quote based on current, not forecast, usage

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

  • You need embedded business accounts.
  • You work on Web, API.
  • You also want card issuing.
Swan review

Questions people ask

Is Episode Six or Swan better?
Neither clearly leads. Episode Six starts at On request and Swan at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Episode Six or Swan?
Episode Six starts at On request and Swan at On request.
Does Episode Six or Swan run on more platforms?
Episode Six runs on Web, API, On-premise. Swan 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 Swan is typically brought in for.
What can Episode Six do that Swan cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Swan covers Embedded business accounts, Card issuing, SEPA payments, Local account localisation.

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.

Swan: Which countries does Swan offer local accounts in?

France, Germany and Spain specifically, alongside broader SEPA payment coverage.

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.

Swan: Is pricing published?

No, Swan describes a usage-based, no-large-setup-fee philosophy but requires a quote for actual numbers.

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.

Swan: Who regulates Swan?

France's ACPR (Autorite de Controle Prudentiel et de Resolution), as a licensed e-money institution.

Share

Related pages

More on Episode Six

More on Swan

Keep looking

Other head to heads