Flaem integrations: payments, e-invoicing, domains and DDoS protection in one panel
Payment gateways, Polish KSeF e-invoicing, domain registrars, DDoS protection providers, SMS and Discord are connected with keys in the admin panel, each integration on its own. The setup checklist shows which ones are still missing, and if you are staying with WHMCS, Blesta, HostBill or Paymenter, Flaem connects to them through the billing bridge.

- 7payment gateways, three of them with BLIK in the panel
- 4DDoS protection providers to connect
- 6notification channels for clients and your team
- 44webhook event types for your own systems
Seven payment gateways and BLIK typed straight into the panel
Clients pay by card, bank transfer, BLIK, PayPal account, paysafecard code, SMS or cryptocurrency. You turn a gateway on with the keys from your own contract with the payment provider, and in the same transaction the payment issues the invoice and starts or renews the service.
BLIK without leaving the store
- 01Code from the banking appWith Przelewy24, Tpay and PayU the client types the six-digit BLIK code in the panel, without going to the gateway's page.
- 02Approval in the bankThey approve the payment in their banking app and stay in your store the whole time.
- 03Invoice and serviceThe invoice is created in the same transaction, and the service goes off to be set up.

Which payment method comes from which gateway
- Card
- Bank transfer
- BLIK in the panel
- PayPal account
- Prepaid code
- Premium SMS
- Cryptocurrency
- StripeAny currency Stripe supports
- Przelewy24PLN, EUR, GBP and CZK
- TpayPLN
- PayU11 currencies, including PLN, EUR and USD
- PayPal11 currencies, including PLN, EUR and USD
- paysafecard10 currencies, including PLN and EUR
- SimPayPLN, no refunds through the gateway
- BTCPay ServerPaid straight into your own wallet
Lines connect each payment method to the gateways that offer it. BTCPay Server works alongside the seven gateways, on your own server.
- Test mode first
- Every gateway starts in test mode so that the first real payment does not arrive by mistake. Going live requires entering the keys again.
- Encrypted keys
- Gateway keys are encrypted in the database and the panel never shows them again.
- Saved Stripe cards
- A card is only a gateway token, the brand and the last four digits. When a renewal charge fails, Flaem retries on the due date, after 3 days and after 7 days.
- Refunds through the gateway
- Full and partial, in every gateway except SimPay. A refund made directly in the gateway is recorded in Flaem as well.
KSeF e-invoicing, VIES, NBP rates and the JPK file without retyping invoices
The invoice is created at the moment of payment, and the FA(3) file goes to KSeF, the Polish national e-invoicing system, from a background queue, so a KSeF outage never blocks a sale or a renewal. VIES checks the VAT number, the exchange rate comes from the NBP table, and when the month closes you get a package for your accountant.
- 01PaymentA gateway, a saved card or the wallet balance
- 02FA(3) invoiceXML from the same record as the client's PDF
- 03Background queueChecked every 60 seconds, each document sent once
- 04KSeFA KSeF token in the context of the seller's tax ID
- 05KSeF numberSaved with the invoice, or a rejection with the reason
Before the invoice reaches the queue
- VIES
- The VAT number of an EU business is checked at the sale, and the reverse charge needs a confirmation no older than 30 days.
- NBP
- An invoice in a foreign currency gets the average rate from table A of the last business day before the tax point, with the table number.
- OSS
- Sales to consumers in other EU countries are counted in euro, and above 10,000 EUR the invoice uses the client's country rate.
When KSeF does not answer
- 1 min
- 5 min
- 15 min
- 30 min
- hourly
- alert with the reason
The queue retries less and less often, and after the twelfth failed attempt every administrator gets an alert with the invoice number and the reason.

