APIs · head to head
Treasury Prime vs Zimpler
Treasury Prime
APIs
Banking as a service platform sold to sponsor banks rather than to fintechs
- From
- On request
- Rated
- -
Zimpler
APIs
Nordic and Brazilian account-to-account payments for regulated high-risk sectors
- From
- On request
- Rated
- -
The short version
- Each has a real cost: 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.; Zimpler pricing is not published and is set by industry and risk profile, so smaller merchants cannot benchmark a quote and often discover they are paying well above a general-purpose provider.
- They diverge on capability: Treasury Prime covers BankOS, Zimpler covers Bank payments.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Treasury Prime and Zimpler actually diverge.
| Attribute | Treasury Prime | Zimpler |
|---|---|---|
| Platforms | API, Web | Web, REST 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 Treasury Prime
- BankOS
- OneKey Banking
- Deposit accounts
- Payments
- Card issuing
- Bank oversight tooling
- Ledger and reconciliation
- Programme onboarding
Only in Zimpler
- Bank payments
- BankID identity
- Payouts
- Recurring payments
- Risk screening
- Brazil coverage
What people use each for
The jobs each tool is most often brought in to do.
Treasury Prime
- A community or regional bank that wants to run an embedded finance line with examiner-acceptable oversight of its fintech programmesnot Zimpler
- A fintech that has already chosen its sponsor bank and needs API access to that bank rather than to a middleware layernot Zimpler
- A company that wants deposits spread across several banks for FDIC coverage beyond a single institution limitnot Zimpler
- A bank replacing a fragile middleware arrangement with a structure where it holds the customer contract and the oversight obligationnot Zimpler
Zimpler
- A Swedish gambling operator needing deposit and verified identity in a single customer flownot Treasury Prime
- A Nordic merchant wanting instant bank payouts rather than card refundsnot Treasury Prime
- A trading platform where confirming account ownership before funding is a regulatory requirementnot Treasury Prime
- A European operator expanding into Brazil and wanting one provider across both marketsnot Treasury Prime
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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.
Zimpler
- Pricing is not published and is set by industry and risk profile, so smaller merchants cannot benchmark a quote and often discover they are paying well above a general-purpose provider.
- As a payment facilitator carrying merchant risk, it declines or offboards merchants on risk grounds, which makes it a dependency you cannot assume will persist.
- Its strength is concentrated in the Nordics, and coverage in southern and eastern Europe is thinner than pan-European account-to-account specialists.
- Revenue concentration in iGaming ties the provider to a sector under constant regulatory change, so licence changes in one market affect the supplier as well as the merchant.
- Bank transfers have no chargeback protection, so disputes are handled commercially and consumers used to card protections may resist the payment method.
Pricing, plan by plan
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
Zimpler
On request- Zimpler payments$undefined/year
- Per-transaction pricing quoted by industry, risk and volume
- Separate pricing for payouts and identity verification
- Merchant underwriting required, with sector restrictions
Which should you pick?
Choose Treasury Prime if
- You need bankos.
- You work on API, Web.
- You also want onekey banking.
Choose Zimpler if
- You need bank payments.
- You work on Web, REST API.
- You also want bankid identity.
Questions people ask
- Is Treasury Prime or Zimpler better?
- Neither clearly leads. Treasury Prime starts at On request and Zimpler at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Treasury Prime or Zimpler?
- Treasury Prime starts at On request and Zimpler at On request.
- Does Treasury Prime or Zimpler run on more platforms?
- Treasury Prime runs on API, Web. Zimpler runs on Web, REST API.
- What is Treasury Prime best used for?
- Treasury Prime is most often used for a community or regional bank that wants to run an embedded finance line with examiner-acceptable oversight of its fintech programmes, a fintech that has already chosen its sponsor bank and needs api access to that bank rather than to a middleware layer, a company that wants deposits spread across several banks for fdic coverage beyond a single institution limit, a bank replacing a fragile middleware arrangement with a structure where it holds the customer contract and the oversight obligation. Of those, a community or regional bank that wants to run an embedded finance line with examiner-acceptable oversight of its fintech programmes and a fintech that has already chosen its sponsor bank and needs api access to that bank rather than to a middleware layer are not what Zimpler is typically brought in for.
- What can Treasury Prime do that Zimpler cannot?
- Treasury Prime covers BankOS, OneKey Banking, Deposit accounts, Payments. Zimpler covers Bank payments, BankID identity, Payouts, Recurring payments.
Answered from the vendors’ own pages
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.
Zimpler: Which markets does Zimpler cover?
Sweden and the Nordics primarily, plus the wider EU and Brazil. It is strongest where national electronic identity schemes exist.
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.
Zimpler: Does it handle identity verification?
Yes. In the Nordics it captures BankID identity alongside the payment, which removes a separate verification step.
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.
Zimpler: Is pricing published?
No. It is quoted per merchant based on sector, risk and volume, and merchants must pass underwriting first.
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
- Treasury Prime vs Unit
- Treasury Prime vs Increase
- Treasury Prime vs Synctera
- Treasury Prime vs Griffin
- Treasury Prime vs Vodeno
- Treasury Prime vs Lithic
- Treasury Prime vs Fintech Farm
- Treasury Prime vs Weavr
- Treasury Prime vs Solaris
- Treasury Prime vs Thredd
- 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
- Treasury Prime vs Paymentology
- Treasury Prime vs Volt
- Treasury Prime vs TrueLayer
- Treasury Prime vs Trustly
- Treasury Prime vs Token.io
- Treasury Prime vs Neonomics
- Treasury Prime vs Brite Payments
- Treasury Prime vs Tink
- Treasury Prime vs Yapily
- Treasury Prime vs Dwolla
- Treasury Prime vs Sila
- Treasury Prime vs Moov
- Treasury Prime vs Fintecture
- Treasury Prime vs Kong
- Zimpler vs Unit
- Zimpler vs Increase
- Zimpler vs Synctera
- Zimpler vs Griffin
- Zimpler vs Vodeno
- Zimpler vs Lithic
- Zimpler vs Fintech Farm
- Zimpler vs Weavr
- Zimpler vs Solaris
- Zimpler vs Thredd
- Zimpler vs Swan
- Zimpler vs Mambu
- Zimpler vs Liveblocks
- Zimpler vs Moesif
- Zimpler vs Ozone API
- Zimpler vs Parse Server
- Zimpler vs Paw
- Zimpler vs Paymentology
- Zimpler vs Volt
- Zimpler vs TrueLayer
- Zimpler vs Trustly
- Zimpler vs Token.io
- Zimpler vs Neonomics
- Zimpler vs Brite Payments
- Zimpler vs Tink
- Zimpler vs Yapily
- Zimpler vs Dwolla
- Zimpler vs Sila
- Zimpler vs Moov
- Zimpler vs Fintecture
- Zimpler vs Kong