Softwr

APIs · head to head

Episode Six vs Trustly

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

Trustly

APIs

Pay-by-bank payments network, majority-owned by private equity firm Nordic Capital

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.; Trustly it is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
  • They diverge on capability: Episode Six covers Tritium API platform, Trustly covers Pay by bank checkout.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Episode Six and Trustly differ
AttributeEpisode SixTrustly
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 Trustly

  • Pay by bank checkout
  • Instant refunds
  • Verified payouts
  • Multi-market bank connectivity
  • Merchant dashboard and reconciliation
  • Fraud and risk 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 Trustly
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Trustly
  • A telco or airline launching a branded wallet and card product at national scalenot Trustly
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot Trustly

Trustly

  • An e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptancenot Episode Six
  • A gaming or gambling operator needing verified, instant payouts to players' bank accountsnot Episode Six
  • A merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delaysnot Episode Six
  • A business in a market with strong open banking adoption wanting pay-by-bank as a checkout optionnot 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.

Trustly

  • It is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
  • Consumer familiarity with paying by bank transfer still lags card payments in most markets, so merchants typically see it used as a secondary option rather than a full card replacement.
  • The 1.15 to 3.15% merchant fee range is not a single published rate, so a merchant cannot know its actual cost without a sales negotiation.
  • As with all open banking-dependent payment methods, reliability depends on the consistency of the underlying banks' own APIs, which Trustly does not control.
  • Its verified payout functionality is heavily used in gaming and gambling, a sector with additional regulatory scrutiny, which is worth factoring in when evaluating vendor risk exposure by association.

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

Trustly

On request
  • Trustly$undefined/month
    • Typical merchant cost of 1.15% to 3.15% depending on volume and market
    • Exact rate negotiated per merchant, not published as a flat card

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

  • You need pay by bank checkout.
  • You work on Web, API.
  • You also want instant refunds.
Trustly review

Questions people ask

Is Episode Six or Trustly better?
Neither clearly leads. Episode Six starts at On request and Trustly at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Episode Six or Trustly?
Episode Six starts at On request and Trustly at On request.
Does Episode Six or Trustly run on more platforms?
Episode Six runs on Web, API, On-premise. Trustly 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 Trustly is typically brought in for.
What can Episode Six do that Trustly cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank 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.

Trustly: Who owns Trustly?

Nordic Capital, a private equity firm, holds a 51.1% majority stake; Alfven & Didrikson and BlackRock hold smaller stakes.

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.

Trustly: Is Trustly going public?

It has discussed an IPO but as of its most recent comments said one remained at least a year away.

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.

Trustly: What does it typically cost a merchant?

Roughly 1.15% to 3.15% of transaction value depending on volume and market, negotiated per merchant.

Share

Related pages

More on Episode Six

More on Trustly

Keep looking

Other head to heads