What your accountant gets every month
When the month closes you get a notice that the settlement is ready, and you download one package with the reports and the JPK file.
Reports in the package
- Revenue
- MRR
- Unpaid invoices
- Refunds
- Reseller commissions
- Node profitability
- Services
- Wallet liabilities
CSV, XLSX and PDF/The JPK file is built from the same documents you see in the panel, so the reports and the file always match.
- Corrections and advances
- A correction points to the corrected invoice with its KSeF number and gives the reason. An advance invoice documents a payment for a named service before it is delivered.
- Reseller KSeF
- A reseller sends invoices with their own token, in the context of their own tax ID and through their own queue.
Domain registrars with a fallback order and full support for .pl
The client searches for and registers a domain in your store, and Flaem talks to the registrar you buy it through. For every extension you set an order of accounts: when the first one does not answer, the registration goes through the next.
.pl domains through Polish registrars or straight at NASK
With the same actions in the client panel as any other domain: renewal, transfer with a code, transfer lock, WHOIS privacy, name servers, DNSSEC and glue records.
After the purchase: DNS zone and email
- PowerDNSClient DNS zones, with a record editor in the client panel.
- CloudflareThe domain's zone run in Cloudflare instead of PowerDNS.
- mailcowMailboxes on servers from the pool, with DKIM, SPF and DMARC records added to the zone automatically.
Domains you already hold in a registrar account are taken over into Flaem and assigned to clients.
- Openprovider
- AfterMarket.plwith DNSSEC1connecting
- ResellerCluband other LogicBoxes brands
- CentralNic
- OVHcloud
- Namecheap
- Porkbun
- domeny.tv3next in line
- NASKdirectly, for .pl domains2next in line
An example setup. You choose the accounts and their order for every extension.
A registrar that is not on the list connects in one of 3 ways
- API described in a formYou describe the registrar's API in the panel, without writing code.
- Your own bridgeYou run a bridge that translates Flaem commands into the registrar's API.
- EPP straight to the registryAs an accredited registrar you connect to the registry directly.
DDoS protection at your provider, set up for every service
Attack traffic is scrubbed in your protection provider's network before it reaches your uplink. Flaem connects that protection, sets filters for every service and shows clients the attacks on their addresses.
Providers you connect in the panel
- Path.netA game-profile filter on the server's main port, a plain filter on additional ports and on ports the client adds, rules for single addresses and attack history in the panel.
- OVHGame profiles, Minecraft Bedrock included, Edge Firewall rules and mitigation profiles on server ports. Ongoing attacks show up in the panel.
- Cloudflare Magic TransitCloudflare announces your prefix over BGP, scrubs the traffic in its network and hands it back over a GRE or IPsec tunnel. You switch the announcement on and off from the panel.
- NeoProtectDDoS protection as a provider service, connected to your addresses and run from the same panel as the other providers.

You set up
- Provider keys in the admin panel, each integration on its own
- A game filter for a port range, for example Minecraft on ports 25000 to 26000, reported to the protection provider
- Route objects in the RIPE database and route validation with RPKI
- Blackhole at your uplink provider and FlowSpec rules at the upstream operator
The client sees
- Reports of attacks on their own addresses, without opening a ticket
- A server that gets a port from the range behind its game's filter on its own
- Ports they add themselves behind a plain filter

