A service is one thing StreamBoost can do for you, defined by what it acts on and how it is priced. Everything in the catalogue is configured on the platform rather than written into the website, which is why prices and limits can change without the site being rebuilt — and why the price you are quoted is always the price the server will charge.
What defines a service
- A name and category, so the catalogue is browsable.
- A target label — what to enter, such as a username or a channel URL.
- A target format, validated before the order is accepted.
- Minimum and maximum quantity, which bound what you can order.
- A pricing model, which decides how quantity becomes a price.
- Whether cancellation is supported, which depends on the service and on the system fulfilling it.
Targets
The target is the single most important field on the order form, because it is what fulfilment acts on. Each service states the format it expects, and the order is validated against that format before your balance is touched.
If a target is rejected, the mismatch is almost always shape rather than substance: a full https:// URL where a bare handle is expected, a display name instead of an account name, or a trailing slash or query string carried along from a copied address bar.
Quantity
Quantity is exactly what you asked for. StreamBoost records it as the target quantity for the order and never rewrites it to match what was actually delivered — that distinction is what makes a shortfall visible instead of quietly disappearing.
Delivered quantity is separately tracked, and it is clamped to what you ordered. If fulfilment ever over-reports, the extra is not counted: you cannot be shown units you did not buy.
The four pricing models
Every service uses one of four models. Whichever applies, the calculation happens on the server — the browser never computes a price and never sends one back, so a tampered page changes what it displays and nothing about what it is charged.
| Model | How the price is formed |
|---|---|
| Fixed | One price for the service, whatever quantity you request. |
| Per unit | A price for each unit. Held internally in millionths of a currency unit so long quantities do not accumulate rounding error. |
| Per thousand | A price per 1,000 units, charged pro rata for your quantity. |
| Tiered | Bands of quantity, each with its own per-1,000 rate, so a large order can be priced differently from a small one. |
What happens when you order
- 1The service, your target and your quantity are validated on the server.
- 2The price is calculated from stored configuration — not from anything the page sent.
- 3Your balance is charged, and the charge is written to your ledger in the same transaction.
- 4The order is handed to fulfilment and begins being tracked.
That ordering matters. The charge and the order record are created together, so there is no window in which money has moved but no order exists to show for it.
Cancellation
Cancellation is offered where both the service and the system fulfilling it support it — the order page tells you which. A cancelled order stops being processed immediately and stays in your history; it is never deleted.
Availability
A service can be disabled by an administrator, and so can the system behind it. When that happens the service stops appearing in the catalogue and stops accepting new orders. Orders already placed are unaffected — they keep their progress and continue.
Top-up amounts, payment methods and the full pricing model:
See how pricing works