APIs · head to head
Neonomics vs Salt Edge
Neonomics
APIs
Nordic open banking payments and data, now with UK coverage through Ordo
- From
- On request
- Rated
- -
Salt Edge
APIs
Independent open banking aggregator covering Europe by PSD2 API and other markets by direct connection
- 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.; Salt Edge coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
- They diverge on capability: Neonomics covers Nordic bank depth, Salt Edge covers Wide country coverage.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Neonomics and Salt Edge actually diverge.
Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web, API), 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
- Nordic bank depth
- UK coverage via Ordo
- Variable recurring payments
- Request to pay
- White label journeys
- Reconciliation data
Only in Salt Edge
- Wide country coverage
- Open Banking Gateway
- Categorisation and enrichment
- Consent management
- Partner and white label
- Sandbox
Both cover
- Payment initiation
- Account information
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 Salt Edge
- A debt collection agency sending request to pay messages instead of chasing bank transfers manuallynot Salt Edge
- A software vendor embedding pay by bank into an accounting or invoicing product for Nordic customersnot Salt Edge
- A business needing both UK and Nordic bank payment coverage from one suppliernot Salt Edge
Salt Edge
- A lender operating across several European and non-EU markets that needs one aggregation contract rather than a different provider per countrynot Neonomics
- A fintech that wants an aggregator not owned by a card network because its use case competes with card productsnot Neonomics
- An accounting or treasury product that needs bank feeds in markets the large aggregators do not servenot Neonomics
- A bank that must publish PSD2-compliant APIs and would rather buy the compliance layer than build itnot 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.
Salt Edge
- Coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
- Pricing is not published and is usage-based, so two providers cannot be compared without running both sales processes, and cost grows with the connected user base rather than with revenue.
- Support and engineering are distributed across Eastern Europe and Canada, and buyers in other time zones report slower turnaround on connection-specific breakages than they get from a domestic provider.
- PSD2 consent rules require customers to reauthenticate periodically, and Salt Edge cannot change that, so any product depending on continuous data must design for consent expiry and the drop-off it causes.
- United States coverage is weaker than Plaid or Mastercard Open Banking, so a company with meaningful US volume ends up running two aggregators and normalising between them.
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
Salt Edge
On request- Salt Edge Open Banking API$undefined/year
- Account information and payment initiation
- Coverage across 50 plus countries
- Consent management and enrichment
Which should you pick?
Choose Neonomics if
- You need nordic bank depth.
- You work on Web, API.
- You also want uk coverage via ordo.
Choose Salt Edge if
- You need wide country coverage.
- You work on Web, API.
- You also want open banking gateway.
Questions people ask
- Is Neonomics or Salt Edge better?
- Neither clearly leads. Neonomics starts at On request and Salt Edge at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Neonomics or Salt Edge?
- Neonomics starts at On request and Salt Edge at On request.
- Does Neonomics or Salt Edge run on more platforms?
- Both run on Web, API, so platform support will not decide this one for you.
- 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 Salt Edge is typically brought in for.
- What can Neonomics do that Salt Edge cannot?
- Neonomics covers Nordic bank depth, UK coverage via Ordo, Variable recurring payments, Request to pay. Salt Edge covers Wide country coverage, Open Banking Gateway, Categorisation and enrichment, Consent management. Both handle Payment initiation, Account information.
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.
Salt Edge: Who owns Salt Edge?
It is independently owned, unlike Tink (Visa), Finicity (Mastercard) or Yodlee (Envestnet), which matters if your use case competes with the owner.
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.
Salt Edge: Is all coverage direct bank API?
No. Inside PSD2 markets connections use regulated APIs; elsewhere coverage relies on direct connections whose reliability depends on the bank not changing its systems. Ask for a per-institution answer.
Neonomics: Does Neonomics hold merchant funds?
No. It initiates payments; settlement, reconciliation and refunds remain with the merchant or its payment provider.
Salt Edge: Does it do payments as well as data?
Yes, payment initiation is supported in European markets where PSD2 applies.
Salt Edge: What does it cost?
Not published. Pricing is usage-based and quoted, though the sandbox is free.
Related pages
Other head to heads
- Neonomics vs Token.io
- Neonomics vs TrueLayer
- Neonomics vs Tink
- Neonomics vs Enable Banking
- Neonomics vs Zimpler
- Neonomics vs Trustly
- Neonomics vs Fintecture
- Neonomics vs Yodlee
- Neonomics vs Brite Payments
- Neonomics vs Tribe Payments
- Neonomics vs Volt
- Neonomics vs Pusher
- Neonomics vs Skyflow
- Neonomics vs Backbase
- Neonomics vs Enfuce
- Neonomics vs Ozone API
- Neonomics vs Bud Financial
- Neonomics vs Akoya
- Neonomics vs Yapily
- Neonomics vs GraphQL Apollo
- Neonomics vs GraphQL Playground
- Neonomics vs Gravitee
- Neonomics vs Hoppscotch
- Neonomics vs HTTPie
- Neonomics vs Janus Gateway
- Salt Edge vs Token.io
- Salt Edge vs TrueLayer
- Salt Edge vs Tink
- Salt Edge vs Enable Banking
- Salt Edge vs Zimpler
- Salt Edge vs Trustly
- Salt Edge vs Fintecture
- Salt Edge vs Yodlee
- Salt Edge vs Brite Payments
- Salt Edge vs Tribe Payments
- Salt Edge vs Volt
- Salt Edge vs Pusher
- Salt Edge vs Skyflow
- Salt Edge vs Backbase
- Salt Edge vs Enfuce
- Salt Edge vs Ozone API
- Salt Edge vs Bud Financial
- Salt Edge vs Akoya
- Salt Edge vs Yapily
- Salt Edge vs GraphQL Apollo
- Salt Edge vs GraphQL Playground
- Salt Edge vs Gravitee
- Salt Edge vs Hoppscotch
- Salt Edge vs HTTPie
- Salt Edge vs Janus Gateway