Softwr

APIs · head to head

Neonomics vs Skaleet

Neonomics logo

Neonomics

APIs

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

From
On request
Rated
-
Full reviewWebsite
Skaleet logo

Skaleet

APIs

Cloud-native core banking and payment hub with deployments measured in months

From
On request
Rated
-
Full reviewWebsite

The short version

  • 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.; Skaleet the installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • They diverge on capability: Neonomics covers Payment initiation, Skaleet covers Cloud-native core.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Neonomics and Skaleet actually diverge.

Attributes where Neonomics and Skaleet differ
AttributeNeonomicsSkaleet
PlatformsWeb, APIWeb, REST API, Linux

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 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 Skaleet

  • Cloud-native core
  • Payment hub
  • Card management
  • Lending
  • API-first
  • Configurable products

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 Skaleet
  • A debt collection agency sending request to pay messages instead of chasing bank transfers manuallynot Skaleet
  • A software vendor embedding pay by bank into an accounting or invoicing product for Nordic customersnot Skaleet
  • A business needing both UK and Nordic bank payment coverage from one suppliernot Skaleet

Skaleet

  • A banking group launching a digital savings or deposit brand in a new country within a yearnot Neonomics
  • A bank modernising payments to ISO 20022 without replacing its whole corenot Neonomics
  • A payroll or HR software company adding embedded banking to its productnot Neonomics
  • A payment service provider needing a ledger and accounts under its existing licencenot 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.

Skaleet

  • The installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • Speed references are mostly greenfield launches inside large groups, which is an easier problem than migrating an existing book off a legacy core.
  • It is European-centric, with payment rails and regulatory work concentrated on SEPA and EU requirements rather than global coverage.
  • As a smaller vendor carrying a bank core, it attracts hard concentration and viability questions in procurement that larger competitors do not face.
  • Pricing is unpublished and scaled by accounts and transactions, so a bank whose volumes grow faster than forecast faces cost escalation it did not model.

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

Skaleet

On request
  • Skaleet Core Banking Platform$undefined/year
    • Subscription licence scaled by accounts and transaction volume
    • Payment hub licensable separately from the full core
    • Implementation and configuration charged as a project

Which should you pick?

Choose Neonomics if

  • You need payment initiation.
  • You work on Web, API.
  • You also want account information.
Neonomics review

Choose Skaleet if

  • You need cloud-native core.
  • You work on Web, REST API, Linux.
  • You also want payment hub.
Skaleet review

Questions people ask

Is Neonomics or Skaleet better?
Neither clearly leads. Neonomics starts at On request and Skaleet at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Neonomics or Skaleet?
Neonomics starts at On request and Skaleet at On request.
Does Neonomics or Skaleet run on more platforms?
Neonomics runs on Web, API. Skaleet runs on Web, REST API, Linux.
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 Skaleet is typically brought in for.
What can Neonomics do that Skaleet cannot?
Neonomics covers Payment initiation, Account information, Nordic bank depth, UK coverage via Ordo. Skaleet covers Cloud-native core, Payment hub, Card management, Lending.

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.

Skaleet: What was Skaleet called before?

TagPay. The company rebranded to Skaleet while keeping the same platform lineage.

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.

Skaleet: Can I buy just the payment hub?

Yes. The payment engine is licensable standalone and can sit over an existing core, which is a common first step.

Neonomics: Does Neonomics hold merchant funds?

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

Skaleet: How fast are real deployments?

Named European deployments have gone live in six to twelve months, including a Crédit Agricole savings platform live in Germany in eight months.

Share

Related pages

More on Neonomics

More on Skaleet

Keep looking

Other head to heads