Building a white-label commission engine into an existing AI chatbot platform
How Integrated MLM Software's development team designed, configured, and API-connected a commission back office for BotFusion — without requiring BotFusion to change its own registration, checkout, or login experience.
CLIENT
BotFusion.co.uk
INDUSTRY
AI chatbot & automation SaaS
REGION
United Kingdom, with development based in Hungary
ENGAGEMENT
White-label platform deployment with custom API integration
An AI chatbot company that needed commission infrastructure, not a new product
BotFusion is a UK-based company with Hungarian roots that builds AI chatbots and automation tools for businesses — helping them automate customer service, sales conversations, and everyday workflow tasks. BotFusion runs a partner program, and approached Integrated MLM Software to build the commission tracking, payout, and back-office infrastructure that program needed to run.
BotFusion’s own product — the chatbot platform, registration flow, and checkout — was already built and working. The task for our development team was to add commission infrastructure underneath it without touching or replacing any of that existing experience.
A back-office system that had to disappear into an existing product
BotFusion’s core software is a chatbot and automation platform, not a commission-tracking system — building and maintaining multi-level payout logic in-house would have pulled engineering time away from the product itself. BotFusion also had a subscription model already in place (monthly and yearly packages with different bot allowances), so any commission system needed to be configured around that structure rather than the other way around.
The harder constraint was integration, not calculation. BotFusion wanted its users to keep registering and paying for a package entirely inside the existing BotFusion product — no redirect to a separate portal to sign up, and no second login to check partner activity. That meant the back office we built needed to run behind the scenes, connected purely by API, and stay invisible until a user actively chose to view it.
A white-label back office, built into BotFusion by API
Our team deployed a fully white-label MLM platform, configured its commission engine to BotFusion’s package structure, and connected it to BotFusion’s existing website and billing flow through a custom API integration — rather than replacing any part of the front end BotFusion had already built. Registration and payment stayed inside BotFusion; our software’s job was to validate referrals, run the commission calculations, and manage the back office behind that existing experience.
The centerpiece of that back office is the platform’s multi-tier commission engine — one of the core capabilities of our direct selling software, and the piece BotFusion’s plan relied on most heavily.
How the five-level commission calculation actually runs
This is the same multi-tier engine we deploy across our direct selling software implementations, configured here to BotFusion’s five-level structure. Here’s what happens on each qualifying purchase:
A purchase event fires
When a package purchase is confirmed inside BotFusion, BotFusion’s checkout sends a purchase event to the platform’s API, identifying the buyer and the package purchased.
The engine walks the sponsor chain
The commission engine looks up the buyer’s sponsor record and traces it upward through the referral chain, level by level, up to the five levels configured for BotFusion’s plan.
Commission is calculated per level
At each level, the engine applies the percentage configured for that level against the package value, and generates a separate commission entry for the partner sitting at that level.
Entries post to each partner's ledger
Each calculated commission is posted to the receiving partner’s ledger inside the platform in real time, where it becomes visible in their member panel and contributes to their withdrawable balance.
The same logic runs for every billing cycle
Because monthly and yearly packages are mapped to the same commission rules, the engine runs this calculation identically regardless of which billing cycle triggered the purchase event.
The result is a commission process that requires no manual calculation or spreadsheet reconciliation on BotFusion’s side — every purchase resolves into the correct set of commission entries automatically, the moment it happens.
Configuring the commission engine to BotFusion's structure
Rather than adapting BotFusion’s requirements to a generic template, our team configured the commission engine specifically around BotFusion’s package structure and payout rules. From a development standpoint, this involved three configuration layers: package mapping, level depth, and payout rules.
The engine was set up to calculate commission automatically across five levels of a referral chain on every qualifying package purchase, following the percentage split BotFusion specified for its plan. Package tiers were mapped directly to BotFusion’s existing product options so the commission engine always calculates against the correct package value:
| Package | Price | Includes |
|---|---|---|
| Affiliate | $9.99 | Affiliate access only, no bot |
| Starter | $49.99 / month | 1 bot |
| Pro | $95.99 / month | 3 bots |
| Starter Yearly | $499 / year | 1 bot, billed annually |
| Pro Yearly | $959 / year | 3 bots, billed annually |
Both billing cycles — monthly packages billed monthly, yearly packages billed annually — feed the same commission calculation logic, so the engine handles either cycle without separate rule sets. Payout requests are handled through a $100 minimum withdrawal threshold, processed monthly on manual request through the platform’s payout tools.
How BotFusion and the platform talk to each other
Beyond the commission calculation itself, three pieces of automation made the integration invisible to end users: referral validation, single sign-on, and payout processing.
Registration & payment stay in BotFusion
New users sign up and purchase their package (Affiliate, Starter, Pro, or a yearly plan) entirely inside the BotFusion product — there is no separate signup form for the end user to complete.
Referral validation through the API
When a new user signs up under a referral link, BotFusion passes the referral code to the platform’s API. The API checks that the referring account exists and is active before the sponsor relationship is written to the back office — invalid or broken referral codes are rejected at this step rather than silently accepted.
Single sign-on into the member panel
When a logged-in BotFusion user opens their commission dashboard, BotFusion’s backend requests a short-lived authentication token from the platform’s API on the user’s behalf. The platform verifies that token and starts an authenticated session in the member panel automatically, so the user lands on their dashboard already signed in — no second username or password to enter.
PayPal payouts
When a partner requests a withdrawal, the platform checks their ledger balance against the $100 minimum threshold and, once approved, sends the payment through its built-in PayPal payout integration directly to the partner’s PayPal account — no manual bank transfer or invoicing step required from BotFusion.
The result is a commission process that requires no manual calculation or spreadsheet reconciliation on BotFusion’s side — every purchase resolves into the correct set of commission entries automatically, the moment it happens.
The problems that actually had to be solved
Connecting a live subscription product to a commission engine by API raises a handful of problems that don't show up until purchase and payment events start flowing between two systems. Four of them shaped how this integration was built.
Preventing duplicate commission on retried events
Payment webhooks aren’t guaranteed to fire exactly once — network issues or timeouts can cause BotFusion’s checkout to send the same purchase event twice. If the commission engine treated each event as a new purchase, a partner could get paid twice for one sale. Every purchase event carries a unique transaction ID, and the engine checks that ID against processed events before calculating commission, so a retried event is recognized and discarded rather than double-paid.
Reversing commission on refunds and failed payments
A commission calculated at the moment of purchase can’t just stay on the books if the underlying payment later fails or is refunded. When BotFusion reports a refund or a failed renewal through the API, the engine reverses the corresponding commission entries across all five levels rather than leaving stale credits in partners’ ledgers.
Keeping the SSO token window short without breaking the handoff
A long-lived authentication token passed between BotFusion and the member panel would be a security liability if intercepted. The token issued for each SSO handoff is single-use and expires within a short window, so it’s only ever valid for the one login it was generated for — if a user’s session in BotFusion expires, they simply get a fresh token generated on their next click through, rather than the system falling back to a shared long-lived credential.
Reconciling monthly and yearly purchases against the same ledger
Because Starter and Pro packages can be billed monthly or annually, commission events for the same package tier arrive on different schedules depending on which billing cycle a buyer chose. The engine normalizes both into the same per-purchase commission calculation rather than running separate logic paths for monthly versus yearly billing, so the ledger stays consistent regardless of which cycle triggered a given entry.
What the BotFusion partner program runs on
Multi-tier commission system
A five-level commission engine that calculates and posts commission automatically on every qualifying purchase — a core capability of our direct selling software.
Custom compensation-plan implementation
The plan was configured to match BotFusion’s package structure and payout rules exactly, rather than adapted from a generic template.
API integration between BotFusion and the platform
A dedicated API layer connects BotFusion’s product to the commission back office for referrals, purchases, and commission events.
Referral validation through API
Sponsor relationships are verified via API call at the moment of signup, before being written to the back office.
Registration and payment inside BotFusion
Users never leave the BotFusion product to sign up or pay for a package.
Automatic multi-tier commission calculation
Every qualifying purchase resolves into commission entries across all five configured levels in real time, with no manual calculation required.
Single sign-on (SSO)
A token-based handoff authenticates a BotFusion login session directly into the platform’s member panel.
PayPal payouts
Withdrawal requests are checked against the ledger balance and minimum threshold, then disbursed automatically through the platform’s PayPal payout integration.
White-label platform
The platform runs as a white-label instance integrated with BotFusion’s existing brand and product, rather than a separate third-party portal.
What the integration delivered for BotFusion
Because registration, payment, and login all stay inside BotFusion’s existing product, the commission back office runs as infrastructure underneath BotFusion rather than as a separate system BotFusion’s team has to operate or maintain in parallel. Referral validation and commission calculation happen automatically through the API and commission engine, removing the need for any manual tracking or calculation on BotFusion’s side.
Because the platform runs white-label and connects via SSO, the partner back office looks and feels like a native part of botfusion.co.uk rather than a separate third-party tool — and because payouts are processed directly through the platform’s built-in PayPal integration, BotFusion didn’t need to build or maintain its own payment disbursement logic.
Commission infrastructure without rebuilding the product
There were two ways to connect BotFusion’s product to a commission back office: embed the MLM platform’s UI directly inside BotFusion via iframe, or keep the two systems separate and connect them by API and webhook events. We used the API approach. An embedded UI would have made BotFusion dependent on our platform’s front end rendering correctly inside their layout, and any update to either system’s interface risked breaking the other. Keeping the systems separate and API-connected meant BotFusion’s product could keep evolving independently, as long as the purchase and referral events it sends stay in the same format.
The same logic applied to how commission is stored: rather than recalculating a partner’s total commission on demand every time they check their dashboard, the engine posts individual ledger entries at the moment each purchase event is processed. That makes the payout balance a running total rather than a live computation, which is what makes instant, on-demand PayPal payouts possible — the platform never has to reconstruct commission history to answer “how much can this partner withdraw right now.”
This is the same architecture we bring to our broader direct selling software deployments, and it’s what makes white-label integrations like this one workable in practice: the client’s product stays the front door, and the commission engine stays a system it talks to, not a system it depends on.
Need commission infrastructure built into your own product?
BotFusion’s implementation shows what a white-label, API-connected commission engine looks like in practice — registration and payment inside your own product, with multi-tier commission calculation, SSO, and payouts running behind the scenes.
