Beeqeeper

A core payment platform, delivered as SaaS

Beeqeeper runs the front and back office of a payment business. Multi currency fiat and crypto accounts, payments, AML controls, treasury and supervisory reporting in one system, delivered as SaaS under your brand.

Built for

Whether you are launching a new product or expanding across regions, the core backend can stay in place.

Neobanks

Launching multi currency wallets and client facing apps on rails that already exist.

Crypto banks

Fiat and digital assets in one place, with AML controls on both.

Payment hubs

High volume flows across currencies and rails, with treasury automation behind them.

Modules

Thirteen admin sections behind one interface. Grouped here by what they do for the business.

Accounts and clients

The client core: entities, people and their money.

Multi currency client accounts with IBANs or virtual account numbers
KYC registry of persons with validation queues and document expiry tracking
Individual and corporate entity types with their own plans
Crypto addresses bound to accounts
Instant account number pool for incoming payments

Payments and operations

Every request passes rules and approval before it touches the ledger.

One queue for deposits, withdrawals and exchanges with 18 filters
Approval flow with AML status and risk level on every row
Ledger of executed transactions with request traceability
Historical import with templates, validation and preview
Transit transactions and external trader or OTC orders

Crypto

Digital assets as first class citizens, not an add-on.

BTC, ETH, LTC, TRX and USDT on ERC20 and TRC20
Direct blockchain node access, confirmed on Bitcoin Core
One ticker in several networks, USDT included
On-chain transactions visible from the back office
Fiat and crypto on- and off-ramps within one account structure

Exchange

An internal exchange, not a widget.

Offers and orders with market matching
Rate registry: external FX feed, cross rates and manual corrections
Per-entity rates for individual pricing
A journal of every executed conversion

AML and compliance

End to end: from a rule firing to a report for the regulator.

Configurable rule inspectors on the transaction flow, with their own log
Risk factors and scoring, AML check queue for new clients and payments
Case management: issues opened from inspector hits
Compliance officer comments and AML reports
External AML systems connect as pluggable services

Treasury and reconciliation

The money side runs itself until a limit is crossed.

Operational funds per currency and bank
Auto accept and auto send limits, manual approval above them
Balance control rules rebalance liquidity between funds
Daily report: client liabilities vs bank balances vs business funds, per currency

Fees and billing

Pricing at any level of detail.

Atomic fees: fixed points plus percent with min and max
Fee plans per currency and transaction type, copyable
Per-account overrides for special clients
Payment methods with limits per transaction and per day
Configurable referral program with bonus journal

Reporting, audit and back office

What the supervisor, the auditor and the operator each need.

Czech National Bank messages generated from approved records
Full audit log of operator actions with hashed attached files
Central file storage: KYC documents, exports, AML reports, one table
Two factor authentication over SMS and Google Authenticator
Notifications through pluggable providers, SMS via Twilio

Inside the admin

Screens from the demo instance, demo data blurred. The structure is what production looks like.

The requests queue: every deposit, withdrawal and exchange with its AML status, risk level and approval state.

Daily reconciliation: client liabilities against operational funds and business funds, currency by currency.

The AML check queue: new clients and payments waiting for review.

How a transaction moves

Every client request follows the same path before it becomes a record.

Request

A client submits a deposit, withdrawal or transfer in the front office.
Rule inspectors

Configurable inspectors check the request on the transaction flow.
AML queue

Risk factors and scoring, compliance officer comments, case management when something needs a closer look.
Approval

An operator approves the request in the approval flow before anything posts.
Ledger

The record lands in the ledger. Fiat and crypto share one account structure.

Who works in it

One platform, four kinds of users.

Your clients

Front office under your brand: accounts, payments and the internal exchange.

Operators

Approval flows, treasury, client requests. Two factor sign in over SMS or Google Authenticator.

Compliance officers

The AML queue, risk scoring, case management and AML reports.

Administrators

Configuration, roles, limits and the full audit log of operator actions.

Integrations

The platform connects to banks, exchanges and compliance services through adapters. More than twenty run in production today. A new provider is an adapter, not a fork of the platform.

Banking rails: National payment systems for SEPA payments, each connection with its own message journal.
Crypto infrastructure: Exchanges, custody providers and direct blockchain nodes for the supported networks.
Identity and compliance: KYC verification, sanctions and PEP screening, on-chain analytics.
Money remittance: Remittance networks and cash processing for payout corridors.
Messaging and rates: SMS notification providers and external FX rate feeds.

One screen of configuration

Brand, logo, SMTP, legal details and bank accounts of an instance are configuration, not code. Verification and audit modes switch on the same screen. One deployment serves one client under their own name.

Security and operational resilience

Built to operate under the requirements of regulated financial clients.

DORA alignment

We work as an ICT third party provider: we mirror the resilience duties of our financial clients and cover them contractually under Article 30.
Access and audit

Two factor authentication over SMS and Google Authenticator, role based access, and a full audit log of operator actions with hashing of attached files.
Hosting and source code

The platform is hosted in the Czech Republic, inside the EU data protection perimeter. Source code stays with us; delivery is SaaS only.

How Beeqeeper is delivered

Implementation first, then a monthly subscription.

SaaS, not a code drop

We run the instance. The client gets a configured system under their own brand, legal details and bank account.
Demo first, then production

We deploy a demo environment before go-live, so you review the configuration and interface on real screens. Production follows quickly: your instance is configured and deployed, not built from scratch.
Implementation and subscription

A one-off implementation fee, then a monthly subscription. Tiers are set by monthly transaction volume.
Custom work on top

Modules specific to a licence or a bank are scoped separately. A rough estimate first, then a fixed scope specification with dates.

A startup offer

Early-stage fintechs get separate terms. For qualifying companies, two things change:

Deferred deployment payment

We deploy the platform with the setup fee deferred. You go live first and pay for the deployment later.

No monthly minimum at the start

For the first months you pay only for executed transactions. The monthly subscription starts once your volumes do.

Whether your case qualifies depends on your stage and setup. Write to us and describe where you are; we will answer with the terms that apply.

Ask about the startup offer

Ask for a walkthrough

Write to us with the setup you are running or planning. We will walk you through the admin interface and say what your case needs on top.