APIs · head to head
Enfuce vs Trustly

Enfuce
APIs
European issuer processor holding its own payment institution licence
- From
- On request
- Rated
- -

Trustly
APIs
Pay-by-bank payments network, majority-owned by private equity firm Nordic Capital
- 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.; Trustly it is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
- They diverge on capability: Enfuce covers Licensed issuing, Trustly covers Pay by bank checkout.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Enfuce and Trustly 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 Trustly
- Pay by bank checkout
- Instant refunds
- Verified payouts
- Multi-market bank connectivity
- Merchant dashboard and reconciliation
- Fraud and risk tooling
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 Trustly
- A corporate issuing fuel or expense cards across several EU countries on one programmenot Trustly
- A bank migrating an existing European card portfolio off a legacy processornot Trustly
- A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot Trustly
Trustly
- An e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptancenot Enfuce
- A gaming or gambling operator needing verified, instant payouts to players' bank accountsnot Enfuce
- A merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delaysnot Enfuce
- A business in a market with strong open banking adoption wanting pay-by-bank as a checkout optionnot 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.
Trustly
- It is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
- Consumer familiarity with paying by bank transfer still lags card payments in most markets, so merchants typically see it used as a secondary option rather than a full card replacement.
- The 1.15 to 3.15% merchant fee range is not a single published rate, so a merchant cannot know its actual cost without a sales negotiation.
- As with all open banking-dependent payment methods, reliability depends on the consistency of the underlying banks' own APIs, which Trustly does not control.
- Its verified payout functionality is heavily used in gaming and gambling, a sector with additional regulatory scrutiny, which is worth factoring in when evaluating vendor risk exposure by association.
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
Trustly
On request- Trustly$undefined/month
- Typical merchant cost of 1.15% to 3.15% depending on volume and market
- Exact rate negotiated per merchant, not published as a flat card
Which should you pick?
Choose Enfuce if
- You need licensed issuing.
- You work on Web, REST API.
- You also want card processing.
Choose Trustly if
- You need pay by bank checkout.
- You work on Web, API.
- You also want instant refunds.
Questions people ask
- Is Enfuce or Trustly better?
- Neither clearly leads. Enfuce starts at On request and Trustly at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Enfuce or Trustly?
- Enfuce starts at On request and Trustly at On request.
- Does Enfuce or Trustly run on more platforms?
- Enfuce runs on Web, REST API. Trustly 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 Trustly is typically brought in for.
- What can Enfuce do that Trustly cannot?
- Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity.
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.
Trustly: Who owns Trustly?
Nordic Capital, a private equity firm, holds a 51.1% majority stake; Alfven & Didrikson and BlackRock hold smaller stakes.
Enfuce: Which regions does it cover?
Europe. It is not a route to issuing cards in the United States or Asia.
Trustly: Is Trustly going public?
It has discussed an IPO but as of its most recent comments said one remained at least a year away.
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.
Trustly: What does it typically cost a merchant?
Roughly 1.15% to 3.15% of transaction value depending on volume and market, negotiated per merchant.
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 Thredd
- 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 Yapily
- Enfuce vs Aiia
- Enfuce vs Swan
- Enfuce vs Volt
- Enfuce vs TrueLayer
- Enfuce vs Token.io
- Enfuce vs Brite Payments
- Enfuce vs Dwolla
- Enfuce vs Zimpler
- Enfuce vs Stainless
- Enfuce vs Strapi
- Enfuce vs Swagger/OpenAPI
- Enfuce vs Thunder Client
- Enfuce vs Toqio
- Trustly vs Marqeta
- Trustly vs i2c
- Trustly vs Weavr
- Trustly vs Tink
- Trustly vs Paymentology
- Trustly vs Highnote
- Trustly vs Lithic
- Trustly vs Thredd
- Trustly vs Episode Six
- Trustly vs Tribe Payments
- Trustly vs Enable Banking
- Trustly vs Salt Edge
- Trustly vs Skyflow
- Trustly vs Yodlee
- Trustly vs Backbase
- Trustly vs Griffin
- Trustly vs Stoplight
- Trustly vs Yapily
- Trustly vs Aiia
- Trustly vs Swan
- Trustly vs Volt
- Trustly vs TrueLayer
- Trustly vs Token.io
- Trustly vs Brite Payments
- Trustly vs Dwolla
- Trustly vs Zimpler
- Trustly vs Stainless
- Trustly vs Strapi
- Trustly vs Swagger/OpenAPI
- Trustly vs Thunder Client
- Trustly vs Toqio
