Softwr

APIs · head to head

i2c vs Neonomics

i2c logo

i2c

APIs

Configurable card issuing and banking processing platform for banks and programme managers

From
On request
Rated
-
Full reviewWebsite
Neonomics logo

Neonomics

APIs

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

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: i2c developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead.; 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.
  • They diverge on capability: i2c covers Configurable product engine, Neonomics covers Payment initiation.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which i2c and Neonomics actually diverge.

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

  • Configurable product engine
  • Credit and instalments
  • Multi-currency
  • Fraud and risk tooling
  • Digital banking front ends
  • Global scheme connectivity

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

What people use each for

The jobs each tool is most often brought in to do.

i2c

  • A bank wanting credit, debit and prepaid portfolios on one processor rather than threenot Neonomics
  • An issuer in a market where local scheme and currency support rules out US-centric processorsnot Neonomics
  • A programme manager launching instalment products without building a lending corenot Neonomics
  • A credit union replacing an ageing processor without writing custom code for product rulesnot Neonomics

Neonomics

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

Where each one falls short

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

i2c

  • Developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead.
  • Implementations lean on i2c or partner professional services, so timelines and costs are set by a services queue rather than by your own engineering speed.
  • Pricing is per active card and per transaction with monthly minimums, none of it published, so comparing bids requires modelling your own portfolio carefully.
  • Configuration flexibility means product behaviour lives in platform settings rather than in your repository, which complicates version control, testing and audit trails.
  • As a private company with a broad global footprint, regional support depth is uneven, and a programme in a smaller market may get thinner service than a flagship account.

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.

Pricing, plan by plan

i2c

On request
  • i2c processing platform$undefined/year
    • Per-active-card and per-transaction processing fees
    • Minimum monthly commitments by programme
    • Implementation and configuration professional services

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

Which should you pick?

Choose i2c if

  • You need configurable product engine.
  • You work on Web, REST API.
  • You also want credit and instalments.
i2c review

Choose Neonomics if

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

Questions people ask

Is i2c or Neonomics better?
Neither clearly leads. i2c starts at On request and Neonomics at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, i2c or Neonomics?
i2c starts at On request and Neonomics at On request.
Does i2c or Neonomics run on more platforms?
i2c runs on Web, REST API. Neonomics runs on Web, API.
What is i2c best used for?
i2c is most often used for a bank wanting credit, debit and prepaid portfolios on one processor rather than three, an issuer in a market where local scheme and currency support rules out us-centric processors, a programme manager launching instalment products without building a lending core, a credit union replacing an ageing processor without writing custom code for product rules. Of those, a bank wanting credit, debit and prepaid portfolios on one processor rather than three and an issuer in a market where local scheme and currency support rules out us-centric processors are not what Neonomics is typically brought in for.
What can i2c do that Neonomics cannot?
i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. Neonomics covers Payment initiation, Account information, Nordic bank depth, UK coverage via Ordo.

Answered from the vendors’ own pages

i2c: Does i2c issue the cards itself?

No. It processes; issuance sits with a bank or licensed issuer, and in most markets you need that relationship separately.

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.

i2c: Can it handle revolving credit?

Yes. Credit, instalments and buy-now-pay-later sit on the same platform as debit and prepaid, which is unusual among modern processors.

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.

i2c: Is it self-serve?

No. Expect a configuration-led implementation with professional services rather than signing up and calling an API.

Neonomics: Does Neonomics hold merchant funds?

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

Share

Related pages

More on i2c

More on Neonomics

Keep looking

Other head to heads