The NordBastion polar-bear mascot at a Nordic stone altar with a luminous Bitcoin-orange circular emblem and electric-yellow Lightning bolts forming a payment-channel mesh around it, cyan-N shield beside him

How-to·9 min read · 10 min hands-on · Updated 2026

How to pay with Bitcoin and Lightning.
On-chain in ten minutes. Lightning in seconds.

Both rails are supported on every NordBastion top-up. Same panel form, two checkout paths, identical credit afterwards.

Pick a rail

Bitcoin · on-chain

~10 min

Settlement: 1 confirmation
Fee: Mempool-dependent
Best for: Larger top-ups
Wallets: Sparrow · Electrum

Bitcoin · Lightning

<10 s

Settlement: Instant
Fee: A few sats
Best for: Small top-ups, urgency
Wallets: Phoenix · Blixt · Mutiny

Chapter 1

Lightning is what Bitcoin should have been for small payments.

Bitcoin's base layer was not designed for $5 payments. The network produces one block every ten minutes, the block has a finite capacity, and the fee market routes transactions by who pays the most per byte. For a $500 top-up that is acceptable; for a $5 top-up the fee can be 5% of the principal during a busy mempool.

Lightning is a payment layer on top of Bitcoin that settles instantly off-chain and only periodically anchors back to the base layer. Two parties open a channel by locking BTC in a 2-of-2 multisig output on-chain; afterwards they can move BTC between themselves arbitrarily many times without writing to the chain. Channels route payments through other channels — a single hop is enough for direct partners; multi-hop routing finds a path across the wider network.

For a customer paying NordBastion: open a channel with any well-connected Lightning service provider (LSP), keep some outbound liquidity, and you can top up arbitrarily many times for arbitrarily small amounts at arbitrarily fast speed. The whole exercise costs a few sats per payment plus the one-time channel-open on-chain fee.

Walk-through · On-chain

Five steps for the on-chain rail, the predictable path.

1. Install a wallet. Sparrow Wallet on desktop is the current default. It supports single-sig, multi-sig, hardware wallets, has built-in Tor, and a clean RBF / CPFP fee-bumping UI. Electrum is an excellent lighter alternative. Avoid custodial mobile wallets for this use-case — the privacy gain of a self-custodial wallet is the whole point.

2. Have BTC in the wallet. Acquire it any way you like — decentralised exchange, non-KYC swap, peer-to-peer cash. Avoid sending directly from a KYC exchange to NordBastion if your threat model cares about the chain trail. If you must, use a coin-join (Wasabi/Whirlpool) or just route through a self-custodial wallet first to break the public exchange-to-host link.

3. Open the top-up. In the panel: Top up → choose Bitcoin (on-chain) → enter the USD amount. The panel returns a fresh single-use receive address and the exact BTC amount equivalent at the current rate. The address is valid for 24 hours.

4. Send. Paste the address into your wallet, enter the exact BTC amount, pick the next-block fee, sign and broadcast. The transaction enters the mempool; in roughly 10 minutes a miner includes it in a block.

5. Order a server. NordBastion credits the balance after one confirmation. The panel updates; if you have a webhook subscription, a topup.confirmed event fires. Click Order, pick a tier and a bastion, and the server boots in about 90 seconds.

Walk-through · Lightning

Five steps for Lightning, the instant path.

1. Install a Lightning wallet. Phoenix on mobile (automatic channel management, simplest experience), Mutiny in a browser (no install), or Blixt if you want full manual channel control. Each handles the inbound-liquidity dance differently; Phoenix opens a channel on first receive at a small fee.

2. Have BTC available on Lightning. Send some on-chain BTC to your Lightning wallet — it will open a channel automatically the first time it sees an inbound. The on-chain fee is paid once; subsequent Lightning payments cost a few sats each. For a customer who tops up a few times a year, this is fine; for very low frequency it might be worth staying on-chain.

3. Open the top-up. In the panel: Top up → choose Bitcoin (Lightning) → enter USD amount. The panel returns a BOLT11 invoice — a long string starting with lnbc — and a QR code. Invoice expiry is 5 minutes by default to keep the rate exposure tight.

4. Pay. Paste the invoice into the wallet, or scan the QR. The wallet finds a route through the Lightning network, settles in under 10 seconds, and the panel shows Confirmed before you can switch tabs.

5. Order. Same as on-chain — pick a tier and a bastion, server boots in 90 seconds.

Privacy considerations

Bitcoin is pseudonymous. Know what that does and does not buy you.

