Treezor

Treezor provides Banking-as-a-Service for businesses embedding financial services through an API. Its services span payment accounts and wallets with virtual and local IBANs, core banking, KYC/KYB, card issuing and processing, acquiring, and SEPA and international payments. Businesses can arrange physical or virtual Visa or Mastercard programs linked to accounts, with configurable controls and limits. Treezor’s REST API accepts and returns JSON; each customer can use a dedicated sandbox for testing. A web dashboard supports onboarding teams and operations monitoring. Authentication options include WebNative for browsers and mobile devices, native iOS and Android SDKs, and bridges for React Native, Flutter, and Capacitor. Card services support Apple Pay, Google Pay, and Samsung Pay. Treezor identifies itself as an ACPR-authorized electronic money institution with authorization to operate in 25 countries. Its core solution is a white-label B2B service for fintechs, regulated institutions, and corporates. Pricing is on request. Listed regions include Belgium, France, Germany, Italy, Luxembourg, Spain, and The Netherlands.

Treezor brings accounts, payments, compliance, and card services together in an API-based B2B offering. Its scope and pricing on request make it a fit for organizations evaluating a tailored embedded finance setup.

Treezor suits fintechs, regulated institutions, and corporates that want to embed financial services through APIs. Businesses setting up a card program need to arrange it with Treezor.

Treezor is an embedded-finance and Banking-as-a-Service platform for companies building financial products into their own software. It is aimed at fintechs, regulated institutions, and corporates with the resources to manage a provider-led implementation. The breadth is valuable, but custom pricing and setup requirements make it less suitable for teams wanting an instant, self-serve banking product.

Overview

Treezor provides a REST API for services across the payment chain, including core banking, KYC/KYB, card issuing and processing, acquiring, and SEPA and international payments. Its BaaS, PaaS, CaaS, and SaaS offerings are complemented by a secure web dashboard for payment management. The result is infrastructure for embedding financial services rather than a finished consumer banking app.

Accounts and wallets can include virtual and local IBANs. Treezor says it is an ACPR-authorized electronic money institution with a European passporting license covering 25 countries. Its stated supported regions include Belgium, France, Germany, Italy, Luxembourg, Spain, and The Netherlands, giving businesses focused on those markets a defined regulatory footprint, though not worldwide coverage.

Key features

Accounts, payments, and compliance

Companies can build payment accounts and wallets, issue payments, collect funds for third parties, and run KYC processes. Core banking, ledger, KYC/AML tools, acquiring, and international payment capabilities cover the operational foundation many embedded-finance products need. This breadth favors organizations consolidating several financial functions with one provider; smaller teams may find the implementation scope heavier than required.

Card programs

Treezor supports physical and virtual Visa or Mastercard cards connected to accounts. Configurable controls and spending limits allow a business to shape card behavior for its product. A card program must first be established with Treezor, with account and implementation managers assisting, so launching cards involves coordination rather than a purely self-service workflow.

API, sandbox, and dashboards

The REST API uses JSON payloads. Every call must use HTTPS and carry a JSON Web Token in the Authorization header, while PCI DSS integration uses mutual TLS and encrypted endpoint communication. Each customer receives a free dedicated sandbox for testing, a practical advantage for teams that need an isolated integration environment.

A dashboard supports onboarding teams, and a customizable dashboard is available for monitoring operations. Card services integrate with Apple Pay, Google Pay, and Samsung Pay. WebNative authentication covers browsers and mobile devices, with native iOS and Android SDKs plus bridges for React Native, Flutter, and Capacitor, giving teams multiple implementation paths.

Acquiring and support

Card acquiring uses HiPay and is not enabled by default; customers must contact Treezor to activate it. For questions about an account, card, or IBAN powered by Treezor, the first support contact is the company that opened that account, which can add an extra layer between an end user and the infrastructure provider.

Pricing

Treezor uses custom pricing, with no public plan tiers or published subscription amounts. That model can make sense for regulated businesses negotiating a tailored program, but it prevents straightforward budget comparison and gives smaller buyers no transparent entry point. The free dedicated sandbox is for testing and should not be mistaken for a free production plan. Card-program setup and acquiring activation also require provider involvement, so implementation scope belongs in the commercial discussion.

Platforms

Treezor supports Android, iOS, web, and API deployments. Native mobile SDKs and bridges for React Native, Flutter, and Capacitor are useful when a product spans mobile and browser channels, while the REST interface suits backend-led integrations.

Who it's for

Treezor is a strong fit for fintechs, regulated institutions, and corporates that need white-label accounts, wallets, payments, compliance, and card programs in one European-oriented stack. It is particularly relevant when a team can work with implementation managers and wants a dedicated sandbox before production. Look elsewhere if you need published pricing, instant activation, or broad global reach without a provider-led setup.

Pros and cons

• Pro: Accounts, wallets, ledger, payments, KYC/AML, cards, acquiring, and international transfers are covered in one API-based platform.
• Pro: A dedicated free sandbox, mobile SDKs, framework bridges, and wallet integrations support serious product development.
• Pro: ACPR authorization and passporting across 25 countries provide a clear European operating context.
• Con: Custom pricing makes costs difficult to assess before a sales process.
• Con: Card programs require setup with Treezor, and acquiring is off by default, adding launch dependencies.
• Con: End-user support is routed through the company that opened the account, rather than directly through Treezor.

Alternatives

Compare the broader Banking-as-a-Service Platforms list when you want to survey the category. Unit is another paid API option, but card pricing, shipping, and order minimums depend on each program. Choose NymCard if self-hosted deployment matters alongside Android, iOS, web, and API support. Paynetics Card Issuing focuses on customizable physical and virtual Visa or Mastercard programs. Vodeno Cloud Platform is a paid alternative with Android, iOS, web, and API access. Mbanq Cloud uses a pay-as-you-grow model with infrastructure, support, and operational costs included. Modulr is worth considering if you prefer published tiers, including its Bronze plan at £30 a month with 80 payments included and £0.80 per extra payment. Weavr starts its Launch plan at £1,947 a month for approved B2B use cases in the EU and UK. Moov offers a Standard pricing plan at $500 a month minimum plus per-feature transaction fees.

Verdict

Choose Treezor when you need a broad, regulated European foundation for embedded accounts, payments, compliance, and card products and can support a managed implementation. Its strongest advantage is the unified API and operational stack; its main drawback is the lack of public pricing and the coordination required to launch card and acquiring services.