Softwr

APIs · head to head

Neonomics vs Strands

Neonomics logo

Neonomics

APIs

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

From
On request
Rated
-
Strands logo

Strands

Personal Finance

Personal and business financial management modules for banks, owned by CRIF

From
On request
Rated
-

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.; Strands transaction categorisation accuracy depends on local merchant data, and banks in smaller markets face months of tuning before customers trust the categories shown.
  • They diverge on capability: Neonomics covers Payment initiation, Strands covers Transaction categorisation.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Neonomics and Strands actually diverge.

Attributes where Neonomics and Strands differ
AttributeNeonomicsStrands
PlatformsWeb, APIWeb, iOS, Android, REST API
CategoryAPIsPersonal Finance

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated).

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 Strands

  • Transaction categorisation
  • Personal financial management
  • Business financial management
  • Lighthouse
  • Automated savings
  • Account aggregation

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

Strands

  • A retail bank adding budgeting and spending insight without building a categorisation enginenot Neonomics
  • A bank wanting personalised product offers driven by observed spending and credit datanot Neonomics
  • A credit union offering small business customers cash flow forecasting inside online bankingnot Neonomics
  • A Nordic institution combining Strands insight with open banking account aggregationnot 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.

Strands

  • Transaction categorisation accuracy depends on local merchant data, and banks in smaller markets face months of tuning before customers trust the categories shown.
  • It is now a product line inside CRIF, a credit bureau, so roadmap priorities follow group data strategy rather than standalone software competition.
  • Commercial terms are often bundled with other CRIF services, which makes a standalone comparison against a pure PFM vendor harder to run.
  • Money management features have weak measurable impact on bank revenue, so the business case relies on engagement metrics that are difficult to tie to profit.
  • It is a white-label component, so the bank still owns design, support and customer communication, and a poor in-app implementation reflects on the bank rather than the vendor.

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

Strands

On request
  • Strands AI Finance Suite$undefined/year
    • Licence scaled by end customers or active users
    • Modules licensed separately for personal, business and Lighthouse
    • Implementation and categorisation tuning 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.

Choose Strands if

  • You need transaction categorisation.
  • You work on Web, iOS, Android, REST API.
  • You also want personal financial management.

Questions people ask

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

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.

Strands: Who owns Strands?

CRIF, the Italian credit bureau and information services group, which acquired it to combine money management software with credit data.

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.

Strands: Is it sold to consumers?

No. It is licensed to banks and credit unions who embed it in their own applications under their own brand.

Neonomics: Does Neonomics hold merchant funds?

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

Strands: Does it include account aggregation?

It supports aggregated external accounts, with CRIF and partners such as Enable Banking supplying the open banking connectivity.

Share

Related pages

Other head to heads