How SMM panels work, step by step

An SMM panel is a website that sits between customers and providers. A customer adds funds and places an order. The panel sends that order to a provider through an API. The provider delivers it, and the panel keeps checking the order's status and updates the customer. If something goes wrong, the panel refunds the balance or passes on a refill request.

The owner's profit is the difference between what the customer pays and what the provider charges. Let's follow one order through the whole journey to see how each piece fits.

The three parties

• The customer wants a service, for example 1,000 views on a YouTube video. They might be a creator, a small business, an agency, or another reseller.
• The panel owner runs the website, chooses providers, sets prices, handles support and collects payments.
• The provider fulfils orders. Providers sell wholesale to many panels through the standard SMM API v2.

Sometimes there are more layers: a provider may buy from another provider, and a panel may itself act as a provider for other panels. The basic flow stays the same.

Step 1: The customer adds funds

Most panels work on a prepaid balance. The customer chooses a payment method, such as M-Pesa in Kenya, MTN MoMo in Ghana or Uganda, Paystack or Flutterwave cards and bank transfers in Nigeria, or crypto anywhere, and tops up. The money goes to the payment gateway and then to the owner's own account. On PanelHubs, the platform never holds customer money; it goes straight to the owner.

The panel records the payment and adds the amount to the customer's balance in the panel's main currency. Customers can view prices in their own display currency, which makes it easier to understand what they're paying.

Step 2: The customer places an order

On the new order page, the customer picks a category and a service, pastes a link and enters a quantity. The panel shows the price and deducts it from the balance. Customers can also place many orders at once with mass order, spread an order over time with drip-feed, or set up a subscription that automatically orders likes or views for each new post.

Step 3: The panel sends the order to the provider

Each service on the panel is linked to a service at a provider. When the order is placed, the panel calls the provider's API with the provider's service ID, the link and the quantity, and pays from the owner's prepaid balance with that provider. The provider replies with its own order ID, which the panel stores.

If the provider rejects the order, for example because the owner's provider balance is too low, the order doesn't just vanish. On PanelHubs, failed orders are kept with the provider's reason, and orders that failed for low balance are resent automatically after the owner tops up the provider. The owner also gets low provider balance alerts to prevent this.

Step 4: Status sync

Delivery can take minutes or days. During that time, the panel asks the provider for updates using the stored order ID. The provider reports a status such as pending, in progress, completed, partial or cancelled, along with how many units are still to deliver.

The panel updates the customer's order list automatically. This is what lets customers check progress themselves instead of messaging the owner, and it's one of the biggest time savers in running a panel.

Step 5: Refunds for partial and cancelled orders

Not every order completes fully. If a provider marks an order as partial, meaning only some of the quantity was delivered, or cancels it, the customer should get money back for what wasn't delivered.

On PanelHubs, partial and cancelled orders are refunded to the customer's balance automatically. There's no refund request to file and no manual review. The customer can then use the balance on another order.

Step 6: Refills after completion

Some services include a refill period. If the count drops within that period, the customer clicks refill on the order, the panel sends a refill request to the provider through the API, and the provider tops the count back up. Cancels work the same way when the provider allows them. On PanelHubs, both are one click for the customer. You can read more in refills explained.

The money flow

Here's a simple example, with made-up numbers for illustration only:

1. A customer tops up the equivalent of $10 through mobile money. That money lands in the owner's account, minus the gateway's fee.
2. The customer orders a service the owner sells for $2. Their panel balance drops to $8.
3. The provider charges the owner $1.20 for that order from the owner's provider balance.
4. The owner's gross margin on the order is $0.80, before gateway fees, platform costs and time.

The owner has two balances to manage: money received from customers, and prepaid balances at providers. Keeping provider balances topped up from customer payments is part of the daily rhythm. Platform costs sit on top: on PanelHubs it's a monthly plan based on order volume, with no per-order fees.

Extra layers: API resellers and child panels

A panel can also be a provider. Every PanelHubs panel has the standard API v2 for its own customers, so another reseller can connect and send orders automatically, just like the panel does with its own providers. Owners can also sell child panels: separate branded panels that buy services from the parent panel and set their own prices. In both cases the order passes through one more step, but the same flow applies.

Getting started

Once you see the flow, a panel is less mysterious: payments in, orders out, statuses back, refunds and refills handled. Your job is choosing good providers, setting fair prices and looking after customers. If you'd like to run your own, you can create a PanelHubs panel and follow your first order end to end.