Softwr

APIs · head to head

i2c vs Marqeta

i2c logo

i2c

APIs

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

From
On request
Rated
-
Full reviewWebsite
Marqeta logo

Marqeta

APIs

Card issuing and transaction processing APIs with just-in-time funding

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.; Marqeta you still need a sponsor bank and a BIN, so the timeline and compliance burden of launching are set by a bank you must separately court and satisfy.
  • They diverge on capability: i2c covers Configurable product engine, Marqeta covers Just-in-time funding.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which i2c and Marqeta actually diverge.

Attributes where i2c and Marqeta differ
Attributei2cMarqeta

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web, REST 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 i2c

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

Only in Marqeta

  • Just-in-time funding
  • Virtual and physical issuing
  • Spend controls
  • Programme management tools
  • Multi-region issuing
  • Webhooks and ledger 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 Marqeta
  • An issuer in a market where local scheme and currency support rules out US-centric processorsnot Marqeta
  • A programme manager launching instalment products without building a lending corenot Marqeta
  • A credit union replacing an ageing processor without writing custom code for product rulesnot Marqeta

Marqeta

  • A delivery marketplace funding courier cards only at the moment a courier pays for the ordernot i2c
  • An expense platform issuing a virtual card per subscription with merchant locksnot i2c
  • A lender issuing a card that draws on an approved credit line rather than a stored balancenot i2c
  • A fintech wanting the same issuing stack across US and European programmesnot 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.

Marqeta

  • You still need a sponsor bank and a BIN, so the timeline and compliance burden of launching are set by a bank you must separately court and satisfy.
  • Pricing carries minimum monthly platform commitments, so a programme with modest card volume pays for capacity it never uses.
  • Programme revenue depends heavily on interchange, which means regulated debit interchange caps and European interchange caps materially change the business case by market.
  • Disputes, chargebacks and fraud losses sit with the programme, and teams that assumed the processor absorbed them discover a real operations headcount requirement.
  • Just-in-time funding makes your own authorisation endpoint a hard availability dependency; if it is slow or down, cards decline at the point of sale.

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

Marqeta

On request
  • Marqeta card issuing$undefined/year
    • Minimum monthly platform fee plus per-transaction and per-active-card charges
    • Interchange share negotiated between programme, processor and sponsor bank
    • Sponsor bank required, with its own fees and approval process

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

  • You need just-in-time funding.
  • You work on Web, REST API.
  • You also want virtual and physical issuing.
Marqeta review

Questions people ask

Is i2c or Marqeta better?
Neither clearly leads. i2c starts at On request and Marqeta at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, i2c or Marqeta?
i2c starts at On request and Marqeta at On request.
Does i2c or Marqeta run on more platforms?
Both run on Web, REST API, so platform support will not decide this one for you.
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 Marqeta is typically brought in for.
What can i2c do that Marqeta cannot?
i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. Marqeta covers Just-in-time funding, Virtual and physical issuing, Spend controls, Programme management tools.

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.

Marqeta: Do I need a sponsor bank?

Yes. Marqeta is an issuer processor, not a bank. Card programmes run on a sponsor bank BIN, and that bank approves and supervises your programme.

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.

Marqeta: How does the pricing really work?

A minimum monthly platform fee plus per-transaction and per-active-card charges, offset by a negotiated share of interchange. The interchange split is the substance of the deal.

i2c: Is it self-serve?

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

Marqeta: What is just-in-time funding?

Marqeta calls your endpoint at authorisation so you decide and fund each transaction, rather than pre-loading balances onto cards.

Share

Related pages

More on i2c

More on Marqeta

Keep looking

Other head to heads