Softwr

APIs · head to head

Ozone API vs Trustly

Ozone API logo

Ozone API

APIs

Standards-compliant open banking API layer for banks and regulators

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: Ozone API it provides the API layer, not the core connectivity, so the bulk of the project is still integrating your own core banking systems and that cost is not in the licence.; 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: Ozone API covers Multi-standard support, 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 Ozone API and Trustly actually diverge.

Attributes where Ozone API and Trustly differ
AttributeOzone APITrustly
PlatformsWeb, REST API, LinuxWeb, 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 Ozone API

  • Multi-standard support
  • Consent management
  • Developer portal
  • Regulatory reporting
  • Premium API monetisation
  • Deployment flexibility

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.

Ozone API

  • A building society facing an open banking compliance deadline with no API team of its ownnot Trustly
  • A bank operating in several jurisdictions that must satisfy different open banking standards at oncenot Trustly
  • A regulator or standards body building national open finance infrastructurenot Trustly
  • A bank wanting to sell premium APIs beyond the regulatory minimum without building entitlement plumbingnot Trustly

Trustly

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

Where each one falls short

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

Ozone API

  • It provides the API layer, not the core connectivity, so the bulk of the project is still integrating your own core banking systems and that cost is not in the licence.
  • Value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend.
  • It is a small UK vendor selling to large regulated institutions, which raises procurement and vendor viability questions during bank due diligence.
  • Premium API monetisation is a genuine capability but few banks have found real demand, so revenue projections used to justify the purchase often do not materialise.
  • Standards evolve continuously and each revision means a change programme in your own systems, even where Ozone absorbs the specification work at the API edge.

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

Ozone API

On request
  • Ozone API$undefined/year
    • Annual licence or managed service subscription, quoted
    • Scaling by institution size, standards in scope and API call volume
    • Implementation and core integration charged separately

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 Ozone API if

  • You need multi-standard support.
  • You work on Web, REST API, Linux.
  • You also want consent management.
Ozone API 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 Ozone API or Trustly better?
Neither clearly leads. Ozone API 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, Ozone API or Trustly?
Ozone API starts at On request and Trustly at On request.
Does Ozone API or Trustly run on more platforms?
Ozone API runs on Web, REST API, Linux. Trustly runs on Web, API.
What is Ozone API best used for?
Ozone API is most often used for a building society facing an open banking compliance deadline with no api team of its own, a bank operating in several jurisdictions that must satisfy different open banking standards at once, a regulator or standards body building national open finance infrastructure, a bank wanting to sell premium apis beyond the regulatory minimum without building entitlement plumbing. Of those, a building society facing an open banking compliance deadline with no api team of its own and a bank operating in several jurisdictions that must satisfy different open banking standards at once are not what Trustly is typically brought in for.
What can Ozone API do that Trustly cannot?
Ozone API covers Multi-standard support, Consent management, Developer portal, Regulatory reporting. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity.

Answered from the vendors’ own pages

Ozone API: Is this a competitor to Plaid or TrueLayer?

No, the opposite side. Ozone is bought by the bank exposing data; Plaid and TrueLayer consume it on behalf of third parties.

Trustly: Who owns Trustly?

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

Ozone API: Does it connect to my core banking system?

It provides the standards-compliant API surface and adapters, but connecting your core is an integration project you scope separately.

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.

Ozone API: Which standards does it support?

UK Open Banking, Berlin Group, FDX, Consumer Data Right and Gulf regional standards, among others, from one platform.

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 Ozone API

More on Trustly

Keep looking

Other head to heads