What actually happens after you press Order
Most of the confusing things about SMM orders stop being confusing once you know what the chain actually looks like.
Step one: your wallet is debited
Before anything is sent anywhere, the charge comes out of your balance inside a database transaction that locks your account row.
The ordering matters. If the panel called the supplier first and debited afterwards, two orders submitted at the same moment could both pass the balance check and both go through, leaving the account negative. Debiting first makes that impossible: the second order finds the balance already gone.
This is also why a failed order refunds rather than never charging — the money moved before the failure was known.
Step two: the order goes to the supplier
The panel calls the supplier's API with a service id, your link and the quantity. The supplier replies with their own order id, which the panel stores against yours.
If that call fails — bad link, service unavailable, supplier out of balance — the order is marked failed and your money is returned immediately. That is the fastest failure in the chain and the one you almost never notice, because it resolves in seconds.
Step three: the supplier delivers
This is the part no panel can see into. The supplier draws from whatever source they have — networks of accounts, other suppliers, their own automation — and pushes units at your link.
Everything unpredictable about SMM lives here. Supply exhaustion, platform sweeps, rate limits, and the difference between a cheap service and an expensive one are all properties of this step. A panel is a shopfront over it; the honest ones say so.
Step four: statuses are polled
The panel asks the supplier, on a schedule, what has happened to every open order. It batches those questions — dozens of order ids in one request — because asking one at a time for hundreds of orders would take longer than the delivery.
Two consequences you have probably seen. Statuses lag reality by minutes, so refreshing frantically achieves nothing. And a panel with a broken or slow poller looks fine until something needs to change, which is when your Partial sits unrefunded.
Step five: refunds settle
When a poll returns partial or cancelled, the same job calculates what was not delivered and credits your wallet. It checks what has already been refunded for that order first, so a second poll cannot pay twice.
This is the step that separates panels. It is entirely automatic here, and on many panels it is a support agent with a spreadsheet — which is why "we will refund it, send us the order number" is such a common reply elsewhere.
Where the catalogue comes from
The service list is not typed in. A scheduled job pulls the supplier's full catalogue, matches each service by the supplier's own id, and refreshes cost, limits and capability flags. Services the supplier drops are deactivated rather than deleted, because existing orders still point at them.
Your price is then calculated from that cost by the commission rules — which is why prices here move when supplier prices move, instead of being a snapshot from whenever someone last updated a spreadsheet.
Why the same service costs different amounts on different panels
Every panel in the chain adds a margin. You may be buying from a panel that buys from a panel that buys from the supplier, and each layer takes its cut — which is why the same supplier service can appear at three different prices across three sites with no difference in what arrives.
It is also why a very cheap panel is not necessarily closer to the source. Sometimes it is; sometimes it is the same chain with a thinner margin and no refund process to pay for.
What happens when the supplier runs out of money
Panels hold a balance with their supplier exactly as you hold one with the panel. If that balance empties, every order the panel forwards is rejected — and from your side it looks like the panel broke, because the failure is instant and universal.
A well-run panel monitors that balance and alerts on it. It is the single most common cause of a panel that worked yesterday and rejects everything today, and it has nothing to do with your order or your link.
Why prices are held in one currency
The supplier bills in dollars, so the catalogue is stored in dollars. Your local price is a display conversion at the day's rate.
Doing it the other way — storing local prices — means every exchange-rate move quietly changes your margin without anything in the system recording that it happened. Storing the currency you are billed in keeps cost and price comparable forever.
What this means for you as a buyer
- Speed is the supplier's, not the panel's. A panel cannot make a queued service instant.
- Quality is the supplier's too. What a panel controls is which services it lists and how honestly it describes them.
- Refund behaviour is entirely the panel's. This is the part worth choosing on.
- Price accuracy is the panel's. A list that never changes is a list that is wrong.
Why the panel cannot simply "check" your account
A reasonable question when an order goes wrong: why not look at the profile and see what happened? Because the panel never touches the platform at all. It talks to a supplier; the supplier talks to the platform. Nothing in the chain gives the panel a way to read your follower count or see whether a post exists.
That is also why the start count on your order comes from the supplier rather than from us, and why "the number on my account does not match" is a question that has to be asked upstream.
The one-line version
Your click debits a wallet, calls an API, and starts a polling loop that ends in either a completed order or a refund. Everything you find frustrating about SMM lives in the step no panel can see; everything you should judge a panel on lives in the steps it controls.
Comments
No comments yet — be the first.