APIs · head to head
Enfuce vs Treasury Prime

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

Treasury Prime
APIs
Banking as a service platform sold to sponsor banks rather than to fintechs
- 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.; Treasury Prime a fintech cannot buy Treasury Prime directly since the 2024 pivot, so the sales process starts with finding a sponsor bank willing to take your programme, which adds months and removes most of your negotiating leverage on fees.
- They diverge on capability: Enfuce covers Licensed issuing, Treasury Prime covers BankOS.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Enfuce and Treasury Prime actually diverge.
| Attribute | Enfuce | Treasury Prime |
|---|---|---|
| Platforms | Web, REST API | API, Web |
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 Treasury Prime
- BankOS
- OneKey Banking
- Deposit accounts
- Payments
- Card issuing
- Bank oversight tooling
- Ledger and reconciliation
- Programme onboarding
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 Treasury Prime
- A corporate issuing fuel or expense cards across several EU countries on one programmenot Treasury Prime
- A bank migrating an existing European card portfolio off a legacy processornot Treasury Prime
- A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot Treasury Prime
Treasury Prime
- A community or regional bank that wants to run an embedded finance line with examiner-acceptable oversight of its fintech programmesnot Enfuce
- A fintech that has already chosen its sponsor bank and needs API access to that bank rather than to a middleware layernot Enfuce
- A company that wants deposits spread across several banks for FDIC coverage beyond a single institution limitnot Enfuce
- A bank replacing a fragile middleware arrangement with a structure where it holds the customer contract and the oversight obligationnot 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.
Treasury Prime
- A fintech cannot buy Treasury Prime directly since the 2024 pivot, so the sales process starts with finding a sponsor bank willing to take your programme, which adds months and removes most of your negotiating leverage on fees.
- Commercial terms including minimum deposit balances, reserve requirements and per transaction pricing are set by the bank rather than the platform, so two fintechs on the same software can face materially different economics with no public benchmark.
- The company cut roughly half its staff in the 2024 pivot, which reduced the teams that supported fintech customers directly and left fintechs relying on their bank for support rather than on the vendor who wrote the software.
- Bank risk appetite is now the binding constraint, and after the Synapse failure sponsor banks decline programmes in higher risk categories that a middleware provider would once have onboarded, so some business models simply cannot get placed.
- If your sponsor bank exits the programme or is told by its regulator to reduce fintech exposure, you are migrating your entire deposit base to another institution, and the software being the same at both ends does not make that a small project.
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
Treasury Prime
On request- BankOS$undefined/year
- Sold to sponsor banks, not directly to fintechs
- Fintech commercial terms are set by the sponsor bank
- Minimum deposits, reserves and per transaction fees vary by bank
Which should you pick?
Choose Enfuce if
- You need licensed issuing.
- You work on Web, REST API.
- You also want card processing.
Choose Treasury Prime if
- You need bankos.
- You work on API, Web.
- You also want onekey banking.
Questions people ask
- Is Enfuce or Treasury Prime better?
- Neither clearly leads. Enfuce starts at On request and Treasury Prime at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Enfuce or Treasury Prime?
- Enfuce starts at On request and Treasury Prime at On request.
- Does Enfuce or Treasury Prime run on more platforms?
- Enfuce runs on Web, REST API. Treasury Prime runs on API, Web.
- 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 Treasury Prime is typically brought in for.
- What can Enfuce do that Treasury Prime cannot?
- Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls. Treasury Prime covers BankOS, OneKey Banking, Deposit accounts, Payments.
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.
Treasury Prime: Can a fintech buy Treasury Prime directly?
No. Since the 2024 pivot it sells to banks. A fintech contracts with a sponsor bank running BankOS, and the bank sets the terms.
Enfuce: Which regions does it cover?
Europe. It is not a route to issuing cards in the United States or Asia.
Treasury Prime: Why did it change model?
Regulatory pressure on the tri-party middleware structure, sharpened by the Synapse failure. Examiners want the bank holding the customer contract and the oversight obligation, which is what bank-direct means.
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.
Treasury Prime: What is OneKey Banking?
A way of spreading deposits across several banks in the network, used for FDIC coverage above a single institution limit and for resilience if one bank exits.
Treasury Prime: Is pricing published?
No, at neither the bank nor the fintech level. Fintech economics are set by the sponsor bank, so expect wide variation.
Related pages
More on Treasury Prime
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 Unit
- Enfuce vs Increase
- Enfuce vs Synctera
- Enfuce vs Vodeno
- Enfuce vs Fintech Farm
- Enfuce vs Solaris
- Enfuce vs Swan
- Enfuce vs Mambu
- Enfuce vs Liveblocks
- Enfuce vs Moesif
- Enfuce vs Ozone API
- Enfuce vs Parse Server
- Enfuce vs Paw
- Treasury Prime vs Marqeta
- Treasury Prime vs i2c
- Treasury Prime vs Weavr
- Treasury Prime vs Tink
- Treasury Prime vs Paymentology
- Treasury Prime vs Highnote
- Treasury Prime vs Lithic
- Treasury Prime vs Thredd
- Treasury Prime vs Episode Six
- Treasury Prime vs Tribe Payments
- Treasury Prime vs Enable Banking
- Treasury Prime vs Salt Edge
- Treasury Prime vs Skyflow
- Treasury Prime vs Yodlee
- Treasury Prime vs Backbase
- Treasury Prime vs Griffin
- Treasury Prime vs Stoplight
- Treasury Prime vs Unit
- Treasury Prime vs Increase
- Treasury Prime vs Synctera
- Treasury Prime vs Vodeno
- Treasury Prime vs Fintech Farm
- Treasury Prime vs Solaris
- Treasury Prime vs Swan
- Treasury Prime vs Mambu
- Treasury Prime vs Liveblocks
- Treasury Prime vs Moesif
- Treasury Prime vs Ozone API
- Treasury Prime vs Parse Server
- Treasury Prime vs Paw