Import from WHMCS, Pterodactyl, Convoy, Virtualizor and cPanel, always with a dry run
Flaem reads the old system through its API, its database or an account backup and shows a report first: what will be created, what will change and what cannot move. Nothing changes until you approve it.
- ReadThrough the panel API, the database or an account backup.
- Dry run reportWhat will be created, what will change and what cannot move.
- ImportImports from WHMCS, Convoy and Virtualizor can be rolled back.
- PricingMoved plans wait inactive at a price of 0, so nobody gets an invoice or a suspension by mistake.
What moves from each system
- stays on its hardware
- moves to Proxmox VE
- data and definitions
Billing
- WHMCSClients, balance into the wallet, renewal dates and amounts, invoices as an archive and saved Stripe cardsBilling data only, servers untouched
Game panels
- PterodactylUsers, nodes, port allocations, eggs, plans and servers with their IDs keptWings node taken over in place
- PelicanEggs from a file, a URL or a GitHub repositoryField-by-field preview of each definition
VPS panels
- ConvoyMachines with the same VMID, users, plans and IP addressesOn the same Proxmox, no restart
- VirtualizorProxmox mode machines and KVM machinesProxmox mode in place, KVM in your maintenance window
- SolusVM, VirtFusion and VMware ESXiVirtual machines, each listed in the dry run reportMoved onto Proxmox VE nodes
Web hosting
- cPanel and DirectAdminSites, domains and zones, mailboxes with forwarders, MySQL databases and filesFrom an account backup, not a live server
Stay with WHMCS, Blesta, HostBill or Paymenter while Flaem runs the servers
You add the Flaem module to your billing system like any server module. That system stays the owner of the client, the money, the term and collections, and Flaem creates, suspends and changes services through the bridge API.
- OrderThe client orders and pays as before.
- Create servicePOST /servicesFlaem links the client to a panel account, creating it from their email the first time, and sets the service up on a node.
- Log in to panelPOST /services/{id}/ssoA one-time login link is created at the moment of the click, for the client and for the administrator.
- UsageGET /services/{id}/usageA daily cron records disk and transfer usage. When there is no measurement, the service is skipped rather than set to zero.
- SuspendPOST /services/{id}/suspendA missed payment stops the service with the reason and note from the billing system. The data stays untouched.
- Callbacksigned, https onlyA suspension or cancellation in the Flaem panel goes back to the billing system, so both show the same thing.
Where the module goes
- WHMCSServer module, one zip archive with a SHA-256 checksum for every Flaem release
modules/servers/flaem - BlestaServer module and the flaem_bridge plugin for callbacks
components/modules/flaem - HostBillHosting module
includes/modules/Hosting/flaem - PaymenterServer extension
extensions/Servers/Flaem
- No second server by mistake
- Every change carries a key made of the service number and the operation, so a job retried after a timeout never builds a second machine.
- No invoices on the Flaem side
- A bridge service gets no invoices, renewals or non-payment suspensions in Flaem. Your system handles those.
- A separate bridge key
- The key has a single scope the regular API does not accept, and a default limit of 600 requests per minute.

Six notification channels, sent through your own providers
Invoices, outages, approaching limits and ticket replies reach the client wherever they choose, and alarms reach your on-call person. Every event can also fire a webhook to your own system.
- In the panel
- FlaemNotifications in the client panel and in the operator panel.
- Your SMTP serverHTML emails in your brand colours, with the text of every message editable in every language.
- SMS
- Twilio, SMSAPI or SerwerSMSTwilio sends worldwide, SMSAPI and SerwerSMS within Poland.
- Push
- Browser, APNs and FCMIn the browser and in the iOS and Android apps.
- Telegram
- Telegram botMessages from the bot, for clients and for your team.
- Discord
- Your Discord applicationAlerts in the client's server channel and issues in your team's channel.
- Clients pick the channels
- The client sets categories and channels, tests a channel and confirms the address.
- Delivery log
- Every send attempt is recorded, failed ones are retried, and a target that keeps failing is switched off with the reason.
- On-call with escalation
- An alarm goes to the on-call person, and without an acknowledgement it climbs the ladder until someone takes it.
- Templates in 5 languages
- You and your resellers edit every message, with a preview and a test send.
Discord as a second panel: tickets in threads, a bot under your brand and client roles
The bot runs on your own Discord application, so your brand speaks on your clients' servers. Your team answers tickets straight from Discord, and clients get alerts about their servers in their own channels.
Servers, backups and invoices, with live server status.
- A new ticket opens a threadA new ticket opens a thread
- Every later message lands in the threadEvery later message lands in the thread
- A reply on Discord goes back to the ticketA reply on Discord goes back to the ticket
A message that came from Discord never goes back to Discord a second time.
If the webhook stops working, the client can still send the ticket, and your screen says plainly that the bridge is down.
On your team's Discord
- New orders in the team channel
- Every ticket as a thread, with replies going back to the panel
- Live server status and outage alerts
On the client's Discord server
- An outage alert channel with the cause, a console link and optionally the last lines of the log
- At most 3 alerts an hour by default, so the channel does not turn into spam
- A status card that changes when the server starts, stops or crashes
Roles given on your server
client former client active client service type node
A client with a node role gets notices on Discord about maintenance on their node.
Sign in with Google, GitHub, Discord or Steam, and fraud screening before a server starts
Clients sign in with an account they already have, and you switch each sign-in provider on separately. Before an order starts a server, fraud screening scores it, and captcha protects the forms.
External sign-in
- GitHub
- Discord
- SteamA Steam account confirms its email before the first purchase
- OpenID ConnectAny identity provider
Captcha. Cloudflare Turnstile or hCaptcha at sign-up and in selected places of the panel.

