Softwr

APIs · head to head

i2c vs Vodeno

i2c logo

i2c

APIs

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

From
On request
Rated
-
Full reviewWebsite
Vodeno logo

Vodeno

APIs

Banking-as-a-service platform running on a partner bank licence, backing NatWest's UK BaaS venture

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.; Vodeno its actual regulatory backing differs by geography, Aion Bank in continental Europe versus NatWest in the UK, so a customer must understand which entity and licence they are actually contracting under rather than assuming one uniform Vodeno product.
  • They diverge on capability: i2c covers Configurable product engine, Vodeno covers Core banking infrastructure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which i2c and Vodeno actually diverge.

Attributes where i2c and Vodeno differ
Attributei2cVodeno
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 Vodeno

  • Core banking infrastructure
  • Card issuance via Mastercard
  • Lending and BNPL modules
  • White-label mobile apps
  • Digital onboarding and compliance
  • UK entity backed by NatWest

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 Vodeno
  • An issuer in a market where local scheme and currency support rules out US-centric processorsnot Vodeno
  • A programme manager launching instalment products without building a lending corenot Vodeno
  • A credit union replacing an ageing processor without writing custom code for product rulesnot Vodeno

Vodeno

  • A European retailer or e-commerce business wanting to embed savings, lending or BNPL products under its own brandnot i2c
  • A UK business wanting banking-as-a-service backed specifically by NatWest's banking technology and licencenot i2c
  • A fintech wanting white-label mobile banking app infrastructure rather than building its own from scratchnot i2c
  • A company comparing banking-as-a-service providers that want to understand which underlying bank licence actually backs the product in their marketnot 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.

Vodeno

  • Its actual regulatory backing differs by geography, Aion Bank in continental Europe versus NatWest in the UK, so a customer must understand which entity and licence they are actually contracting under rather than assuming one uniform Vodeno product.
  • Pricing is entirely unpublished across both the European and UK businesses.
  • The scale of NatWest's investment (up to roughly £120 million) signals a business still working toward profitability, with NatWest itself targeting breakeven within five years of the venture launching, which is a meaningful timeline risk for a customer building long-term infrastructure dependency on it.
  • As banking-as-a-service infrastructure, any customer remains dependent on Vodeno's underlying bank partner maintaining its own licence and risk appetite, which is a layer of dependency beyond Vodeno's own commercial terms.
  • Product scope, such as lending and BNPL availability, may differ between the UK and European entities, so a company operating in both markets should not assume identical capability across the two.

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

Vodeno

On request
  • Vodeno$undefined/year
    • Platform licensing fee, not published
    • Terms differ between the European (Aion Bank) and UK (NatWest) entities

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 Vodeno if

  • You need core banking infrastructure.
  • You work on Web, API.
  • You also want card issuance via mastercard.
Vodeno review

Questions people ask

Is i2c or Vodeno better?
Neither clearly leads. i2c starts at On request and Vodeno at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, i2c or Vodeno?
i2c starts at On request and Vodeno at On request.
Does i2c or Vodeno run on more platforms?
i2c runs on Web, REST API. Vodeno 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 Vodeno is typically brought in for.
What can i2c do that Vodeno cannot?
i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. Vodeno covers Core banking infrastructure, Card issuance via Mastercard, Lending and BNPL modules, White-label mobile apps.

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.

Vodeno: Does Vodeno hold its own banking licence?

No, it operates through partner banks, Aion Bank in continental Europe and NatWest in the UK.

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.

Vodeno: Is the UK business the same as the European business?

They are related but distinct entities backed by different bank partners, with different investment structures.

i2c: Is it self-serve?

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

Vodeno: How much has NatWest invested?

A capped commitment of up to roughly £120 million into the UK entity, plus a separate roughly €58 million investment in Vodeno Group for an 18% stake.

Share

Related pages

More on i2c

More on Vodeno

Keep looking

Other head to heads