Categories
Hosting, Mining Business

Hosting is sold on credit. What the payment, suspension and lien clauses actually allow, how to assess a provider’s own financial stability, and why withholding a whole invoice over one disputed line is the fastest route to default.

Hosting agreements get read carefully in two places: the price per kilowatt hour and the term. The payment clauses in between tend to get skimmed, because at signing nobody expects to be late.

Then a quarter goes badly. Hashprice falls, a shipment of replacement hashboards eats the reserve, a treasury decision leaves less cash on hand than planned, and an invoice sits unpaid for three weeks. At that point the clauses nobody read start governing the relationship, and they are usually far more aggressive than clients expect.

This is how the commercial credit side of hosting actually works, in both directions: what a provider can do when you do not pay, what you should look for before you sign, and the one clause that turns a cash flow problem into a hardware problem.

Hosting is sold on credit, and that shapes everything

A hosting provider buys power from a utility, usually on monthly terms and frequently in arrears. They supply you power continuously and bill you afterward. For the period between delivering the electricity and collecting from you, they have financed your operation.

That is why deposits exist. A one to two month deposit is standard and is not a fee: it is collateral against the window the provider is exposed. It also explains why providers care about payment timing more than clients expect. A site running several hundred client machines on thirty day terms is carrying a very large receivable, and the utility will not wait.

Understanding that makes the rest of the clauses read less like aggression and more like a lender protecting a position, which is what they are.

The clauses that matter, in the order they bite

Payment terms. Find the number of days and what it runs from: invoice date, or receipt. Net 15 is common in hosting and is shorter than most other B2B services. An accounts payable process built around net 30 will be structurally late every month.

Late fees and interest. Usually a percentage per month on the overdue balance. The headline number looks small and annualizes to a lot. Check whether it compounds and whether it applies from the due date or after a grace period.

Suspension. This is the clause that matters most and the one most often skimmed. It gives the provider the right to power down your machines after a defined period of non-payment, frequently somewhere between ten and thirty days past due. Suspension is not termination, but powered-off miners earn nothing while continuing to accrue whatever fees the agreement says continue to accrue.

Continuing charges during suspension. Read whether hosting fees keep running while your machines are off. In many agreements they do, on the reasoning that the rack space is still reserved for you. That combination, no revenue plus continuing fees, is what turns a short cash squeeze into a spiral.

Lien and sale rights. The most serious clause in any hosting agreement. Many grant the provider a security interest in hardware on site, and the right to sell it against unpaid balances after notice. The specifics vary widely by jurisdiction and by how carefully the agreement was drafted. If you read only one clause before signing, read this one.

What good practice looks like from both sides

From the provider’s side, the behaviors that distinguish a professional operation are notice and proportionality. An invoice reminder before the due date. A clear first notice at the point the account goes past due, naming the date suspension would occur. A human conversation before any machine is powered down. Suspension as a last step rather than an automatic trigger.

From the client’s side, the single most valuable habit is talking early. Providers deal with seasonal cash flow constantly and most will work with a client who contacts them before the due date with a specific plan. The same client who goes quiet for three weeks and then asks for leniency gets a much worse outcome, because by then the provider has already assumed the worst and started protecting their position.

Nothing about that is unique to mining. It is ordinary trade credit. What is unique is that the collateral sits in the creditor’s building.

Assess the provider’s finances too, because the risk runs both ways

Clients are assessed for credit. Providers rarely are, and that asymmetry has cost people their hardware. A hosting provider under financial stress is a direct risk to your machines, regardless of whether you have paid every invoice on time.

There are signals you can observe without access to anyone’s books. Invoices that arrive late or in inconsistent formats. Requests to prepay further ahead than the agreement requires. A sudden push to collect early. Deferred maintenance you can see on a site visit. Staff turnover, particularly technicians. Slower responses to routine requests.

None of those is conclusive alone. Several together, especially a request for unusual prepayment, deserve a direct conversation. The escalation path when that conversation goes badly is covered in what to do when a hosting provider fails, and the preventative work belongs in your facility due diligence before signing.

Deposits: what to confirm before you pay one

A deposit is your money sitting in someone else’s account, often for years. Three questions are worth asking in writing.

Is it held separately, or does it fund operations? The honest answer from most hosting providers is that it funds operations, and that is normal, but it tells you the deposit is an unsecured claim if the business fails rather than a segregated asset.

What triggers its return, and when? Typically some number of days after the end of the term, after final reconciliation. Pin down the number.

Can it be applied against a late invoice without your agreement, and if it is, must it be topped back up? Many agreements say yes to both. That matters because a deposit silently consumed by one late payment leaves you with a top-up demand on top of the arrears.

Disputes are not the same as non-payment

The most avoidable way to end up in default is to withhold payment over a billing disagreement. If you believe an invoice is wrong, the correct move is almost always to pay the undisputed portion, withhold only the disputed line, and put the dispute in writing immediately with your reasoning and supporting data.

Withholding the whole invoice over one contested line converts a billing question into non-payment, and suspension clauses do not generally care why the balance is outstanding. The habit of reading every hosting invoice line by line when it arrives, rather than at quarter end, is what keeps disputes small and timely.

Questions to ask before signing

What are the payment terms, and do they run from invoice date or receipt? What is the late fee, and does it compound? After how many days past due can you suspend my machines? Do hosting fees continue to accrue while they are suspended? Do you take a security interest in hardware on site, and under what conditions can it be sold? How much deposit, is it segregated, what returns it, and must it be replenished if applied?

Those six questions take ten minutes at signing. They describe exactly what happens on the worst month you will have with this provider, which is the month worth planning for. Pricing is what you negotiate; credit terms are what you live with.

Explore Rax Mining

Categories