Recognise the request
A Bitcoin on-chain payment uses a blockchain transaction. A Lightning payment uses a network invoice or supported payment flow with its own expiry and routing. A merchant accepting BTC does not automatically accept Lightning.
Respect the invoice window
Check the requested amount and expiry. An exchange withdrawal may take longer than a direct wallet payment. Do not repeatedly pay an invoice because a page is slow to update; inspect the wallet’s outcome first.
Know what counts as settled
On-chain billing normally waits for a confirmation policy. Lightning settlement is different and a route can fail without completing the payment. Preserve the invoice and wallet payment record for support.
KoalaVPS scope
KoalaVPS checkout offers BTC on Bitcoin on-chain with a 25-minute live quote window. Lightning is not a connected customer payment route. The local checkout still requires backend transaction verification and order reconciliation before any payment can be treated as confirmed.
Distinguish pseudonymity and payment transport
A Bitcoin address is not inherently a real-name identifier, but public transactions can link activity. Lightning changes payment routing and settlement mechanics; it does not guarantee anonymity or fix an exposed hosting account. Use the actual supported invoice method and retain only the necessary proof.
Keep the wallet outside the support process
No billing adjustment requires your wallet seed. A transaction or invoice reference is the appropriate starting point. Keep a private record of the asset, network, amount and result so a delayed page update does not tempt you into an accidental second payment.
Follow an on-chain invoice through three states
For a Bitcoin on-chain purchase, first preserve the order and valid quote. Next check that the wallet actually broadcasts a transaction paying the requested destination and amount, with fees accounted for. Finally wait for the merchant’s confirmation and reconciliation policy. A wallet’s “sent” status and a merchant’s credited balance are different observations. The KoalaVPS quote window is 25 minutes; its actual invoice expiry governs the request, and payment verification still needs the connected backend.
- Do not replace a pending invoice with a second payment merely because the page has not refreshed.
- When a wallet or exchange changes a transaction, keep the current transaction identifier alongside the original payment record.
- For an underpayment or a late arrival, contact the merchant with the invoice and transaction reference; verify any supplementary transfer instructions before sending more funds.
- For a refund, agree a destination you control through the verified account channel rather than assuming the original input address is safe.
Official documentation: Bitcoin developer guide: payment verification
Diagnose a Lightning request as a separate payment
A BOLT 11 Lightning invoice encodes a payment request with its own network and expiry information. Open it only with a compatible wallet and confirm the decoded details before payment. When routing fails or the outcome is uncertain, inspect the wallet’s actual result first. Use a new invoice only after the old attempt’s outcome is understood. An on-chain Bitcoin address cannot receive a Lightning invoice payment.
- KoalaVPS customer checkout currently supports Bitcoin on-chain, not a Lightning merchant route.
- For another merchant offering Lightning, preserve the invoice and payment result needed for support; never disclose the wallet seed.
- Check available outbound balance, fees and invoice expiry when the wallet reports no usable route. Do not assume a merchant VPS problem from a route failure alone.
Official documentation: Lightning BOLT 11: invoice encoding