Softwr

APIs · head to head

Neonomics vs Weavr

Neonomics logo

Neonomics

APIs

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

From
On request
Rated
-
Full reviewWebsite
Weavr logo

Weavr

APIs

Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence

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.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • They diverge on capability: Neonomics covers Payment initiation, Weavr covers Plug-and-play products.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Neonomics and Weavr actually diverge.

Attributes where Neonomics and Weavr differ
AttributeNeonomicsWeavr
PlatformsWeb, APIWeb, REST 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 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 Weavr

  • Plug-and-play products
  • Regulated cover
  • Card issuing
  • Multi-currency accounts
  • Identity and onboarding
  • Data insights

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

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Neonomics
  • A marketplace paying out sellers from accounts held inside its own productnot Neonomics
  • A procurement platform issuing virtual cards against approved purchase ordersnot Neonomics
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot 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.

Weavr

  • Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
  • It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
  • Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
  • European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.

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

Weavr

On request
  • Weavr embedded finance$undefined/year
    • Platform subscription plus per-account and per-card fees
    • Interchange share negotiated as part of the commercial terms
    • Monthly minimums apply to card programmes

Which should you pick?

Choose Neonomics if

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

Choose Weavr if

  • You need plug-and-play products.
  • You work on Web, REST API.
  • You also want regulated cover.
Weavr review

Questions people ask

Is Neonomics or Weavr better?
Neither clearly leads. Neonomics starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Neonomics or Weavr?
Neonomics starts at On request and Weavr at On request.
Does Neonomics or Weavr run on more platforms?
Neonomics runs on Web, API. Weavr runs on Web, 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 Weavr is typically brought in for.
What can Neonomics do that Weavr cannot?
Neonomics covers Payment initiation, Account information, Nordic bank depth, UK coverage via Ordo. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

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.

Weavr: Do I need my own financial licence?

No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.

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.

Weavr: How is it different from a banking-as-a-service API?

It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.

Neonomics: Does Neonomics hold merchant funds?

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

Weavr: How does Weavr make money?

Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.

Share

Related pages

More on Neonomics

More on Weavr

Keep looking

Other head to heads