On-chain · what it protects

NordBastion never learns your identity. Account is an email + password. The link between you and the wallet that paid is only as good as the link between you and that wallet — break it, and the host has nothing to leak.

On-chain · what it leaks

The chain is public. Any subsequent investigator with access to chain-analysis tooling can walk backward from NordBastion's collection wallet to your sending wallet. If that path traces to a KYC source, the identity link is recoverable.

Lightning · what changes

The actual payment hop is private (a brief HTLC routed through intermediaries), but the channel-open transaction that funded your wallet is on-chain. The on-chain analysis still applies to the channel-open; the LN hop itself is opaque.

When to pick Monero

When the on-chain chain-analysis path matters in your threat model and you do not want to defend against it with mixers or coin-joins. Monero closes the path by default — see /guides/how-to-pay-vps-with-monero/.

FAQ · Bitcoin / Lightning

Questions, answered.

Eight questions a Bitcoin / Lightning user asks before paying a host.

When should I use Lightning instead of on-chain Bitcoin?

Lightning makes sense when the top-up amount is small (a few dollars to a few hundred), urgency is high (you want the server in seconds, not ten minutes), and you already maintain a working Lightning wallet with inbound liquidity. On-chain makes sense when the amount is large enough that on-chain fees are negligible as a percentage, when you do not want to deal with channel-management edge cases, or when you are funding a long-running prepaid balance you do not need to top up often.

Which Bitcoin wallet should I use?

For on-chain, Sparrow Wallet on desktop is the current default recommendation — modern, multi-format (single-sig, multi-sig, hardware-wallet-friendly), built-in Tor, and a clean fee-bumping UI. Electrum remains an excellent choice if you prefer a lighter footprint. For Lightning, Phoenix is the simplest mobile wallet (auto-managed channels), Blixt if you want manual channel control, Mutiny if you want a browser-based option. If you run your own node, Core Lightning or LND speaks LN directly and the workflow is identical.

Can I send Bitcoin to NordBastion from a KYC exchange?

Technically yes, but the privacy outcome is reduced. The exchange holds your identity and a record of every withdrawal it processes; the on-chain graph then publicly links your exchange withdrawal to NordBastion's collection wallet. For a customer who treats the host as KYC-free at the front door but is comfortable with the exchange-to-host chain being analysable, this is fine. For a customer whose threat model includes "an investigator works backward from the host's wallet," send the BTC through a self-custodial wallet first (and ideally a coin-join if you have used one).

How long does a Bitcoin on-chain confirmation take?

NordBastion credits after a single network confirmation. That is usually about 10 minutes — Bitcoin produces a block roughly every 10 minutes on average. Mempool congestion can extend it; setting a fee at the current "next-block" level (visible in any modern wallet) keeps the wait predictable. The panel shows the live progress.

Is Lightning safe for hosting payments?

Yes. Lightning is settled by signed bilateral transactions that can be enforced on the Bitcoin base layer if either party misbehaves. The two operational caveats: (1) the receiving wallet must have inbound liquidity for the amount, which NordBastion maintains; (2) the customer wallet must have outbound liquidity, which is the routine concern of any Lightning user. If a route cannot be found, the payment simply fails and no funds move.

Is on-chain Bitcoin really anonymous?

It is pseudonymous. Every Bitcoin transaction is a public ledger entry. A determined investigator can chain-analyse the graph backward from the receiver to the sender to the funding source. For threat models that include this, two options improve the privacy floor: (a) use Monero instead — see /guides/how-to-pay-vps-with-monero/. (b) Use a coin-join service (Wasabi or Whirlpool, where available) before paying, so the on-chain trail breaks at the join.

What fee should I set on my on-chain transaction?

Pick the "next-block" or "one-block" fee suggestion in your wallet. Sparrow, Electrum and Mutiny all surface the current mempool rates clearly. Under-fee a transaction and it can sit unconfirmed for hours; over-fee and you waste sats. The exact sats-per-vByte at any given moment is mempool-dependent.

What if my on-chain payment is stuck?

Modern wallets support RBF (Replace-By-Fee) — re-broadcast the same transaction with a higher fee. Sparrow and Electrum expose this in one click. Once one of the two versions confirms, the other is dropped. NordBastion sees only the confirming one and credits the balance once it lands. If you cannot RBF, CPFP (Child-Pays-For-Parent) is the fallback — pay a high-fee child transaction that spends the stuck one's output, and miners include both.

Ready