APIs · head to head
Enfuce vs Thredd
Enfuce
APIs
European issuer processor holding its own payment institution licence
- From
- On request
- Rated
- -
Thredd
APIs
Issuer processing platform for fintechs and digital banks, formerly Global Processing Services
- From
- On request
- Rated
- -
The short version
- Each has a real cost: Enfuce coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.; Thredd pricing is entirely unpublished, so cost comparison against competing processors requires a sales process.
- They diverge on capability: Enfuce covers Licensed issuing, Thredd covers Issuer processing.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Enfuce and Thredd actually diverge.
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 Enfuce
- Licensed issuing
- Card processing
- Tokenisation
- Spend controls
- Multi-currency programmes
- Carbon and data services
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.
Enfuce
- A European fintech launching cards without spending two quarters finding a sponsor banknot Thredd
- A corporate issuing fuel or expense cards across several EU countries on one programmenot Thredd
- A bank migrating an existing European card portfolio off a legacy processornot Thredd
- A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot Thredd
Thredd
- A digital bank or fintech needing issuer processing across many countries under one contractnot Enfuce
- A BNPL, lending or crypto product needing certified card processing behind its own brandnot Enfuce
- A company that finds outdated Global Processing Services (GPS) material and needs to confirm it is now Threddnot Enfuce
- An embedded finance platform wanting a processor already integrated with core banking systems such as Mambunot Enfuce
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Enfuce
- Coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
- Where Enfuce acts as the licensed issuer it takes on regulatory risk and prices accordingly, so the convenience of skipping a sponsor bank is not free.
- European interchange caps limit programme revenue far below US levels, so business cases imported from a US card model do not survive the move.
- It is a smaller supplier than Marqeta or i2c, which means less negotiating room on scheme fees and a thinner partner ecosystem around it.
- Pricing is entirely quoted with monthly minimums, so low-volume programmes carry a fixed cost that does not scale down with a slow launch.
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
Enfuce
On request- Enfuce issuing and processing$undefined/year
- Per-active-card and per-transaction fees with monthly minimums
- Higher pricing where Enfuce acts as licensed issuer rather than processor only
- Interchange arrangements depend on who holds the issuing licence
Thredd
On request- Thredd$undefined/year
- Volume and programme-based pricing, not published
- Custom quote required via sales
Which should you pick?
Choose Enfuce if
- You need licensed issuing.
- You work on Web, REST API.
- You also want card processing.
Choose Thredd if
- You need issuer processing.
- You work on Web, API.
- You also want multi-country reach.
Questions people ask
- Is Enfuce or Thredd better?
- Neither clearly leads. Enfuce 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, Enfuce or Thredd?
- Enfuce starts at On request and Thredd at On request.
- Does Enfuce or Thredd run on more platforms?
- Enfuce runs on Web, REST API. Thredd runs on Web, API.
- What is Enfuce best used for?
- Enfuce is most often used for a european fintech launching cards without spending two quarters finding a sponsor bank, a corporate issuing fuel or expense cards across several eu countries on one programme, a bank migrating an existing european card portfolio off a legacy processor, a programme that must report cardholder transaction carbon data to meet sustainability commitments. Of those, a european fintech launching cards without spending two quarters finding a sponsor bank and a corporate issuing fuel or expense cards across several eu countries on one programme are not what Thredd is typically brought in for.
- What can Enfuce do that Thredd cannot?
- Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls. Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.
Answered from the vendors’ own pages
Enfuce: Do I need my own licence to use Enfuce?
Not necessarily. Enfuce holds Finnish payment institution authorisation and can act as issuer, or process under your own licence if you have one.
Thredd: Is Thredd the same company as Global Processing Services?
Yes, GPS rebranded as Thredd in 2023; it is the same company and platform.
Enfuce: Which regions does it cover?
Europe. It is not a route to issuing cards in the United States or Asia.
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.
Enfuce: How does interchange work?
Who holds the issuing licence determines who receives interchange, so the licensing choice and the revenue model are the same decision.
Thredd: Is pricing published?
No, it requires a sales conversation.
Related pages
Other head to heads
- Enfuce vs Marqeta
- Enfuce vs i2c
- Enfuce vs Weavr
- Enfuce vs Tink
- Enfuce vs Paymentology
- Enfuce vs Highnote
- Enfuce vs Lithic
- Enfuce vs Episode Six
- Enfuce vs Tribe Payments
- Enfuce vs Enable Banking
- Enfuce vs Salt Edge
- Enfuce vs Skyflow
- Enfuce vs Yodlee
- Enfuce vs Backbase
- Enfuce vs Griffin
- Enfuce vs Stoplight
- Enfuce vs Unit
- Enfuce vs Treasury Prime
- Enfuce vs Synctera
- Enfuce vs Toqio
- Enfuce vs Yapily
- Enfuce vs Swan
- Enfuce vs Temenos Transact
- Enfuce vs Token.io
- Thredd vs Marqeta
- Thredd vs i2c
- Thredd vs Weavr
- Thredd vs Tink
- Thredd vs Paymentology
- Thredd vs Highnote
- Thredd vs Lithic
- Thredd vs Episode Six
- Thredd vs Tribe Payments
- Thredd vs Enable Banking
- Thredd vs Salt Edge
- Thredd vs Skyflow
- Thredd vs Yodlee
- Thredd vs Backbase
- Thredd vs Griffin
- Thredd vs Stoplight
- Thredd vs Unit
- Thredd vs Treasury Prime
- Thredd vs Synctera
- Thredd vs Toqio
- Thredd vs Yapily
- Thredd vs Swan
- Thredd vs Temenos Transact
- Thredd vs Token.io