Softwr

APIs · head to head

Trustly vs Zeplo

Trustly logo

Trustly

APIs

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

From
On request
Rated
-
Full reviewWebsite
Zeplo logo

Zeplo

APIs

Message queue as a URL prefix, adding retries and delays to any HTTP request

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Zeplo has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; Zeplo zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
  • They diverge on capability: Trustly covers Pay by bank checkout, Zeplo covers URL prefix interface.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Trustly and Zeplo actually diverge.

Attributes where Trustly and Zeplo differ
AttributeTrustlyZeplo
Starting priceOn requestFree
Pricing modelquotePer month by request count
Free tierNoYes
PlatformsWeb, APIWeb, Cloud

Identical on both: 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 Trustly

  • Pay by bank checkout
  • Instant refunds
  • Verified payouts
  • Multi-market bank connectivity
  • Merchant dashboard and reconciliation
  • Fraud and risk tooling

Only in Zeplo

  • URL prefix interface
  • Retries with backoff
  • Delayed delivery
  • Cron scheduling
  • Concurrency limits
  • Deduplication keys
  • Request logs
  • Team workspaces

What people use each for

The jobs each tool is most often brought in to do.

Trustly

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

Zeplo

  • A Vercel or Cloudflare Workers application that needs retried background jobs without deploying a separate always-on workernot Trustly
  • A team that wants a webhook receiver protected by a concurrency limit so a burst does not overwhelm a downstream APInot Trustly
  • A small product needing cron jobs against HTTP endpoints without adding a scheduler to its infrastructurenot Trustly
  • A developer adding idempotent retries to an unreliable third-party API call with a one-line URL changenot Trustly

Where each one falls short

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

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.

Zeplo

  • Zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
  • The free Developer tier includes only 500 requests a month and one team member, so it is a demonstration allowance rather than a usable free plan for anything real.
  • Overage on the Developer tier is 20 US dollars per 100,000 requests, two hundred times the marginal rate on the Company tier, so exceeding the free allowance without upgrading is expensive.
  • Team members cost 15 US dollars each beyond the plan allowance, which is an odd charge on an infrastructure product billed by request volume.
  • Log retention is 30 days on both published tiers, so anything requiring longer audit trails on job execution has to be logged separately.

Pricing, plan by plan

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

Zeplo

Free
  • DeveloperFree
    • 500 requests a month included
    • $20 per additional 100,000 requests
    • 1 team member
  • Company$39/month
    • 1,000,000 requests a month included
    • $10 per additional million requests
    • Up to 3 team members
  • Enterprise$undefined/month
    • Volume discounts
    • Custom team size
    • Support with SLA

Which should you pick?

Choose Trustly if

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

Choose Zeplo if

  • You need url prefix interface.
  • You want to start without paying.
  • You work on Web, Cloud.
  • You also want retries with backoff.
Zeplo review

Questions people ask

Is Trustly or Zeplo better?
Neither clearly leads. Trustly starts at On request and Zeplo at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Trustly or Zeplo?
Zeplo has a free tier; the other does not. Paid plans start at On request for Trustly and Free for Zeplo.
Does Trustly or Zeplo run on more platforms?
Trustly runs on Web, API. Zeplo runs on Web, Cloud.
Can I use Zeplo for free?
Yes. Zeplo has a free tier, so you can try it without paying. Trustly starts at On request.
What is Trustly best used for?
Trustly is most often used for an e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptance, a gaming or gambling operator needing verified, instant payouts to players' bank accounts, a merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delays, a business in a market with strong open banking adoption wanting pay-by-bank as a checkout option. Of those, an e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptance and a gaming or gambling operator needing verified, instant payouts to players' bank accounts are not what Zeplo is typically brought in for.
What can Trustly do that Zeplo cannot?
Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.

Answered from the vendors’ own pages

Trustly: Who owns Trustly?

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

Zeplo: How does Zeplo work?

You prefix your endpoint URL with zeplo.to and add query parameters for retries, delay, cron or concurrency. No SDK or broker is needed.

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.

Zeplo: What does it cost?

Free for 500 requests a month; 39 US dollars a month for a million requests, then 10 dollars per additional million.

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.

Zeplo: Is it suitable for critical jobs?

It is a small vendor in your execution path with no published SLA below Enterprise, so weigh that against the convenience.

Zeplo: Does it work with serverless platforms?

Yes, that is its main use, covering Vercel, Cloudflare Workers, Netlify and similar environments that lack long-running workers.

Share

Related pages

More on Trustly

More on Zeplo

Keep looking

Other head to heads