Pay Later has always been the simple part: 25% up front, three monthly installments, no finance charges. What changed in the latest release is how you settle each installment — including paying one straight out of your energy balance, which means a machine can help pay for itself out of the platform it already lives in.
Most hardware financing in this industry is either a loan with interest or a revenue-share arrangement that quietly takes a cut of production forever. Pay Later is neither. It is a payment schedule: a quarter of the order to start, then three equal monthly installments, with no additional finance charges or surprise fees. The hardware is deployed as soon as the first payment clears, so it is running while the balance is still outstanding.
That structure has been public for a while. The mechanics underneath it just got considerably more flexible.
Key takeaways
- 25% up front, three monthly installments, four months total — no interest, no finance charges.
- Hardware deploys after the first payment rather than after the last, so it is producing during the term.
- New: an installment can be paid from your energy balance — recorded in transaction history with the order and installment detail.
- New: SEPA bank transfer settles a single installment in the EU, from order details or order history.
- Alongside SEPA, individual installments can be paid with BTC Pay or Changelly Pay.
- Bank routes are supported for SEPA (EU), ACH (US), and transfers for Canada, Australia, Hungary and Turkey.
- Payment reminders go out automatically every 30 days, so the schedule does not depend on your memory.
Paying an installment from your energy balance
This is the change worth understanding properly, because it closes a loop that used to require moving funds out of the platform and back in.
Your energy balance is the credit held on the platform for hosting power. Rewards can be routed into it, referral commissions can be applied to it, and it can be topped up directly. Previously it did one job: it paid for electricity. It can now settle a Pay Later installment.
The safeguards are worth stating because they define the feature's edges:
- Only a pending installment is eligible. The feature applies to an installment that is due, not to arbitrary rebalancing of your schedule.
- Duplicate charges are prevented by design, so an installment cannot be settled twice through two routes.
- Every payment is recorded in transaction history with the order and the specific installment attached, so the audit trail names what was paid rather than showing an unexplained debit.
The practical effect: production that lands in your balance can go toward the hardware that produced it, without a withdrawal, a conversion and a re-deposit — and without the fees and delay each of those steps carries.
Settling a single installment by bank transfer
SEPA bank transfer now pays an individual installment in the EU, initiated from either order details or order history. That sounds small until you have tried to run a short payment schedule through a banking rail built for lump sums.
The full set of routes shown in the payment-instructions interface covers SEPA for the EU, ACH for the US, and bank transfer for Canada, Australia, Hungary and Turkey. Crypto routes remain available through BTC Pay and Changelly Pay, and a single order can be settled with a combination of methods.
What changed behind the scenes, and why you should care
One fix in the same release is worth knowing about, because it affected fairness rather than features. The daily overdue check used to time out partway through and skip the most recently overdue accounts. The consequence was inconsistent treatment: some accounts were flagged and charged a late fee the same day, while others were missed entirely and carried stale amounts.
It now completes in a single pass, so flagging happens the same day and late fees are calculated correctly. A billing system that treats identical situations differently depending on where you sit in a queue is a fairness problem, and it is the kind of thing that is invisible in a feature list.
Administrators can also now edit existing orders including Pay Later schedules. Where a change affects hosting, invoices and hosting contracts are reissued and the customer re-signs — a schedule change is a contract change, and it is handled as one.
Where Pay Later is the right tool, and where it is not
It fits when the constraint is timing rather than capital: you intend to buy the hardware, the economics work at your rate, and spreading four months of payments while the machine is already producing is simply better sequencing.
It fits poorly as a way to buy more hardware than the arithmetic supports. A payment schedule does not improve a machine's break-even electricity rate, and it does not change what hashprice is doing. If a unit does not cover its power at your rate, financing it over four months does not fix that — it just arrives in four pieces. Run the break-even figure first:
At a spot hashprice of $38.33 per PH/s per day and a rate of $0.048/kWh, that threshold is 33.3 J/TH. Check your hardware against your rate before you check it against a schedule.
Final thoughts
The headline structure of Pay Later has not changed, and it did not need to: a quarter down, three monthly payments, nothing added on top. What has changed is that settling it no longer forces you out of the platform and back in again. An installment can be paid from the balance the machines feed, or through the bank rail you actually use, one installment at a time.
Financing should change when you pay, never what you owe.
Three steps, in order
Check your break-even rate → choose the Bitcoin miner → start with 25%.
See how Pay Later works
