Softwr

APIs · head to head

Neonomics vs Zeplo

Neonomics logo

Neonomics

APIs

Nordic open banking payments and data, now with UK coverage through Ordo

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: Neonomics coverage outside the Nordics and the UK is comparatively shallow, so a pan European merchant will find gaps and inconsistent bank behaviour in southern and eastern markets.; 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: Neonomics covers Payment initiation, Zeplo covers URL prefix interface.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Neonomics and Zeplo actually diverge.

Attributes where Neonomics and Zeplo differ
AttributeNeonomicsZeplo
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 Neonomics

  • Payment initiation
  • Account information
  • Nordic bank depth
  • UK coverage via Ordo
  • Variable recurring payments
  • Request to pay
  • White label journeys
  • Reconciliation data

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.

Neonomics

  • A Norwegian or Swedish merchant collecting payments directly from bank accounts to avoid card feesnot Zeplo
  • A debt collection agency sending request to pay messages instead of chasing bank transfers manuallynot Zeplo
  • A software vendor embedding pay by bank into an accounting or invoicing product for Nordic customersnot Zeplo
  • A business needing both UK and Nordic bank payment coverage from one suppliernot Zeplo

Zeplo

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

Where each one falls short

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

Neonomics

  • Coverage outside the Nordics and the UK is comparatively shallow, so a pan European merchant will find gaps and inconsistent bank behaviour in southern and eastern markets.
  • It is a small company relative to Tink and TrueLayer, so supplier viability and the depth of engineering support behind bank API changes are genuine procurement questions.
  • Payment initiation only means the merchant handles settlement, reconciliation and refunds, and there is no chargeback framework to fall back on.
  • Integrating a recently acquired UK business means two regulatory entities and, for a period, two technology stacks, so cross market feature parity is a promise rather than an existing state.
  • Conversion is governed by each bank's own authentication experience, and Nordic BankID flows behave differently from UK app redirects, so a single UX cannot be assumed across the footprint.

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

Neonomics

On request
  • Neonomics platform$undefined/year
    • Quoted per customer, typically per initiated payment or per API call
    • Volume commitments and monthly minimums are common
    • Payment initiation only; merchant handles settlement and refunds

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

  • You need payment initiation.
  • You work on Web, API.
  • You also want account information.
Neonomics 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 Neonomics or Zeplo better?
Neither clearly leads. Neonomics 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, Neonomics or Zeplo?
Zeplo has a free tier; the other does not. Paid plans start at On request for Neonomics and Free for Zeplo.
Does Neonomics or Zeplo run on more platforms?
Neonomics 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. Neonomics starts at On request.
What is Neonomics best used for?
Neonomics is most often used for a norwegian or swedish merchant collecting payments directly from bank accounts to avoid card fees, a debt collection agency sending request to pay messages instead of chasing bank transfers manually, a software vendor embedding pay by bank into an accounting or invoicing product for nordic customers, a business needing both uk and nordic bank payment coverage from one supplier. Of those, a norwegian or swedish merchant collecting payments directly from bank accounts to avoid card fees and a debt collection agency sending request to pay messages instead of chasing bank transfers manually are not what Zeplo is typically brought in for.
What can Neonomics do that Zeplo cannot?
Neonomics covers Payment initiation, Account information, Nordic bank depth, UK coverage via Ordo. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.

Answered from the vendors’ own pages

Neonomics: Is Neonomics authorised in the UK?

Yes, through the acquisition of Ordo, an FCA authorised open banking payments firm, approved by the FCA and the Norwegian regulator.

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.

Neonomics: Does it support variable recurring payments?

Yes in the UK through the Ordo capability, subject to which banks support commercial VRP; support elsewhere is more limited.

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.

Neonomics: Does Neonomics hold merchant funds?

No. It initiates payments; settlement, reconciliation and refunds remain with the merchant or its payment provider.

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 Neonomics

More on Zeplo

Keep looking

Other head to heads