Softwr

APIs · head to head

i2c vs Thredd

i2c logo

i2c

APIs

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

From
On request
Rated
-
Full reviewWebsite
Thredd logo

Thredd

APIs

Issuer processing platform for fintechs and digital banks, formerly Global Processing Services

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.; Thredd pricing is entirely unpublished, so cost comparison against competing processors requires a sales process.
  • They diverge on capability: i2c covers Configurable product engine, Thredd covers Issuer processing.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which i2c and Thredd actually diverge.

Attributes where i2c and Thredd differ
Attributei2cThredd
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 Thredd

  • Issuer processing
  • Multi-country reach
  • Scheme certification
  • Programme support across verticals
  • High platform availability
  • Global office footprint

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

Thredd

  • A digital bank or fintech needing issuer processing across many countries under one contractnot i2c
  • A BNPL, lending or crypto product needing certified card processing behind its own brandnot i2c
  • A company that finds outdated Global Processing Services (GPS) material and needs to confirm it is now Threddnot i2c
  • An embedded finance platform wanting a processor already integrated with core banking systems such as Mambunot 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.

Thredd

  • Pricing is entirely unpublished, so cost comparison against competing processors requires a sales process.
  • The 2023 rebrand from GPS to Thredd means research under either name alone can miss relevant material, and partner or press references before 2023 will still say GPS.
  • Issuer processing does not include the banking licence itself, so a fintech still needs a separate BIN sponsor or bank partner, adding a second relationship to manage.
  • As shared infrastructure behind many fintech brands, an outage or processing delay at Thredd becomes a simultaneous incident for every programme running on it, with limited visibility for any single customer into root cause.
  • Its verticals span crypto, BNPL and remittance broadly, so depth of specialist support in any one vertical may be thinner than a processor focused narrowly on that niche.

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

Thredd

On request
  • Thredd$undefined/year
    • Volume and programme-based pricing, not published
    • Custom quote required via sales

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

  • You need issuer processing.
  • You work on Web, API.
  • You also want multi-country reach.
Thredd review

Questions people ask

Is i2c or Thredd better?
Neither clearly leads. i2c starts at On request and Thredd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, i2c or Thredd?
i2c starts at On request and Thredd at On request.
Does i2c or Thredd run on more platforms?
i2c runs on Web, REST API. Thredd 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 Thredd is typically brought in for.
What can i2c do that Thredd cannot?
i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.

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.

Thredd: Is Thredd the same company as Global Processing Services?

Yes, GPS rebranded as Thredd in 2023; it is the same company and platform.

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.

Thredd: Does it hold the banking licence for programmes it processes?

No, Thredd is the issuer processor; a separate bank or BIN sponsor holds the actual issuing licence.

i2c: Is it self-serve?

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

Thredd: Is pricing published?

No, it requires a sales conversation.

Share

Related pages

More on i2c

More on Thredd

Keep looking

Other head to heads