Every order scored before anything starts
- AcceptThe order carries on as usual.
- ReviewThe payment, invoice and service are recorded, and only the delivery waits until someone on your team decides.
- RejectThe buyer gets a refusal code and a case number. Only your team knows the reasons.
Mods, plugins and modpacks from the catalogues players already know
The client searches for a plugin or a mod in the panel and installs it in one click, without hunting for files or uploading them over SFTP. You decide which catalogues are switched on.
Minecraft
- ModrinthMods, plugins and modpacks
- CurseForgeModpacks in one click
- HangarThe PaperMC plugin catalogue
- SpigotMCPlugins for Spigot and Paper
- GeyserMCGeyser and Floodgate for Bedrock players
Steam games and Thunderstore
- Steam WorkshopMods and collections, for example in Garry's Mod
- ThunderstoreGame mods installed from the panel
- Updates from SteamA new game version with one button
How a plugin reaches the server
Backups to S3 storage, SFTP, Proxmox Backup Server and the client's own drive
Where each plan's backups go is set in the wizard when you add a node or a plan. The further from the service a backup lies, the bigger the failure it survives, and the client can add their own cloud drive.
- On the nodeThe service node's disksurvives an error inside the client's system
- On a separate diskFor example a large HDDsurvives a failure of the machine's disk
- Off the nodeS3, SFTP or Proxmox Backup Serversurvives the loss of the whole node
- In a second locationA backup VPS copy sold as an add-onsurvives a problem with the whole data centre
Off the node, you choose "only there" or "here and there".
- The client's cloud drive
- The client connects their cloud account, and backups of their services land there too, next to yours.
- Backup of the whole installation
- Every day at a chosen hour, to a separate disk or S3-compatible storage, apart from client backups.
- S3 as your product
- You can also sell S3-compatible storage to clients, with buckets and keys created in their panel.
Anything not on this list connects through the API, 44 webhooks, Terraform or MCP
The public API with keys and scopes, signed webhooks, the TypeScript client, Terraform, the command line tool and an AI assistant over MCP all use the same keys, limits and usage log.
- REST API v1
- OpenAPI 3.1 documentation in every installation, scoped keys, a per-minute request limit and allowed addresses.
- TypeScript client
- Generated from the installation's OpenAPI description, so a call to an endpoint that does not exist simply does not compile.
- Terraform and the command line
- Clients describe their services in Terraform files and see the plan before a change, and run everyday operations from the terminal.
- AI assistant over MCP
- Claude or another MCP-compatible assistant gets 23 tools and exactly the permissions its key has.
A webhook on its way to your system
- Attempt 1delivered
- after 30 s
- after 2 min
- after 5 min
- after 15 min
- after 1 h
The HMAC-SHA256 signature covers the timestamp and the body, so the receiver spots a forgery and an old event replayed.
After 20 failed deliveries in a row the address is switched off with the reason.
Questions about integrations
Keys, contracts with providers, the licence and what to do when something is not on the list.
In the admin panel, separately for each integration. The setup checklist shows which ones are still missing, and payment gateway keys are encrypted in the database and never shown by the panel a second time.
Yes. Flaem connects to your accounts: you turn a payment gateway on with the keys from your contract with its provider, register domains through your own registrar accounts and send SMS through your own provider account.
You connect it by describing its API in a panel form, without writing code, with your own bridge or, as an accredited registrar, over EPP straight to the registry.
Yes. The modules for WHMCS, Blesta, HostBill and Paymenter add Flaem as the service panel, while money and invoices stay in your system. You move to full Flaem later, one service at a time.
Sales carry on, because the invoice waits in a background queue. The queue retries after 1, 5, 15 and 30 minutes, then every hour, and after the twelfth failed attempt administrators get an alert with the reason.
Attack traffic is scrubbed in your protection provider's network: Path.net, OVH, Cloudflare Magic Transit or NeoProtect. Flaem sets the filters for services and shows clients attack reports, and on the node you can also switch on the kernel filter.
You pay for options, not integrations. DDoS protection costs $10 and domains with DNS $10 a month, however many providers and registrars you connect. Payment gateways, KSeF, notification channels, sign-in and bridge modules come with the base.
Missing something on the list?
Tell us what you use today. The REST API and webhooks connect Flaem to any system, and if an integration will help other operators too, we will add it to the product.
